Domain Property vs URL Prefix in Search Console: Which to Choose

When you add a site to Google Search Console, the first decision is the property type, and it quietly shapes every report you read afterward. The domain property vs url prefix choice decides which URLs are counted. Pick a URL-prefix property for http://example.com/ and you will see nothing about https://example.com/ or https://www.example.com/, even though most visitors use those. Pick a domain property and you see all of them together.

This guide is for site owners, marketers and developers who are adding a site, or who inherited a property and want to know what it covers. You will learn exactly what each type includes, how each is verified, when to use both, and how to avoid reading the wrong property. By the end you should have a clear property plan for your site in a single list.

Neither type changes how your site appears in search. Google notes that adding a property does not affect your website on Google Search; it only lets you view and manage data.

Before you begin

You need a Google account. To verify a domain property you also need access to your domain's DNS settings, through your registrar or DNS host. If someone else controls DNS, ask them to add one record for you or use a URL-prefix property, which has more verification options.

Allow about 20 minutes, plus waiting time for DNS. Adding a property is safe: if you do not finish in one sitting, nothing on your website is affected. When you edit DNS, copy the existing records first so you can restore them. Add only the verification record, and do not change other records. For the rest of setup, see Set Up Google Search Console.

Domain property vs URL prefix: the two types side by side

	Domain property	URL-prefix property
Example	`example.com`	`https://example.com/`
Includes	All subdomains and multiple protocols (http, https, ftp)	Only URLs that begin with the exact prefix, including the protocol
Subpaths	Yes, every path on every covered host	Only paths under the prefix
Verification	DNS record only	Several methods
Best for	A complete view of one registered domain	A subfolder, one subdomain, or one protocol

What a domain property covers

If you create a domain property for example.com, its data includes http://example.com, https://example.com, https://www.example.com, http://m.example.com, https://m.example.com/any/path/here and any deeper subdomain such as http://a.b.c.example.com. It does not include example.org or example.co.uk, because the public suffix is part of the property name. A property for fish.example.com covers fish.example.com and its children, but not the parent example.com.

Two syntax rules matter. Enter just the domain, without http://, https:// or a path. And do not add a www prefix: if you enter www.example.com, Search Console creates the property as example.com, which covers both the www and non-www hosts. Public suffixes themselves cannot be verified as domain properties.

What a URL-prefix property covers

A URL-prefix property is the beginning of a URL. If it is https://example.com/pets/, then https://example.com/pets/puppies and https://example.com/pets/cats?a=siamese&b=in-stock are in, but http://example.com/pets/ (different protocol) and https://m.example.com/pets/ (different subdomain) are out. Include the protocol and the final slash. If your site answers on several protocols or hosts, you need a separate property for each.

Step-by-step instructions

Step 1: List the hosts and protocols your site really uses

Write down every hostname that serves your content: the apex (example.com), www, any m. or app subdomains, and a blog or shop on its own subdomain. Note whether http:// still answers. This list tells you what a single property must cover. If your site uses both www and non-www, or you have subdomains, a domain property is the simplest way to see them all. If the two hosts both answer without a redirect, fix that first; see www vs non-www.

What success looks like: You have a list of hosts, protocols and sections.

Step 2: Decide what you need to see

Choose by purpose:

One complete picture of the whole domain: a domain property.
Only a subfolder, such as /blog/ or a country folder: a URL-prefix property for that path.
One subdomain on its own: a URL-prefix property for it, or a domain property for the subdomain.
No access to DNS: a URL-prefix property, because you can verify it with a file, a tag or another method.

For most sites with DNS access, the best answer is both: a domain property for the full view and a few URL-prefix properties for sections you report on separately.

What success looks like: You can say which property answers which question.

Step 3: Create the domain property

In Search Console, open the property selector, choose Add property, then Domain, and enter the root domain. Search Console shows a TXT record to add. A typical record looks like this:

Type:  TXT
Host:  @   (or leave blank, depending on your DNS provider)
Value: google-site-verification=<the string shown in Search Console>

Copy the value exactly from Search Console. For the host field, Google says to leave it blank or use @, as your DNS provider's documentation describes. Some providers offer a one-click flow where you sign in and verification happens immediately. A CNAME record is the alternative when a TXT record does not suit your setup.

What success looks like: Search Console shows the DNS record to publish.

Step 4: Verify, and wait if needed

Click Verify after you publish the record. When you add the record manually, Google says it can take up to two or three days for your provider to start serving it. If verification fails, wait a day or two and try again. Google's Admin Toolbox can show which TXT or CNAME records your provider is serving. Leave the record in place after success; if you remove it, you lose verification.

If verification keeps failing, use Search Console Verification Failed.

What success looks like: The property is marked verified and stays that way.

Step 5: Add URL-prefix properties for the sections you track

Add a URL-prefix property such as https://example.com/blog/ or https://shop.example.com/. Once you have verified the parent, child properties are auto-verified using the same method. For example, Google says that verifying example.com by file upload means a child such as https://example.com/some/path is auto-verified too.

Do this only for sections you actually report on. Google's own example is a travel site with separate properties for /france/, /ireland/ and /spain/, alongside one for the whole site.

What success looks like: Each reporting section has a property whose scope you can state in one sentence.

Step 6: Label and use the right property

Search Console lists every property in the selector, and the names look similar. Before you copy a number into a report, confirm which property you are in. A domain property will show larger totals than a URL-prefix property for the same site because it includes more URLs. Do not compare them as if they were the same measure. If you want to split a domain property by host or protocol, you can add a page filter in the Performance report. See Read the Search Console Performance Report.

You can have up to 1,000 properties in one account, so there is no need to be stingy, but keep the list tidy.

What success looks like: Every report you share names its property.

Step 7: Plan who owns the verification

Verification lasts while Search Console can still find your token, and it checks periodically. If it can no longer confirm it, you are notified, and permissions can expire after a grace period. If all verified owners lose access, all users lose access to the property. Record where the DNS record lives, who can edit it, and add at least two owners.

What success looks like: More than one trusted person can keep the property verified.

Final verification checklist

Your host and protocol list is written down.
A domain property exists for the root domain, verified through DNS.
URL-prefix properties exist only for sections you track.
The TXT or CNAME record is still in DNS.
You can state the scope of each property in one sentence.
Reports and exports name their property.
At least two owners exist.

Common mistakes to avoid

Verifying only http://example.com/. A URL-prefix property for the wrong protocol shows little or no data. Use a domain property or add the HTTPS version.
Entering www.example.com for a domain property. Search Console strips it to example.com, which is fine, but do not expect it to show only www.
Adding https:// to a domain property. Domain properties take the domain alone.
Deleting the DNS record after verifying. You can lose verification. Keep it.
Comparing totals across property types. They cover different URLs.
Expecting a parent to be covered by a child. fish.example.com does not include example.com.
Relying on a single owner. Add a second one.

Frequently asked questions

Do I need both types?

Not required. A domain property alone gives the full picture. Add URL-prefix properties when you want sections separated or when DNS verification is not possible.

Can I verify a domain property without DNS?

No. Google says a domain property requires DNS record verification, except for properties on Google products such as Blogger or Google Sites.

Does a domain property include subdomains?

Yes, it includes all subdomains and multiple protocols.

Which one is better for a site with a subfolder per country?

A domain property for the whole site plus a URL-prefix property for each country folder is a common pattern, matching Google's own example.

Does the property type affect rankings?

No. It changes which data you see and manage, not how Google treats your site.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.