Google Search Console: Domain Property vs URL-Prefix Property
When you open Google Search Console and click "Add property," you are immediately asked to choose between two fundamentally different ways to represent your website: a Domain property or a URL Prefix property. The choice affects how much data you see, how you verify ownership, who you can share access with, and how completely you can monitor your site's search performance. Getting this decision wrong means staring at incomplete data for months before realizing the gap.
Two Property Types in GSC
Google Search Console has offered two distinct property types since 2019. The Domain property is DNS-verified and aggregates data across every protocol and subdomain variation of your root domain in a single view. The URL Prefix property is the older model: it captures data only for the exact URL pattern you specify, treating each variation — http, https, www, non-www — as a separate entity. Both types report the same underlying signals (impressions, clicks, index coverage, sitemaps), but Domain properties collect all of that data under one roof, while URL Prefix properties give you a narrowly scoped slice.
Understanding this distinction is not merely academic. Sites that run only a URL Prefix property for https://www.example.com/ will silently miss all data from http://example.com/, https://example.com/, blog.example.com/, and any other variation. If your redirects are imperfect, that missing data represents real crawl activity and real coverage issues you cannot see.
What Domain Property Covers
A Domain property encompasses every URL that belongs to your root domain. That means https://example.com/, http://example.com/, https://www.example.com/, http://www.example.com/, blog.example.com/, shop.example.com/, and any other subdomain — all aggregated into one unified property. Google collects impressions, clicks, crawl data, sitemap reports, and index coverage from every one of these variations and surfaces them together.
This is especially valuable for sites that have not yet perfected their redirect configuration. Even if you have set up canonical tags pointing to the https://www version and 301 redirects from http, Googlebot will still occasionally encounter and crawl the other variants. A Domain property captures those crawls in your coverage report, letting you identify redirect chains, soft-404s, or crawl budget leakage on variants you thought were fully suppressed.
Performance data (the Search Results report) also aggregates across all variants. If some old http links are still driving impressions, you will see those clicks in your Domain property data. In a URL Prefix property scoped to https://www, those impressions are simply invisible.
What URL Prefix Property Covers
A URL Prefix property covers only the URLs that begin with the exact string you enter. If you enter https://www.example.com/, you see data only for URLs matching that prefix. Google treats https://example.com/ as a completely different property — even though most browsers and most users consider them the same website. A URL Prefix property does not automatically include subdomains. blog.example.com/ would need its own separate URL Prefix property.
You can use URL Prefix properties to scope data to a specific subdirectory. https://www.example.com/blog/ is a valid URL Prefix entry, and it will report only on URLs within that blog path. This is occasionally useful for large sites where different teams own different content sections and need isolated reporting — though in most cases, filtering a Domain property by URL path achieves the same result without the overhead of managing multiple properties.
Verification Methods
The most important practical difference between the two property types is how you prove ownership to Google.
Domain property: Only one verification method is available — a DNS TXT record. You must log in to your domain registrar (GoDaddy, Namecheap, Cloudflare, or whichever registrar holds your domain), add the TXT record Google provides, and wait for propagation. DNS changes typically propagate within a few minutes on modern providers, but can take up to 48 hours in rare cases. Because DNS ownership inherently proves you control the entire domain (all subdomains and protocols), Google accepts this as sufficient proof for the broader Domain property scope.
URL Prefix property: Five verification methods are available, which makes it accessible even when you cannot touch DNS settings. You can verify with: (1) an HTML file uploaded to the root of your web server, (2) an HTML meta tag placed in the <head> of your homepage, (3) a Google Analytics tracking snippet already installed on the site, (4) a Google Tag Manager container tag, or (5) a DNS TXT record (the same method used for Domain properties). If you are an agency or developer given access to the CMS but not to DNS or the server, the meta tag or Analytics methods are often the fastest path.
When to Use Domain Property
The Domain property is the right choice for the vast majority of modern websites. It is the recommended option for any site owner who controls their DNS settings and wants complete, accurate data. Specific situations where Domain properties are clearly superior:
- You want a single consolidated view of all search performance data without manually reconciling data across multiple URL Prefix properties.
- Your site has ever run on http, non-www, or multiple subdomains — even if you have since migrated — because old crawl data and residual links may still generate activity on those variants.
- You run a main site plus subdomains (blog, shop, support) and want a unified index coverage report.
- You want to be sure your sitemap submissions are complete and not accidentally scoped to only one URL variant.
If you are setting up GSC for the first time and can access your DNS, start with a Domain property. You can always add URL Prefix properties later for specific use cases.
When to Use URL Prefix Property
URL Prefix properties remain useful in three specific scenarios:
- Scoped contractor access: If you need to give an SEO agency or freelancer access to data for one subdomain only — say
shop.example.com/— you can add a URL Prefix property for that subdomain and grant them access to that property alone. This is not possible with a Domain property, which grants access to all subdomains simultaneously. - Staging vs production comparison: Adding a URL Prefix property for
https://staging.example.com/lets you monitor what Google is doing with your staging environment separately from your production Domain property. - No DNS access: If you manage a site but genuinely cannot modify DNS records — for example on some corporate intranets or shared hosting setups where the registrar is controlled by another team — a URL Prefix property with HTML file or meta tag verification may be your only option.
How to Set Up a Domain Property
Setting up a Domain property takes about five minutes if you have your DNS provider login ready.
- Go to Google Search Console (search.google.com/search-console) and sign in with the Google account that should be the property owner.
- Click the property selector dropdown at the top left and choose Add property.
- In the "Select property type" screen, choose Domain on the left side.
- Enter your domain name without any protocol prefix — for example,
example.comnothttps://example.com. Click Continue. - Google will display a DNS TXT record value. Copy it exactly.
- Log in to your domain registrar (Cloudflare, GoDaddy, Namecheap, etc.) and navigate to DNS settings for your domain.
- Add a new TXT record with the host set to
@(or blank, depending on your registrar) and paste the Google-provided value as the record value. - Return to GSC and click Verify. If DNS has propagated, verification completes immediately.
Data collection begins as soon as the property is verified. Historical data going back up to 16 months becomes available within a day or two as Google indexes your property configuration.
How to Set Up a URL Prefix Property
A URL Prefix property setup is similar but requires the exact URL you want to monitor.
- In Google Search Console, open the property selector and click Add property.
- Choose URL prefix on the right side of the property type screen.
- Enter the full URL with protocol — for example,
https://www.example.com/. Include the trailing slash. Click Continue. - Select your preferred verification method from the list: HTML file, HTML tag, Google Analytics, Google Tag Manager, or DNS record.
- If using the HTML tag method, copy the meta tag and paste it into the
<head>section of your homepage template. Save and deploy the change. - If using the HTML file method, download the provided file and upload it to the root of your web server so it is accessible at
https://www.example.com/googleXXXXXXXX.html. - Return to GSC and click Verify. Google will fetch the verification signal. If found, the property is verified immediately.
Can You Have Both?
Yes — and many professional SEO setups include both. Having a Domain property alongside one or more URL Prefix properties is fully supported by Google. Each property collects and reports data independently; there is no overlap or double-counting issue in the way you query each property.
A common configuration is: one Domain property as the primary monitoring view, plus URL Prefix properties for individual subdomains that are managed by separate teams or agencies. For example, you might maintain example.com as a Domain property for holistic monitoring, and also have https://blog.example.com/ as a URL Prefix property so your content team can have access to their section without seeing the full site's data.
The Domain property should be your primary reference for overall site health, index coverage reports, and sitemap management. URL Prefix properties work well as secondary scoped views for specific purposes.
Common Mistakes
Several recurring errors appear when site owners set up GSC properties without understanding the distinction between property types.
Adding only a URL Prefix property and missing www/non-www data. This is the most common mistake. A site owner adds https://www.example.com/ as a URL Prefix and monitors that for months, unaware that significant traffic and crawl activity on https://example.com/ is not being reported. If canonicals or redirects are misconfigured, these variants can accumulate index coverage errors that go undetected.
Using a Domain property when you need to share partial access. Domain properties grant access across all subdomains. If you add an agency as a Full User on your Domain property, they can see data for every subdomain — including internal tools, staging environments, or other parts of the business you may not want them to access. In those cases, a URL Prefix property scoped to the relevant subdomain is the correct choice.
Forgetting to submit sitemaps to the Domain property. After verifying a Domain property, some owners submit their sitemap only to an existing URL Prefix property out of habit. Sitemaps should be submitted to the Domain property directly so Google associates the sitemap with the broadest verified scope.
Confusing property type with protocol. A Domain property for example.com automatically covers both http and https. You do not need to add http://example.com as a separate Domain property — doing so would simply duplicate the same Domain property.