Choose a domain property when you want all data for a site: every subdomain, every protocol and every path. It needs a DNS record. Choose a URL-prefix property when you cannot edit DNS, or when you want data for one protocol, subdomain or folder. Many owners add both, with the domain property as the full picture.
What each type covers
Google's help puts it this way. A domain property aggregates data for all subdomains, protocols and subpaths. A URL-prefix property includes only URLs that begin with the exact prefix, protocol included, and its own example excludes http:// and m. addresses. A separate property is needed for each protocol and each subdomain you want covered that way.
Decision table
| Your situation | Choose | Reason |
|---|---|---|
| You manage the DNS and want complete data | Domain | One property covers http, https, www, non-www and subdomains |
| Site has several subdomains (app, blog, docs) | Domain | Otherwise each needs its own prefix property |
| Hosting or domain access sits with someone else | URL-prefix | HTML tag or file methods do not need DNS |
| Client site, and you only need one folder such as /blog/ | URL-prefix with that path | Google says to use a prefix to limit data by path or protocol |
| You migrated from http to https or changed www | Domain, plus keep the old property | Old and new addresses are different prefixes |
| Team members should see only part of the site | URL-prefix per section, plus a broad one | Matches Google's suggestion for distinct sections |
Verification per type
| Type | Methods in Google's help | Keep in place |
|---|---|---|
| Domain | DNS TXT or CNAME record only (Google-hosted sites verify automatically) | Do not remove the record after verifying, or you lose verification |
| URL-prefix | HTML file upload, HTML meta tag, Google Analytics, Google Tag Manager | The file, tag or snippet must stay. Search Console checks periodically |
Child properties inherit the parent's verification, and several owners can verify the same property. Owners using the same method should avoid overwriting each other's tokens. Google also says that if every verified owner loses access, all users lose access.
Picking in practice
If you can add a DNS record, start with a domain property, because later changes such as a move to https or a new subdomain stay inside it. Add URL-prefix properties only for folders or teams that need a narrower view. WordPress owners without DNS access can still verify a prefix with the meta tag method; the steps are in connecting Search Console to WordPress.
If data looks missing
Check the property list first. Google's Performance report help says chart data is aggregated by property, so the wrong prefix shows little or nothing for the right site. Other causes are covered in Search Console not showing data. Once the data is flowing, the low CTR pages finder and the guide on a good CTR help you use it.
Common mistakes
- Adding only the http version of a site that now serves https. The prefix then matches almost nothing.
- Removing the DNS record after verification. Google says this loses verification.
- Typing a path or www into a domain property. It takes the root domain only.
- Relying on one person's token. Add a second owner so a departing teammate does not lock everyone out.
We did not find a Google statement that a domain property shows more or better data than a prefix covering the same URLs. The difference is coverage, not data quality.
Questions people ask
Can I have both a domain and a URL-prefix property for one site?
Yes. Google's help suggests creating a property per section plus a broader one, such as a domain property, when a site has distinct sections. Different teams can then see only the part they manage.
Why does my URL-prefix property show no data?
A prefix property only counts URLs beginning with the exact prefix, including protocol. If your site lives at https://www.example.com but you added https://example.com, the traffic belongs to a different property. Add the right prefix or a domain property.
Do I type www in a domain property?
No. Google's help says not to include a www prefix, because a domain property already includes both www and non-www, along with other subdomains.
Does a domain property need DNS access?
Yes. Google's verification help lists a DNS TXT or CNAME record as the only method for domain properties, apart from Google-hosted sites that verify automatically. Verification can take a few days to propagate.
Related
Sources
- Search Console Help: Add a website property, accessed 2026-11-12.
- Search Console Help: Verify your site ownership, accessed 2026-11-12.
- Search Console Help: Performance report, accessed 2026-11-12.