Domain Property vs. URL Prefix in Google Search Console: What You Need to Know

When you set up Google Search Console (GSC), one of the first choices you face is whether to verify a Domain Property or a URL Prefix Property. On the surface, they sound similar. But once you start digging into performance reports, coverage issues, and backlink tools, the differences become clear — and they matter for your SEO strategy.

In this article, we’ll explore the key differences, why the numbers often don’t match, and how to use both properties strategically to get the most accurate picture of your website’s presence in Google Search.

What Is a Domain Property?

Think of the Domain Property as the master lens for your entire domain. Once verified via a DNS TXT record, it automatically covers:

• http://example.com

• https://example.com

• http://www.example.com

• https://www.example.com

• Any subdomains like blog.example.com or shop.example.com

This gives you comprehensive data in one place. For example:

• If your site migrated from http to https, the Domain Property will include historical data from both versions.

• If you accidentally still have a few www. pages indexed, those clicks will show up in the Domain Property.

The downside? Because it rolls everything together, it can be harder to isolate issues or track your preferred canonical version without adding filters.

What Is a URL Prefix Property?

By contrast, a URL Prefix Property is much narrower. It covers only the specific version you enter, such as:

• https://example.com/

That means:

• It will not include http://example.com

• It will not include https://www.example.com

• It will only include URLs that begin exactly with https://example.com/

This gives you a clean, focused dataset. You’ll see exactly how your live, canonical site performs without the noise of old or alternate versions.

Most site owners today should be tracking https:// as their primary URL Prefix Property, since Google strongly favors HTTPS as a ranking factor.

Why the Numbers Don’t Match

It’s common for SEOs and site owners to compare Domain vs. URL Prefix data and panic when the totals don’t line up. Here’s why:

1. Scope of Data

• Domain Property = all versions combined

• URL Prefix = only one version

If you’ve recently migrated to HTTPS or switched from www to non-www, the Domain Property will still reflect activity from the old versions.

2. Canonicalization

Google doesn’t always use the URL you prefer as the canonical. If it selects http://example.com/page instead of https://example.com/page, clicks may only appear in the Domain Property.

3. Index Coverage

The Domain Property may reveal that legacy pages are still indexed — pages you thought were gone may still show in search results.

4. Link Reports

Backlinks often point to multiple variants of your site. The Domain Property aggregates them, while the URL Prefix splits them up.

👉 The result: Domain Property numbers are usually larger, but URL Prefix numbers are usually more accurate for current SEO reporting.

How to Check If Old Versions Still Get Traffic

Want to know if http:// or www. are still causing issues? Here’s how:

1. Open the Domain Property in GSC.

2. Go to Performance → Search Results.

3. Add a Page Filter:

   • Filter for http:// → see if insecure pages still get clicks.

   • Filter for www. → see if the www version still shows up.

   • Filter for subdomains like m. if you’ve had a mobile site in the past.

4. Compare those results against your https:// property.

5. Use the Coverage Report to check if old URLs are still indexed.

6. Use the URL Inspection Tool on outdated URLs to confirm whether Google is redirecting and consolidating them correctly.

If you find traffic going to outdated versions, it’s a sign that you need to:

• Tighten up 301 redirects

• Update internal links to point only to HTTPS versions

• Submit a clean sitemap with the preferred version only

Why You Can Only Disavow Links in URL Prefix Properties

Here’s a quirk that confuses many SEOs: toxic backlink disavows can only be submitted under a URL Prefix Property, not a Domain Property.

Why?

• The Disavow Tool is a legacy feature built before Domain Properties existed.

• It expects a single, specific URL pattern like https://example.com/.

• A Domain Property covers too many versions (http, https, subdomains), and Google doesn’t want to risk applying disavows too broadly.

Best practice:

• Submit your disavow file under your main https:// prefix.

• Only use additional disavows for unique subdomains if they have their own backlink profiles.

Best Practices for Using Both Properties

To get the best of both worlds, here’s how to use Domain and URL Prefix Properties together:

• Monitor big picture trends in the Domain Property. This shows whether legacy versions are still active, and whether your entire domain is being crawled properly.

• Do tactical SEO work in the URL Prefix Property. This is where you’ll check indexing, manage sitemaps, submit disavow files, and measure performance on your canonical site.

• Report with context. Always note whether you’re showing Domain Property or URL Prefix data to avoid confusion. A drop in prefix numbers may just mean consolidation, not lost traffic.

Key Takeaway

Think of it this way:

• Domain Property = the wide-angle lens. It shows you everything — even legacy or subdomain traffic you may not want.

• URL Prefix Property = the magnifying glass. It shows you the clean, canonical version you care about.

For accurate SEO reporting, rely on the URL Prefix Property. But keep the Domain Property around as a diagnostic tool to spot issues with migrations, redirects, and stray backlinks.

Over time, with proper canonicalization and redirect hygiene, almost all of your traffic should consolidate into the HTTPS URL Prefix Property — and that’s exactly where you want it.