Google Search Console: Domain vs URL Prefix

Key highlights

• Understand the core differences between Domain properties and URL-prefix properties to choose the right setup for your site.
• Explore how Domain properties aggregate data across all subdomains and protocols for a complete, overall SEO overview.
• Learn the specific verification methods required for each property type to ensure seamless access to your search data.
• Uncover the benefits of using URL-prefix properties for granular tracking of specific site sections or directories.
• Discover how to manage your search presence effectively by balancing both property types within your technical strategy.

When you add a website to Google Search Console (GSC), one of the first decisions you face is choosing between two property types: the domain property and the URL prefix property. This choice shapes how much data you see, how you verify ownership and how comprehensively Google tracks your site’s performance. Understanding the GSC domain vs URL prefix distinction is not merely a technical formality, it directly influences the quality of insights you can draw from one of the most powerful free tools in your SEO arsenal.

Whether you are a seasoned SEO professional or a business owner managing your first website, selecting the wrong property type can leave critical data gaps in your reporting. This article breaks down everything you need to know about the difference between domain and URL prefix in GSC, from how each property works to when you should use one over the other.

Quick glance: Key differences between domain and URL prefix in GSC

Feature	Domain property	URL prefix property
Coverage	Tracks the entire domain including all subdomains and protocols	Tracks only the specific URL prefix entered
Includes subdomains	Yes	No
Includes protocols	Yes	No, the protocol must match exactly
Verification method	DNS verification only	Multiple methods such as HTML file upload, HTML tag, DNS or Google Analytics
Setup complexity	Slightly more technical because DNS access is required	Easier and quicker to set up
Data completeness	Provides unified and comprehensive data across the domain	Data may be split across multiple properties
Best use case	Full website monitoring and SEO performance tracking	Tracking specific sections of a website or when DNS access is unavailable
Property scope	One property can cover the entire domain	Separate properties may be required for different protocols or subpath

What is a domain property in Google Search Console?

A domain property in Google Search Console aggregates data from every variation of your website under a single root domain. When you create a domain property, GSC captures performance data across all subdomains, all protocols (HTTP and HTTPS) and all URL paths associated with that root domain.

For example, if your root domain is [yourdomain].com, a domain property would consolidate data from:

• www.[yourdomain].com
• blog.[yourdomain].com
• shop.[yourdomain].com
• http://[yourdomain].com
• https://[yourdomain].com
• https://www.[yourdomain].com

This makes the domain property the most comprehensive property type available in GSC. You get a bird’s-eye view of your entire web presence under one roof, eliminating the need to switch between multiple properties to piece together fragmented performance data.

How verification works for a domain property?

• The domain property overall requires DNS verification, which involves adding a specific TXT record to your domain’s DNS settings.
• You must complete this process through your domain registrar or hosting provider, as it is the only method GSC accepts for domain properties.
• While this method is more technically involved than some URL prefix verification options, it is essential for domain-level access.

• Once the TXT record is added and verified, GSC confirms ownership of the entire domain namespace.
• This verification grants access to aggregated data across every subdomain and protocol variation, providing an overall view of your site’s performance.
• This serves as a significant advantage for sites with complex structures or multiple subdomains serving different content categories.

What data does a domain property include?

A domain property pulls together impressions, clicks, average position and click-through rates from all versions of your domain. If you have historically operated both HTTP and HTTPS versions of your site or recently migrated from one subdomain configuration to another, the domain property ensures none of that historical data is lost or siloed. Google treats all these variations as part of the same unified property.

What is a URL prefix property in Google Search Console?

A URL prefix property is more specific and narrower in scope. It tracks data only for the exact URL prefix you specify, including all pages and paths that begin with that precise URL string. Unlike a domain property, a URL prefix property does not automatically extend to subdomains or alternative protocols unless you add them separately.

For instance, if you add https://www.[yourdomain].com as a URL prefix property, GSC will only track pages that begin with exactly that string. It will not capture data from http://www.[yourdomain].com, https://[yourdomain].com (without the www) or any subdomains like blog.[yourdomain].com.

Verification options for URL prefix properties

One of the key advantages of the URL prefix property is the variety of verification methods available. You can verify ownership using any of the following:

• HTML file upload: Upload a Google-provided HTML file to your website’s root directory.
• HTML meta tag: Add a verification meta tag to the <head> section of your homepage.
• Google Analytics: Use your existing Google Analytics tracking code for verification.
• Google Tag Manager: Verify through your GTM container snippet.
• DNS record: Add a TXT or CNAME record via your domain registrar (also available for URL prefix).

This flexibility makes URL prefix properties easier to set up for users who do not have direct access to their domain’s DNS settings. Developers working within a CMS environment or marketing teams without server-level access will often find this the more practical option.

When does a URL prefix property make sense?

A URL prefix property works well when you need to track a specific subdirectory or section of a larger site. For example, if you manage a company blog hosted at https://www.[yourdomain].com/blog and you want to isolate that section’s performance data independently, a URL prefix property lets you do exactly that. It provides focused visibility into a specific segment of your site without mixing in data from unrelated sections.

The key difference between domain and URL prefix in GSC

Understanding the difference between domain and URL prefix in GSC comes down to three core dimensions: scope of data, verification complexity and use case alignment.

1. Scope of data collection

The domain property captures the widest possible dataset. Every URL under your root domain, regardless of subdomain, protocol or path, is included in the property’s reporting. This makes it ideal for understanding your site’s overall search performance without gaps caused by fragmented property configurations.

The URL prefix property, by contrast, is scoped to a precise URL string. Any URL that does not begin with that exact string is excluded from the property’s data. If your site has multiple subdomains or operates on both HTTP and HTTPS, you would need separate URL prefix properties for each variation to achieve the same coverage a single domain property provides.

2. Verification requirements

Domain properties demand DNS-level verification. This means you or your hosting provider must access your DNS management panel and add a TXT record. While this is straightforward for most hosting environments, it can be a barrier if your DNS is managed by a third party or if you do not have the necessary permissions.

URL prefix properties offer multiple verification pathways, as outlined above. This flexibility is one of the primary reasons many users default to URL prefix properties when first setting up GSC. However, the convenience comes at the cost of data completeness.

3. Data aggregation and reporting accuracy

If your site has both http://[yourdomain].com and https://www.[yourdomain].com active simultaneously (even during a migration), a URL prefix property will only show data for the specific version you added. You could be missing a significant portion of your impressions or clicks without realizing it. A domain property eliminates this risk entirely by consolidating all versions.

For sites that have undergone migrations, from HTTP to HTTPS, from non-www to www or from one subdomain structure to another, the domain property provides historical continuity that URL prefix properties cannot replicate without adding and cross-referencing multiple separate properties.

4. Subdomain handling

This is one of the most critical distinctions in the Google Search Console domain vs URL prefix comparison. A domain property automatically includes all subdomains: www, blog, shop, support and any others. A URL prefix property is completely blind to subdomains unless each one is added as its own separate property.

For businesses running eCommerce stores on a subdomain, regional sites on country-code subdomains or support portals on dedicated subdomains, the domain property is the only way to get a unified performance view in a single dashboard.

Domain vs URL prefix: which one should you use?

The answer depends on your specific goals, site architecture and level of DNS access. Here is a practical framework to guide your decision:

Choose a domain property if:

• You want the most complete and accurate picture of your site’s search performance.
• Your site operates on multiple subdomains or has historically used both HTTP and HTTPS.
• You have recently completed or are planning a site migration.
• You have full access to your domain’s DNS settings.
• You manage a large site where data completeness is critical for decision-making.

Choose a URL prefix property if:

• You need to isolate data for a specific section or subdirectory of your site.
• You do not have access to your domain’s DNS panel.
• You are setting up GSC for a single, consistent HTTPS version of a simple site with no subdomains.
• You need to verify quickly using methods like HTML meta tags or Google Analytics.
• You are managing a specific subdomain independently from the main site.

Can you use both simultaneously?

Yes. GSC allows you to add multiple properties for the same website. Many SEO professionals add a domain property for holistic reporting while also maintaining URL prefix properties for specific segments or subdomains that require independent monitoring. This layered approach gives you both the big-picture view and the granular, section-level insights you need to make informed optimizations.

Common mistakes to avoid when setting up GSC properties

Understanding the GSC domain vs URL prefix distinction helps you avoid several common configuration errors that can distort your data and lead to misguided SEO decisions.

1. Relying solely on a URL prefix property for a multi-subdomain site

If you add only https://www.[yourdomain].com as a URL prefix property but your blog lives at blog.[yourdomain].com, all of your blog’s search performance data is invisible in that property. Many site owners discover this gap only after noticing that their GSC data does not align with their analytics platform’s organic traffic figures.

2. Not verifying all URL variations

If you use URL prefix properties exclusively, failing to add both the www and non-www versions, as well as both HTTP and HTTPS versions, creates blind spots. Google Search Console treats each of these as a distinct property, and data from one does not automatically appear in the others.

3. Overlooking the domain property during site migrations

During a site migration — whether from HTTP to HTTPS or from one domain structure to another — tracking performance across all URL variations becomes essential. Without a domain property, you may struggle to accurately attribute ranking changes to your migration decisions versus external factors like algorithm updates.

Final thoughts

The choice between a GSC domain vs URL prefix property is more consequential than it might initially appear. The domain property offers unmatched comprehensiveness, pulling together data from every subdomain and protocol variation under your root domain into a single, unified view. The URL prefix property offers greater flexibility in verification and more precise, scoped reporting for specific site sections. For most website owners and SEO professionals seeking the most accurate, complete and actionable data, the domain property is the recommended choice, provided DNS access is available.

Understanding the difference between domain and URL prefix in GSC empowers you to configure your Search Console properties strategically rather than defaulting to whatever is easiest to set up. The right property type ensures the data you rely on for keyword analysis, ranking reports and performance tracking reflects the full reality of your site’s presence in Google Search.

If you are managing your website’s presence in Google Search Console and want professional tools that make technical tasks like DNS verification and domain management straightforward, get started with Bluehost Google Workspace today, overall, equipping your business with a professional suite ensures you have the reliable infrastructure needed to support your growth from day one.

FAQs

What is the main difference between domain and URL prefix in Google Search Console?

A domain property in GSC covers all subdomains and URL protocols under a single root domain, offering comprehensive data coverage. A URL prefix property tracks only URLs that begin with the exact prefix you specify, making it narrower in scope but more flexible to verify.

Should I use a domain property or URL prefix property in GSC?

Most site owners benefit most from a domain property because it consolidates all search data in one place. Use a URL prefix property if you need to track a specific subdirectory independently or if you do not have access to your domain’s DNS settings for verification.

Does a domain property in GSC include all subdomains?

Yes. A domain property automatically includes all subdomains (such as www, blog or shop) as well as all protocols (HTTP and HTTPS) under your root domain. This is one of its primary advantages over URL prefix properties, which must be added individually for each subdomain.

How do I verify a domain property in Google Search Console?

Domain properties can only be verified through DNS verification. You must log into your domain registrar or DNS management panel and add a TXT record provided by Google Search Console. Once Google detects the record, the domain property is verified and data collection begins.

Can I have both a domain property and a URL prefix property in Google Search Console for the same site?

Yes. GSC allows you to add multiple properties for the same website simultaneously. Many SEO professionals maintain a domain property for overall site performance monitoring while adding URL prefix properties for specific subdomains or subdirectories that require separate, focused analysis.