Domain Property vs. URL-Prefix Property in Search Console
Quick answer: A Search Console Domain property covers all protocols and subdomains for a domain and requires DNS verification. A URL-prefix property covers only URLs beginning with the exact prefix and supports several verification methods. Use a Domain property for a complete site-wide view; use URL-prefix properties when you need narrower scope or cannot change DNS.
Two properties can display the same brand name and still cover very different sets of URLs. That difference affects verification, totals, access, and whether a public traffic claim represents the whole site.
For most sites with DNS access, Google recommends the broader Domain-level view. URL-prefix properties remain useful for narrow sections, operational boundaries, and verification methods that do not require DNS changes.
SEARCH CONSOLE
Domain Property vs. URL-Prefix Property in Search Console
PRIMARY KEYWORD
Domain property vs URL-prefix property
READ TIME
8 minutes
What does a Domain property include?
A Domain property covers the domain across protocols and subdomains. A property for example.com can include https, http, www, and other subdomains under that domain. Verification is performed through DNS.
That scope is useful for consolidated reporting and for finding traffic on hosts or protocols that a team might otherwise forget. It also means totals can be larger than any one URL-prefix property.
What does a URL-prefix property include?
A URL-prefix property covers URLs beginning with the exact property prefix. Protocol and path matter. A property for https://example.com/blog/ does not automatically include http://example.com/, https://www.example.com/, or pages outside /blog/.
URL-prefix properties support multiple verification methods and can isolate a specific host or section. They are useful when teams have distinct responsibilities or cannot manage the domain's DNS.
Which property type should you use for traffic verification?
Use the property whose scope matches the public claim. If the receipt says “example.com organic clicks,” a Domain property is the clearest source for a whole-domain total. If the claim is specifically about a subdomain or directory, a matching URL-prefix property can be appropriate.
Prevent duplicate or confusing choices in the interface by grouping properties by registrable domain, labeling the type, and favoring the Domain property when both cover the same public site. Never relabel a sitemap URL-prefix as if it were the root domain.
Why might the two property types report different numbers?
The Domain property can include additional subdomains and protocols. A URL-prefix property can exclude canonical destinations or redirected variants outside its prefix. Different users may also apply different filters or view different data states.
Compare a matching subset rather than assuming the totals should be equal. If the site's canonical traffic all resolves to one prefix, they may be close, but scope still needs to be confirmed.
- Domain: broad scope, DNS verification
- URL-prefix: exact prefix, several verification options
- Domain is usually clearer for whole-site reporting
- URL-prefix is useful for a host, protocol, or path boundary
TAKEAWAY CHECK
What belongs on the choose the right property?
- 01Write down the exact public claim.
- 02List protocols, subdomains, and paths that should count.
- 03Use a Domain property for full-domain coverage when possible.
- 04Use URL-prefix only when its narrower scope is intentional.
- 05Label the property type in shared reports.
- 06Keep sitemap or page URLs out of the display name.
What else do people ask about Domain property vs URL-prefix property?
Can I have both property types for the same site?
Yes. Many teams keep a Domain property for complete reporting and URL-prefix properties for operational or historical needs. Be careful when dashboards list both, because users can accidentally publish or compare totals from different scopes.
Why is my sitemap showing as a Search Console property?
Someone may have created a URL-prefix property using the sitemap URL instead of submitting that URL in the Sitemaps report. Because URL-prefix properties accept paths, Search Console can return it as a property. Prefer the root Domain or intended URL-prefix property for site reporting.
Does a Domain property prove legal ownership of the domain?
DNS verification demonstrates control sufficient to add the verification record. It does not by itself prove legal ownership of the company, trademark, content, or asset. Use precise language such as verified Search Console owner rather than broader legal claims.
Can a URL-prefix property include subdomains?
Only when the subdomain is part of that exact prefix. A property for https://www.example.com/ does not automatically include https://shop.example.com/. Add a separate prefix or use a Domain property when consolidated subdomain coverage is required.
Which primary sources support this guide?
Product behavior and metric definitions change. These are the official Google references used for this article and checked on July 19, 2026.
- 01Google Search Console property types
Official differences between Domain and URL-prefix properties.
- 02Google Search Console: users and permissions
Google's definitions of verified owners, delegated owners, full users, and restricted users.
- 03About Search Console data
Google's documentation on freshness, privacy omissions, row limits, time zones, and discrepancies.
PUT THE CLAIM ON THE RECORD
Your SEO result deserves a source, not a trust-me caption.
Connect an owner-level Search Console property, choose what stays public, and get a receipt with a stable share link.