Google Search Console Domain vs URL Prefix Property: Which Should You Choose?

· About

Google Search Console Domain vs URL Prefix Property: Which Should You Choose?

When you first verify a site in Google Search Console (GSC), you face an early decision that affects every report, API call, and indexing workflow going forward: should you add a Domain property or a URL-prefix property? The choice is not reversible in the sense that you cannot merge them — you can add both, but they behave differently, and picking the wrong one creates blind spots in your data.

Domain Property vs URL-Prefix Property

Domain Property

A Domain property covers all protocols and subdomains of a root domain. For example, a Domain property for example.com includes:

  • https://example.com/
  • https://www.example.com/
  • https://blog.example.com/
  • http://example.com/ (legacy HTTP URLs)

Verification requires a DNS TXT record at the domain registrar level. You cannot verify a Domain property with an HTML file or meta tag alone.

URL-Prefix Property

A URL-prefix property covers only URLs that start with the exact prefix you specify. Examples:

  • https://www.example.com/ — does not include https://example.com/ without www.
  • https://example.com/blog/ — only the /blog/ subdirectory.

Verification supports multiple methods: HTML file upload, HTML meta tag, Google Analytics, Google Tag Manager, and DNS.

Which Should You Choose?

Choose a Domain Property If…

  • You control DNS and want a single view of all subdomains and protocols.
  • Your site serves both www and non-www, or uses multiple subdomains (blog, shop, docs).
  • You plan to use the Search Console API for automated reporting across the entire domain.
  • You want to avoid gaps when HTTP URLs still appear in Google's index.

Choose a URL-Prefix Property If…

  • You do not have access to DNS (common on shared hosting or client-managed domains).
  • You only care about one specific section of a large site (e.g., a subdirectory you manage).
  • You need the fastest verification path via HTML tag or file upload.
  • You are testing GSC on a staging subdomain and do not want it mixed with production data.

Common Mistakes

Verifying Only One Variant

Many site owners verify https://www.example.com/ as a URL-prefix property but forget that Google may also index https://example.com/ (non-www). Search data for the non-www variant will not appear in that property. A Domain property solves this automatically.

Mixing HTTP and HTTPS

If your site migrated from HTTP to HTTPS but old HTTP URLs remain in the index, a URL-prefix property for HTTPS only will miss HTTP performance data. Again, a Domain property captures both.

Assuming One Property Is "Enough" for API Access

API integrations (Search Analytics pulls, URL inspection automation) are scoped to the property you authenticate against. If your API script uses a URL-prefix property but your sitemap includes URLs outside that prefix, you will get incomplete or empty results.

Can You Use Both?

Yes — and many experienced operators do. A typical setup:

  1. Domain property for holistic monitoring, DNS-level verification, and API access.
  2. URL-prefix property for quick verification during migrations or when handing off access to a contractor who cannot modify DNS.

Data between the two is not automatically merged in the UI, but the Domain property gives you the authoritative full-domain view.

Verification Step-by-Step (Domain Property)

  1. In GSC, click Add property and select Domain.
  2. Enter your root domain (e.g., example.com) without protocol or path.
  3. Copy the TXT record Google provides.
  4. Log in to your DNS provider (Cloudflare, Route 53, Namecheap, etc.).
  5. Add a TXT record at the root (@) with the value Google supplied.
  6. Wait for DNS propagation (minutes to 48 hours) and click Verify in GSC.

Verification Step-by-Step (URL-Prefix Property)

  1. In GSC, click Add property and select URL prefix.
  2. Enter the full prefix including protocol and trailing slash (e.g., https://www.example.com/).
  3. Choose a verification method. HTML tag is the most common for CMS platforms like Blogger, WordPress, and static site generators.
  4. Paste the meta tag into your site's <head> section or use a plugin.
  5. Click Verify.

Impact on Sitemaps and Indexing

Sitemaps are submitted per property. For a Domain property, submit sitemaps that list URLs across your entire domain. Google will associate each URL with the correct property automatically.

For URL-prefix properties, only submit sitemaps containing URLs that fall within the verified prefix. Submitting a sitemap with out-of-scope URLs will result in warnings or ignored entries.

Bottom Line

If you have DNS access, start with a Domain property. It is the most complete and future-proof option. Add URL-prefix properties only when you have a specific operational reason — limited access, subdirectory ownership, or staging isolation.

Related Links

No comments