“URL is not in property” is Search Console telling you the URL you pasted into the inspection bar does not belong to the property you currently have open. Nothing is wrong with the page. You are standing in the wrong room.
You may have met the same thing in its longer wording, which is the one most people paste into Google: inspect a URL in the currently selected property, or switch properties. Same message, same cause, same fix.
It is one of the few Search Console messages that says exactly what it means and still gets misread constantly, because people assume it is a verdict on the URL. It is not. Google’s URL Inspection documentation puts the rule plainly: the URL must be in the current property, and to test a URL in a property you do not own, you use a non-owner test such as the Rich Results Test instead.
Why does Search Console say the URL is not in property?
A Search Console property is not “my website”. It is a very specific string, and it comes in two shapes with different coverage. This is the whole cause of the error.
Run through that list against the URL you pasted and the property name at the top left of the screen, and the answer is almost always in one of these:
- The protocol. The property is
http://example.com/from years ago, the site moved to https, and every URL you inspect now sits outside it. - The www.
https://example.com/andhttps://www.example.com/are two separate URL-prefix properties. Half the accounts I open have both, with data in only one of them. - A subdomain. Blog on
blog.example.com, shop onshop.example.com, help centre on a vendor subdomain. A URL-prefix property for the root host covers none of them. A domain property covers all of them. - The path prefix. A property verified as
https://example.com/uk/will refuse a URL at/de/. This is deliberate, and it is how agencies get access to one section of a client site. - The wrong account entirely. You are looking at the property for a different client. It happens more often than anyone admits when you have thirty of them in the list.
How to fix it
If you own the site, the fix is to open the property that covers the URL, or to create one that does. Check the property switcher first: the URL may already be covered by a property you have and simply have not selected. If not, and you have DNS access, add a domain property. It covers every protocol, every subdomain, and every path in one place, and it removes this entire category of confusion permanently. That is my default on any account I set up, and the reason is not the data, it is that nobody can ever inspect a URL into the wrong room again.
There is one thing worth knowing before you switch everyone over: a new property starts collecting from the day it is verified, so the domain property will not carry the historical performance data your old URL-prefix property has. Keep the old one. Verify the new one alongside it and let the history build.
If you do not own the site, you cannot inspect it, and no workaround changes that. Inspection reports what Google’s index holds about a page, which is owner-only information. What you can do without ownership is run the Rich Results Test on the live URL, which fetches and renders the page and tells you what structured data Google can read from it. That is a live fetch, not index data, and it answers a genuinely different question. For anything about whether the page is indexed, the honest external check is a site search or a rank check, both of which are approximations. My guide on whether the site: operator is accurate covers how far that gets you.
The check that saves the most time
Before you inspect anything on an unfamiliar account, read the property name at the top and read it as a string, not as a brand. https://www.example.com/ is a different thing from example.com, and the difference decides which URLs will work all day.
The reason this matters beyond the error message: a URL-prefix property that misses half the site also means the Page indexing report you have been reading covers half the site. The counts are not wrong; they are just answering a narrower question than you thought you asked. When a client tells me their indexed count looks far too low, the property definition is the first thing I check, before anything about the pages themselves. It sits alongside URL is unknown to Google in the small set of Search Console messages that describe your account setup rather than your website.
Sources
- Google Search Console Help, URL Inspection tool, the URL must be in the current property, and non-owner testing
- Google Search Console Help, Search Console property types, domain and URL-prefix coverage