# Google Search Console Domain vs URL Prefix: Which to Use

[David Kaufmann](/content/author/david-kaufmann/index.html)  
July 4, 2026

Does your site need a **Domain** or a **URL-prefix** property? Put simply: most sites should run a **Domain property**, but plenty of teams run both.

If you can edit your domain's DNS, create a **Domain property.** It rolls up every subdomain and both http and https into one report, so no part of your site stays hidden. A **URL-prefix property** is best when you can't touch DNS, or when you deliberately want to track a single section, subdomain, or protocol on its own. This guide compares both and gives you a clear pick — for where this choice sits in the wider tool, see our [complete Google Search Console guide](/content/blog/google-search-console/index.html).

> A Search Console "Domain property" is not the same as your domain name. Your _domain name_ is `example.com`. A _URL_ is the full address, like `https://example.com/pets`. A _Domain property_ is a reporting container, keyed to your domain name, that gathers every URL underneath it.

In this article

## The two property types in 30 seconds

When you add a property in Search Console, you pick one of two types:

- ›**Domain property** (`example.com`) — covers every subdomain (www, blog, shop, m) and both protocols (http, https). You verify it by DNS only.
- ›**URL-prefix property** (`https://example.com`) — covers only the exact protocol and subdomain you enter. It can be verified several ways: HTML file, HTML tag, Google Analytics, Google Tag Manager, or DNS.

A Domain property rolls up your whole site; a URL-prefix property tracks one exact version

## What a Domain property covers

A Domain property is defined **without a protocol and without a path**, and it [can include subdomains](https://support.google.com/webmasters/answer/10431861). That means one property aggregates `https://www.example.com`, `https://blog.example.com`, the non-www version, and the http variants, all together. Add a new subdomain later and it's tracked automatically, with no extra setup.

The trade-off: a Domain property is [verified only by adding a DNS record](https://support.google.com/webmasters/answer/9008080) at your domain registrar. **No DNS access means no Domain property.**

## What a URL-prefix property covers

A URL-prefix property tracks only URLs that begin with the exact prefix you enter, [including the protocol](https://support.google.com/webmasters/answer/34592). Search Console treats each of these as a **separate** property:

- ›`https://example.com` and `http://example.com` (different protocol)
- ›`https://example.com` and `https://www.example.com` (different subdomain)
- ›`https://m.example.com` (a subdomain the prefix above won't capture)

The upside is verification flexibility: HTML file upload, an HTML meta tag, Google Analytics, Google Tag Manager, or DNS all work. That flexibility is why URL-prefix is the fallback **when you can't edit DNS.**

## Domain vs URL-prefix: a side-by-side comparison

|  | **Domain property** | **URL-prefix property** |
| --- | --- | --- |
| **Scope** | All subdomains + http/https, combined | Only the exact protocol + subdomain entered |
| **Verification** | DNS record only | HTML file, HTML tag, Analytics, Tag Manager, or DNS |
| **Setup & maintenance** | Needs DNS access; new subdomains auto-included | Works without DNS; a move to https or a new subdomain needs a new property |
| **Data you see** | The fullest dataset for the whole site | Only the slice that matches the prefix |
| **Best for** | Most sites, when you control DNS | No DNS access, or isolating one section/protocol |

## Which property should you choose?

Google's own team recommends creating **at least one Domain property** because it gives the most complete view, and Google has noted that site owners on URL-prefix properties were often [underestimating their traffic](https://developers.google.com/search/blog/2019/09/auto-dns-verification) before switching — because a www prefix quietly excluded other subdomains and protocols.

Can you edit your DNS? Yes → Domain property. No → URL-prefix property

Reach for a **URL-prefix property** in these cases:

- ›**You don't have DNS access.** You can't create a Domain property without it, so URL-prefix with an HTML tag or Analytics is your route in.
- ›**You want to isolate a section.** Tracking only `https://example.com/blog/` or only a `shop.` subdomain keeps that reporting clean.
- ›**You need a specific protocol or subdomain.** During an http→https migration, a URL-prefix on each version lets you watch the switch happen.
- ›**You're scoping access for a contributor.** A URL-prefix limits what an external agency or freelancer sees to one part of the site.

> Edge case worth naming: if your blog lives on a subdomain managed by a different platform, a Domain property still covers it (DNS is at the registrar level), while a www URL-prefix would miss it entirely.

## How to set up each property (step by step)

### Domain property

1. ›In Search Console, open the property selector and click _Add property_ → _Domain_.
2. ›Enter your domain without protocol or www (`example.com`).
3. ›Copy the TXT record Google provides and add it in your registrar's DNS settings (choose "Any DNS provider" if the guided flow doesn't match yours).
4. ›Save, wait for propagation, then click _Verify_.

### URL-prefix property

1. ›_Add property_ → _URL prefix_.
2. ›Enter the full address including protocol (`https://www.example.com`).
3. ›Pick a method under _Verify ownership_: HTML file, HTML tag, Analytics, Tag Manager, or DNS.
4. ›Add the token to your site (or DNS) and click _Verify_.

Google Search Console's Select property type dialog: choose Domain or URL prefix

If you're deciding which verification method fits your CMS, our [Google Search Console setup guide](/content/blog/google-search-console/index.html) walks through each one.

## Can you have both?

Yes — and many teams do. They **keep a Domain property for the complete sitewide view** and one or more URL-prefix properties to watch specific sections in isolation.

The two don't conflict, each keeps its own history, and verifying one often auto-verifies the other. The only rule of thumb: **decide which property is your source of truth for reporting**, so numbers don't get compared across different scopes by accident.

## How this maps to your SEOcrawl AI data

SEOcrawl AI connects to Search Console through OAuth and reads your live GSC data — with unlimited retention rather than Google's 16-month window. **Which property you connect decides how much of your site SEOcrawl can see.**

Connect the Domain property for the fullest dataset; use tags to rebuild per-section views

Connect the **Domain property and SEOcrawl gets the fullest dataset:** every subdomain and protocol feeding your dashboards, rank tracking, and winners/losers, so nothing is missing from the analysis. If you run a multi-country or multi-subdomain site, the Domain property plus SEOcrawl's tagging lets you **rebuild the per-section views** without losing the sitewide total — no need to split your data across separate URL-prefix properties just to see each section.

> **Connect once, see the whole site.** SEOcrawl AI unifies your Search Console data — filter, tag, and track any section without losing the sitewide total. [Try SEOcrawl AI](/content/site-root.html).

The SEOcrawl AI dashboard unifies your Search Console data across the whole site

## FAQs

### What's the difference between a domain and URL-prefix property?

A Domain property (`example.com`) **tracks every subdomain** and both http and https in one report and is verified only by DNS.

A URL-prefix property (`https://example.com`) tracks only the exact protocol and subdomain you enter, and can be verified several ways: HTML file, HTML tag, Analytics, Tag Manager, or DNS. **Domain gives the fuller view;** URL-prefix gives finer scope.

### Do I need DNS access to use Google Search Console?

No. DNS access is required **only for a Domain property.** If you can't edit DNS, add a URL-prefix property instead and verify it with an HTML tag, an HTML file, Google Analytics, or Google Tag Manager.

You'll get **full performance data for that exact URL version;** you just won't get the automatic all-subdomains rollup a Domain property provides.

### Why is my traffic higher in the Domain property than the URL-prefix property?

Because they measure different scopes. **A Domain property sums clicks and impressions across every subdomain** and both protocols, while a www URL-prefix counts only that one version. The Domain figure isn't inflated; **the URL-prefix figure was always partial.**

### Can I switch from a URL-prefix to a Domain property without losing data?

Adding a Domain property **doesn't delete your URL-prefix property or its history;** each keeps its own data. You can't merge past data between them, so the cleaner move is to add the Domain property now and keep both.

From that point, **the Domain property becomes your complete record** while the URL-prefix retains its historical view of that specific version.

### Is a Domain property the same as my domain name?

No. Your domain name is the address you own (`example.com`). A Domain property is **a Search Console reporting container built around that domain name** that aggregates every URL under it, across subdomains and protocols.

You enter the domain name to create the property, but the property is the data view, not the domain itself.

### Which property type should I connect to SEOcrawl AI?

**The Domain property feeds SEOcrawl the complete dataset** — every subdomain and protocol — so your dashboards and rank tracking reflect the whole site rather than one version.

A URL-prefix connection works too, but **SEOcrawl will only see that slice.** For multi-subdomain sites, connect the Domain property and use tags to rebuild section-level views.