Domain vs. URL Prefix in Google Search Console: Which Should You Choose?
You've just logged into Google Search Console for the first time — or you're setting up a new property — and Google immediately hits you with a fork in the road. On the left: Domain. On the right: URL prefix. The labels are brief, the help text is cryptic, and your gut says to just pick one and move on.
That impulse to click quickly is understandable. But the choice you make here determines how much search data you'll actually see, how you prove ownership to Google, and whether you'll spend the next six months wondering why your numbers don't add up. It's one of the most consequential setup decisions in SEO — and it's routinely made too fast.
This guide breaks down both property types in plain English, explains the verification processes behind each, and gives you a clear recommendation for most websites. By the end, you'll know exactly what to click and why.
What Is a Property in Google Search Console?
Before getting into the two types, it helps to understand what a "property" actually is. In Google Search Console (GSC), a property is simply a representation of your website — or a section of it — that Google uses to organize and display search performance data. Every piece of information you see inside GSC (clicks, impressions, crawl errors, index coverage) is scoped to whatever property you've set up.
This matters because Google treats different versions of your website as entirely separate entities. http://example.com, https://example.com, http://www.example.com, and https://www.example.com are four distinct websites as far as GSC is concerned — unless you tell it otherwise. The property type you choose determines whether those versions are unified under one roof or tracked separately. Content Ladder
The Domain Property: Full Coverage, One View
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. Bluehost
So if your root domain is yoursite.com, a Domain property would consolidate data from http://yoursite.com, https://yoursite.com, http://www.yoursite.com, https://www.yoursite.com, https://blog.yoursite.com, https://shop.yoursite.com, and any other subdomain you're running — all automatically, without creating separate properties for each.
Using a domain property gives you a comprehensive view of your entire domain, including all subdomains and protocols. This allows you to manage and monitor everything in one place. It also helps future-proof your reporting: the domain property type will help you simplify management by automatically including new subdomains and protocol changes without needing manual updates or separate properties. SEOTestingSEOTesting
There's one more practical benefit worth calling out. A domain property will report URLs that serve HTTP pages that appear in search results, giving you the opportunity to fix these with the necessary redirects to the HTTPS versions. That kind of visibility is easy to miss if you're only tracking one protocol. SEOTesting
The Trade-Off: DNS Verification Only
The Domain property's power comes with a technical price. The domain property 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. Bluehost
This step trips up a lot of people who aren't familiar with DNS management. You'll need access to your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) or wherever your domain's name servers are pointed. The DNS verification process for domain properties, although a little more technical, is more secure and ensures you control the entire domain. SEOTesting
One thing to watch out for: if your DNS settings are altered, the verification can fail, and you'll need to re-verify your ownership, which can be inconvenient during hosting changes or migrations. SEOTesting
The URL Prefix Property: Targeted, Flexible, Faster to Set Up
A URL Prefix in Google Search Console is specific to URLs with the designated prefix, including the protocol (either HTTP or HTTPS). For example, if you set up a URL prefix property for "http://example.com," it will only include URLs that start with that exact prefix. It won't include URLs that start with "https://example.com" or "http://www.example.com" because they don't match the specified prefix. Content Ladder
That precision cuts both ways. On one hand, it lets you isolate a specific section of your site and see its performance without other variations muddying the data. This is especially useful if you want to focus on a particular part of your site, such as a blog or a shopping section. SEOTesting
On the other hand, if you set up a URL prefix for only https://www.yoursite.com thinking you're covered, you could be missing all the traffic going to https://yoursite.com (without the www), any HTTP version, or any subdomains. That's a data gap that can quietly distort your reporting for months.
The Advantage: Multiple Verification Methods
Unlike domain properties, which require DNS verification, a URL prefix property can be verified using more accessible methods, such as an HTML file upload, meta tag, Google Analytics, or Google Tag Manager. SEOTesting
This flexibility is the URL prefix's biggest practical advantage. If you're managing a site on a platform where you can't touch DNS settings — or you're an agency that needs to verify a client's property quickly without waiting on IT — the HTML tag or Analytics method can have you up and running in minutes.
Side-by-Side: Domain vs. URL Prefix
FeatureDomain PropertyURL Prefix PropertyCovers all subdomains✅ Yes — automatically❌ No — one subdomain onlyCovers HTTP & HTTPS✅ Yes — both protocols❌ No — one protocol onlyNew subdomains auto-included✅ Automatic❌ Must create new propertiesVerification methodsDNS TXT record onlyHTML file, meta tag, GA, GTM, DNSTechnical difficultyModerate (DNS access needed)Low–Moderate (varies by method)Best forFull-site, long-term SEO trackingSpecific sections or limited accessRecommended as primary✅ YesSupplementary use
Which One Should You Choose?
A domain property minimizes the risk of missing data and is the recommended default for most site owners and SEO professionals. SEO Specialist USA
If you have access to your domain registrar or DNS settings, start with the Domain property every time. It future-proofs your data collection, covers every version of your site from day one, and eliminates the risk of protocol or subdomain gaps fragmenting your reporting.
URL prefix properties are useful in specific cases, but they should not replace a domain property for full-site SEO tracking. For the most accurate insights, use both properties: rely on the domain property for primary SEO reporting, and use URL prefix properties for testing, validation, or focused analysis. SEO Specialist USA
Use a URL Prefix instead when:
You don't have DNS access and need to verify quickly
You want isolated data for a specific subdirectory (e.g., /blog/)
You're an agency verifying a property before getting DNS credentials
Your subdomains serve genuinely distinct products with separate reporting needs
How to Verify a Domain Property (Step by Step)
The DNS verification process is the part most people find intimidating. Here's exactly what it looks like.
Step 1 — Open GSC and Add a Property. Go to search.google.com/search-console. Click the property selector in the top-left, then "Add property." In the modal, select the Domain option on the left side.
Step 2 — Enter your root domain without protocol or www. Type your domain exactly as it appears at your registrar: yoursite.com, not https://www.yoursite.com. Click Continue.
Step 3 — Copy your unique TXT record. When asked to verify your Domain property in Search Console, choose TXT for Select record type in the Search Console verification popup. Search Console will give you a string value TXT record to use in the next step. It looks something like google-site-verification=abc123XYZ…. Keep this tab open. Google Support
Step 4 — Log in to your DNS provider. This is wherever you bought your domain — GoDaddy, Namecheap, Cloudflare, Squarespace, etc. Navigate to your domain's DNS settings. Look for something like DNS Records, Domain Management, or Name Server Management. Google Support
Step 5 — Add a TXT record. Click "Add Record" and select TXT as the type. For the Host/Name property, either leave this blank, or set as "@", as described in the documentation for your DNS provider. For the Value property, provide the Search Console TXT record string that you generated earlier. Set TTL to 3600 or use the default. Save the record. Google Support
Step 6 — Wait for propagation. DNS changes can take anywhere from a few minutes to 48 hours to propagate globally. It's often much faster, but be prepared to wait if verification doesn't go through immediately. If you're on Cloudflare, propagation is often near-instant. Sabine Blankevoort
Step 7 — Return to GSC and click Verify. If verification fails on the first attempt, wait a bit and try again. You can check whether the record is live using dnschecker.org with a TXT lookup before re-attempting.
Important: The unique TXT record must stay in your domain's DNS settings until Google detects it and verifies ownership. Once verified, the TXT record can be safely removed. Removing it before Google verifies ownership will cause the verification to fail. Google Support
A Note on DNS vs. Your Hosting Provider
One point of frequent confusion: if your domain registrar (like GoDaddy) is separate from your host (like SiteGround), the record belongs wherever your name servers point. So if GoDaddy owns your domain but your name servers are pointed to SiteGround, add the TXT record in SiteGround — not GoDaddy. Not sure where your name servers point? Check with your host or look up your domain at whois.domaintools.com. Yourcreativecontent
What Happens After Verification?
Once verified, your Domain property starts collecting data immediately — or rather, it surfaces data Google has already been collecting. If you already have your website versions added to GSC, you will not need to wait for indexation and other info to appear. After verifying your domain property, all data will be immediately available. MarketingSyrup
From there, your primary GSC reports — Performance, Index Coverage, Sitemaps, Core Web Vitals — will reflect your entire domain across all protocols and subdomains in a single unified view. No more toggling between four different properties trying to piece together the full picture.
After verifying your domain property: explore the Performance tab to view impressions, clicks, and average click-through rates, and the Indexing tab to check the status of your site's pages and sitemaps. Shoutex
The Bottom Line
The Domain property is the right choice for the vast majority of websites. It captures everything, requires only one-time DNS verification, and scales automatically as your site grows. The URL Prefix property has its place — particularly for focused analysis or when DNS access isn't available — but it works best as a complement to a Domain property, not a replacement for it.
If you've already set up URL prefix properties and been wondering why your data feels incomplete, that's likely why. The good news: you can add a Domain property at any time without losing your existing properties or historical data.
Sources
Google Search Console Help — Verify your site ownership: support.google.com/webmasters/answer/9008080
SEOTesting — Domain vs URL Prefix in Google Search Console: seotesting.com/google-search-console/domain-vs-url-prefix
Bluehost Blog — Google Search Console: Domain vs URL Prefix: bluehost.com/blog/gsc-domain-vs-url-prefix
Content Ladder — Difference Between Domain and URL Prefix in GSC: contentladder.in/blog/difference-between-domain-and-url-prefix-in-google-search-console
Sabine Blankevoort — Verifying a Domain Property in GSC via DNS: sabineblankevoort.com/blog/verify-domain-property-in-google-search-console-via-dns
Marketing Syrup — How to Verify Domain Property in GSC via TXT DNS: marketingsyrup.com/how-to-verify-domain-property-in-google-search-console-via-dns
Your Creative Content — How to Add a Google Search Console TXT Record: yourcreativecontent.com/blog/how-to-add-a-google-search-console-txt-record-step-by-step-for-every-platform
Ready to get your SEO foundation right from the start?
Setting up Google Search Console correctly is just one piece of a smart digital strategy. At Ritner Digital, we handle the technical setup, ongoing monitoring, and strategic optimization so you can focus on running your business.
Get in touch at ritnerdigital.com → Contact
Frequently Asked Questions
Do I need both a Domain property and a URL Prefix property?
Not necessarily, but it can be useful. The Domain property should be your primary setup — it captures everything. A URL Prefix property on top of that is optional and only worth adding if you want to isolate performance data for a specific section of your site, like a blog or shop subdirectory. For most small to mid-size websites, the Domain property alone is enough.
Can I switch from a URL Prefix property to a Domain property later?
Yes, and you won't lose any data. Adding a Domain property doesn't delete or replace your existing URL Prefix properties — they'll all coexist in your GSC account. Your historical data in the URL Prefix properties stays intact. Going forward, the Domain property will be the one you rely on for full-site reporting.
What if I don't have access to my DNS settings?
Start with a URL Prefix property using the HTML tag or Google Analytics verification method. Then, once you gain DNS access — either yourself or through your developer or host — come back and add the Domain property. Many agencies do exactly this when onboarding a new client before getting full technical access.
Why does my Domain property show different numbers than my URL Prefix property?
Because they're measuring different things. Your Domain property includes traffic from all subdomains and both HTTP and HTTPS versions of your site. Your URL Prefix property only captures the exact URL variation you set up. If you see more data in the Domain property, that's not an error — it's the point. You were missing that data before.
How long does DNS verification take?
It varies. Some DNS providers like Cloudflare propagate changes in seconds. Others can take anywhere from a few minutes to 48 hours. If GSC throws a verification error right away, don't panic — just wait an hour and try again. You can check whether your TXT record is live yet by looking it up at dnschecker.org before clicking Verify again.
Will Google re-verify my Domain property automatically?
Yes — as long as your TXT record stays in your DNS settings. Once verified, Google periodically checks that the record is still there to confirm continued ownership. If the record is accidentally deleted (say, during a DNS migration), your verification can lapse and you'll need to re-verify. It's worth double-checking after any hosting or registrar changes.
Can I add multiple users to a Domain property?
Yes. User management for Domain properties works the same way as for URL Prefix properties — you can add users with different permission levels (Owner, Full User, Restricted User). Those added users won't need to go through the DNS verification process themselves; they simply get access once you've granted it.
What's the difference between a Domain property and a domain-level property?
This one confuses people because the terminology is similar. A Domain property (the one covered in this post) is set up without a protocol — just yoursite.com— and covers everything underneath it. A "domain-level property" is an older term sometimes used to describe any property that doesn't include a path string, including entries like https://example.com. Google's own documentation draws this distinction, so if you're reading older GSC guides, keep that in mind.
Should I set up separate properties for my subdomains?
Generally, no — that's one of the main problems the Domain property solves. If you set up a Domain property for yoursite.com, data from blog.yoursite.com, shop.yoursite.com, and any other subdomain is automatically included. Separate subdomain properties only make sense if you have a specific reason to track a subdomain in complete isolation with its own reporting and user access.
Does setting up Google Search Console affect my rankings?
No. GSC is a monitoring and diagnostic tool — it has no direct influence on how Google ranks your pages. What it does do is give you the data to make informed decisions that can improve your rankings over time: finding crawl errors, identifying underperforming pages, submitting sitemaps, and spotting indexing issues before they become serious problems.
Have a question that isn't covered here? Reach out to the Ritner Digital team — we're happy to help.