Domain vs URL-Prefix Property
When you add a site to Google Search Console you choose between a Domain property and a URL-prefix property. They cover different things and verify differently. This guide explains both, compares them side by side, and tells you which to pick and how to set it up.
- Exact coverage
- Verification methods
- Pros and cons
- Which to choose
Domain example.com (all subdomains, http+https) URL prefix https://www.example.com/
A Domain property covers everything under a root domain: all subdomains, http and https, every path. It needs DNS verification. A URL-prefix property covers only URLs that start with the exact prefix you enter, and offers more verification methods. Choose Domain if you can edit DNS; choose URL-prefix for one section or when you cannot. Many sites use both.
Domain property
A Domain property includes everything under one root domain: all subdomains such as m. or www. or deeper ones, both http and https, and ftp, with every path on those hosts.
example.com
Enter only the root domain. Do not add www, a protocol or a path; www is added automatically.
Not for public suffixes
Public suffixes cannot be verified, and the same name under a different ending, such as .org instead of .com, counts as a separate property.
URL-prefix property
A URL-prefix property includes only URLs beginning with the exact prefix you specify, including the protocol and the final slash. Subdomains, other protocols and other paths are excluded.
| Prefix entered | Covered | Not covered |
|---|---|---|
| https://www.example.com/ | All https www URLs | http, non-www, other subdomains |
| https://www.example.com/blog/ | Only URLs under /blog/ | Everything else |
A site that uses both http and https, or several subdomains, needs a separate property for each.
Side by side
| Feature | Domain | URL-prefix |
|---|---|---|
| Covers subdomains | Yes | No |
| Covers http and https | Yes | No, only the one you enter |
| Section-level data | Needs filters | Built in by choosing a folder prefix |
| Verification | DNS record only (except Google-hosted sites) | Several methods |
| Setup effort | One property | One per protocol, subdomain or section |
Which should you choose?
| Your situation | Choose |
|---|---|
| You can edit DNS and want everything together | Domain |
| You cannot access DNS | URL-prefix |
| You need data for one section, protocol or subdomain | URL-prefix |
| You want totals plus section views | Both |
Verification
Domain properties require a DNS record. The exception is Google-hosted sites such as Blogger or Google Sites, which verify automatically when you use the same account. URL-prefix properties offer many methods. The Google page links to a separate verification guide, so I do not list the methods here as fact. For a walkthrough, see Google Search Console setup.
Set it up step by step
Decide the type
Use the table above.
Type the value correctly
Domain: root domain only. URL-prefix: full URL with protocol and final slash.
Prove ownership
Domain needs a DNS record. For URL-prefix use any available method.
Let data accumulate
Data collection starts once anyone adds the property, even before verification. It usually appears within a few days.
Using both together
Reports differ by property. Check the Performance report in each. If you only use one property, the Domain property is the more complete choice when DNS is available (my own recommendation).
Notes for WordPress sites
- DNS access. If DNS sits at your registrar or Cloudflare, add the TXT record there (my own note).
- Several host versions. If you use URL-prefix, add the exact version you serve, including https and www or non-www.
- Plugins. SEO plugins can add a verification meta tag, which suits URL-prefix properties. See Yoast SEO settings.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Fix |
|---|---|---|
| No data yet | Just added | Wait a few days |
| Data missing for a subdomain | URL-prefix property used | Add that subdomain or use Domain |
| DNS verification fails | Record not saved or not propagated | Recheck the record and retry later |
| Wrong totals | Compared different property types | Compare like with like |
Checklist
Choose
- Can I edit DNS?
- Need section data?
- Several subdomains?
- Decide Domain, prefix or both
Enter
- Domain without protocol or www
- Prefix with protocol and slash
- Correct host version
- No typos
Verify
- DNS record for Domain
- Pick an available method for prefix
- Confirm success
- Keep verification in place
After
- Submit sitemap
- Check data in a few days
- Add section properties if useful
- Share access with owners
What Google’s page does not say
Google’s page does not rank one type as better and does not list the URL-prefix verification methods itself, deferring to a separate guide. It also does not say how long DNS changes take to be detected.
Key terms
- Property
- A site or section added to Search Console.
- Root domain
- The base domain such as example.com.
- Prefix
- The start of a URL, including protocol.
- DNS record
- A setting at your domain provider used to prove ownership.
Common mistakes
Adding www to a Domain property
It is added automatically.
Forgetting the trailing slash
Prefix must be exact.
One host version only
Misses other versions.
Deleting the DNS record
Verification can be lost.
Expecting instant data
It takes days.
Mixing totals
Different scopes.
Related guides
Domain vs URL-prefix questions
Which is better?
It depends. Domain gives a complete view; URL-prefix gives precise segments and more verification options.
Does Domain include subdomains?
Yes, along with http, https and every path.
Does URL-prefix include http and https?
No. It covers only the exact prefix, including protocol.
How do I verify a Domain property?
With a DNS record, except for Google-hosted sites that verify automatically.
Can I use both?
Yes. Google notes many sites combine them.
How many properties can I have?
Up to 1,000 per account.
When does data appear?
Usually within a few days of adding the property.
Do I need to re-verify a re-added property?
Not if it still has one verified owner.
Coverage, syntax, verification, limits and the combine-both advice come from Google’s help page. The decision table, step-by-step routine, WordPress notes, troubleshooting table and checklists are my own.