The URL not in property error in Google Search Console looks scarier than it is. It is not an indexing problem; it simply means the URL you pasted into URL Inspection does not belong to the property you currently have selected.
I hit this on this very site, and the fix took under a minute once I understood what Google was actually checking. Here is what the message means, why it shows up, and how to stop seeing it for good.
Key Takeaways
- “URL not in property” means the inspected URL does not match the selected property; your page can still be perfectly indexed.
- URL-prefix properties are exact: https vs http, www vs non-www, and every subdomain count as different properties.
- The fix is switching to the property that matches your URL, or adding and verifying that version if it does not exist yet.
- A Domain property covers every protocol and subdomain at once, which prevents this error permanently.
What “URL not in property” actually means
The URL Inspection tool only inspects URLs that live inside the property you have open. When the URL falls outside that boundary, Search Console refuses with the message “URL not in property. Inspect a URL in the currently selected property or switch properties.” It is a scope check, nothing more.
Google explains in its URL Inspection documentation that the tool works per property, so this message says nothing about whether the page is indexed, penalised, or broken. It only says you are standing in the wrong room while asking about it.
Why Search Console says your URL is in a different property
Almost every case comes down to how strict URL-prefix properties are. A property added as https://www.example.com covers only URLs that start exactly like that, so the http version, the non-www version, and every subdomain are all treated as separate websites by Search Console.
That is why the error usually appears right after a migration to https, a www change, or when a site runs both versions in parallel. You are inspecting a real URL of your own site, just under a prefix the selected property does not cover.
| Mismatch | Example | The quick fix |
|---|---|---|
| Protocol | Inspecting an http URL in an https property | Inspect the https version, or add the http property |
| www vs non-www | Inspecting www.example.com inside the example.com property | Switch to the www property, or add it |
| Subdomain | blog.example.com inside a www.example.com property | Add the subdomain as its own property, or use a Domain property |
| Different site | Pasting a client’s or competitor’s URL | You can only inspect URLs in properties you have verified |
A close cousin of this message is the canonical variant, where Search Console tells you the Google-selected canonical sits in another property. I covered that separately in how to fix the canonical URL not in property error, because the cause there is canonicalisation rather than scope.
How to fix URL not in property, step by step
- Copy the exact URL from your browser, then look at the property selector in the top-left of Search Console. Compare the prefix character by character: protocol, www, subdomain.
- Switch to the matching property from that dropdown if you already own it, then run the inspection again. This resolves the majority of cases instantly.
- Add the missing property if no version matches: click “Add property” in the same dropdown, enter the exact prefix, and verify it. Google walks through the options in its add a website property guide.
- Re-run URL Inspection inside the correct property; the error disappears because the URL now sits within scope.
Use a Domain property to avoid property mismatches for good
If you keep juggling http, https, www, and subdomain versions as separate properties, the durable fix is a Domain property. It is verified once through DNS and covers every protocol and every subdomain of the domain, so no URL of yours can ever fall outside it.
URL-prefix properties still have their place, because they let you scope data to one section or version when you genuinely want that split. But as the main property for a normal site, the Domain type removes this whole class of error, and I set one up for every project I work on.
So, how serious is a property mismatch in Search Console?
Honestly, it is the least serious error Search Console will ever show you, because nothing on your site is wrong. Your rankings, indexing, and traffic are untouched; the tool just refused to answer a question asked in the wrong property.
Where I would spend the saved energy is on the property setup itself: verify a Domain property and the confusion never returns. And if your actual goal was to pull a page out of Google rather than inspect it, that is a different job, which I covered in how to remove URLs from Google search results.
Still fighting a Search Console error?
If a stubborn Search Console message will not go away, feel free to contact us or email me and I will help you pin down the cause. A clean property setup makes every other diagnosis easier.
Update Logs
04 Jul 2026
- Reworked the fix around property scope: why URL Inspection rejects URLs from a different property version, with a mismatch table, a Domain property recommendation, and current Google references.
Want our posts to show up more often on Google?
One step & Google will surface this site in your Top Stories.
