Analytics and Tracking

Property Type

Also called Domain property, URL prefix property

The choice in Search Console between covering an entire domain and covering one exact protocol, host and path prefix.

Quick facts: Property Type

Category
Analytics and Tracking
Also called
Domain property, URL prefix property
Level
Beginner
Affects
Data completeness, reporting scope, verification method
Where to see it
Google Search Console (Add property), your DNS or registrar control panel
In this article4
  1. How property type works
  2. Why property type matters
  3. Common mistakes with property type
  4. How to act on it

How property type works

When you add a site to Search Console you are asked to choose between two kinds of property, and the choice decides what data you will ever see.

A domain property covers everything on the domain: both secure and insecure addresses, the bare domain and the www version, and every subdomain beneath it. Because that scope is so wide, it can only be verified by adding a record at your domain’s DNS, which proves you control the domain itself rather than one website sitting on it.

A URL prefix property covers exactly what you type and nothing else. The protocol, the host and any path you include all form part of the definition, so a property for the secure www version of a site does not include the insecure version, the bare domain, or a subdomain. In exchange it accepts several verification methods — an uploaded file, a tag in the page head, Google Analytics or Tag Manager — and it lets you isolate one section, such as a blog folder or a shop subdomain, as its own reporting unit.

Why property type matters

Mostly because of what a narrow property hides. Sites usually answer on several addresses, and if you have verified only one of them, everything happening on the others is invisible to you. That is why a site can appear to lose all its search data overnight after moving to secure hosting or switching between the bare and www versions: the traffic did not vanish, it moved to an address your property does not describe.

The scope also decides what your reports mean. A domain property gives you one honest total for the whole business. Prefix properties let you report a section on its own, which is genuinely useful when a blog, an online shop or a market-specific subdomain or subfolder is managed by different people.

Common mistakes with property type

The frequent one is treating a single prefix property as complete coverage and then diagnosing a problem that does not exist. Before concluding that indexing has collapsed, check that you are looking at the address the site actually serves.

The second is deleting old properties during a tidy-up. Historical data belongs to the property, so removing an old prefix property throws away the record of what happened before a migration, and there is no way to get it back.

The third is losing verification quietly. A DNS record dropped during a hosting change, or a verification tag removed with a theme, ends access without any obvious warning.

How to act on it

Verify a domain property first, so nothing on the domain is ever missing from your view, and keep prefix properties for the sections you genuinely report on separately. If your registrar makes DNS records awkward, start with a prefix property verified by tag and add the domain property later.

Leave old properties in place, record which verification method each one uses, and re-check them after any hosting or theme change. Getting this right before a move is part of ordinary technical SEO preparation.

Do and do not

Do

  • Verify a domain property so nothing is missed
  • Add prefix properties for sections reported separately
  • Re-check verification after any hosting change

Do not

  • Assume a prefix property covers the www version
  • Delete old properties holding historical data
  • Diagnose a traffic loss before checking property scope

Questions people ask about this

Which property type should I choose?

A domain property if you can add a DNS record, because it covers every address on the domain and leaves no gaps. Add URL prefix properties on top when you want a section reported separately, such as a blog folder or a shop subdomain, or when a tool you use requires that form. Most sites end up with both.

My data disappeared after moving to HTTPS. What happened?

Almost certainly nothing happened to your traffic. A URL prefix property is defined by the exact protocol and host, so a property created for the insecure address stops collecting once the site answers on the secure one. Verify the new address, or better, verify a domain property, which covers both and prevents the same surprise next time.

Can I have more than one property for the same site?

Yes, and it is common practice. A domain property gives the complete picture while prefix properties give focused views of particular sections. Keeping old properties also preserves their historical data, which is lost permanently if you delete them. There is no penalty for holding several, so tidy up your list rather than removing entries.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.