Domain vs URL-Prefix Property
Two kinds of Search Console property: a domain property covers all subdomains, protocols and paths; a URL-prefix property covers one exact prefix.
Reviewed by Alexander Yarovenko · Updated: 2026-10-04
A Search Console property is the site or part of a site whose data you view. A domain property covers everything under a domain: every subdomain, protocol and path, with www and non-www together. A URL-prefix property covers only URLs that start with one exact prefix, including protocol and subdomain.
What it is and where the boundary lies
The choice decides what the reports include. A domain property for example.com includes subdomains such as blog.example.com, both http and https, and all paths. A URL-prefix property for https://example.com/shop/ includes only addresses that begin with that string; https://www.example.com/ or http://example.com/ would need their own properties. The choice changes coverage and verification, not how Google ranks the site.
How it differs from similar terms
| Aspect | Domain property | URL-prefix property |
|---|---|---|
| What it covers | all subdomains, protocols and paths | only URLs with the exact prefix |
| www and non-www | both included | separate properties needed |
| http and https | both included | separate properties needed |
| Verification | DNS record only | HTML file, tag, Analytics, Tag Manager or DNS |
| Best for | the whole site in one view | one path, protocol or subdomain |
Why it matters
With a URL-prefix property it is easy to miss traffic: a site that serves both www and non-www, or both protocols, splits its data across several properties, and each shows only part. A domain property gives one complete picture. A prefix property is useful when you deliberately want a slice, for example a directory owned by another team.
How to choose
- Want the whole site in one place? Use a domain property.
- Cannot edit DNS records? Use a URL-prefix property, which accepts several verification methods.
- Need data for one folder or one subdomain? Add a URL-prefix property for that prefix.
- Serve several variants? A domain property saves creating one prefix property per variant.
- Need both? Keep both: the domain property for the full view, prefix properties for slices.
Practical example
| Property | Covers | Misses |
|---|---|---|
| domain: example.com | everything below | nothing |
| prefix: https://example.com/ | https, no www, all paths | www, http and subdomains |
| prefix: https://www.example.com/ | https with www | non-www, http and subdomains |
| prefix: https://blog.example.com/ | the blog subdomain | the main site |
Three prefix properties would be needed to approximate what one domain property shows.
Common mistakes
- Adding only one prefix variant: data from the other variants is missing from that view.
- Comparing totals from different properties: they cover different sets of URLs.
- Choosing a domain property without DNS access: verification uses a DNS record only.
- Assuming the type affects ranking: it changes what you can see.
- Expecting to convert one type into the other: add a new property and verify it.
How to validate the result
After adding a property, wait for data and compare its totals with another property that overlaps it. For a domain property the total should be at least as large as that of any prefix property under it. Check the Page indexing report and the Performance report in the property you will actually work in.
More questions
Which property type is better?
A domain property for a full view of the site; a URL-prefix property for a slice or when you cannot edit DNS.
How many properties can I have?
Google’s help says up to 1,000 per Search Console account.
Can I convert a prefix property into a domain property?
The help page does not describe conversion. Add a new property of the type you want and verify ownership.
Next practical step
List every address your site answers on (protocol, www, subdomains) and check whether one domain property covers them. The lesson on what Search Console is shows how the properties fit into the tool.
Related concepts
- Google Search Console — the tool where properties live.
- Performance report — data you see per property.
- URL Inspection tool — works for URLs in the selected property.
- Sitemap — submitted per property.