Which Google Search Console Property Should I Use?

Most website owners should start with a Domain Property when they control the domain's DNS settings. A URL-prefix Property is useful when you need narrower reporting or cannot use DNS verification. Platform Properties are for eligible creator accounts and channels—not websites.

Quick recommendation Choose a Domain Property for an entire website whenever possible. Add a URL-prefix Property when you need to isolate a specific protocol, subdomain or directory. Choose a Platform Property only for a supported social-media account or creator channel.

Choose by what you want to track

Entire website

Use a Domain Property

Best when you want one property covering the domain across protocols and subdomains.

  • Requires DNS access
  • Includes HTTP and HTTPS
  • Includes www and other subdomains
  • Provides broad website reporting
Exact site section

Use a URL-prefix Property

Best when you want to track only URLs beginning with one exact prefix.

  • Supports several verification methods
  • Can isolate a protocol
  • Can isolate a subdomain
  • Can isolate a directory
Creator account

Use a Platform Property

Best for an eligible account or channel on a supported third-party platform.

  • Not used for your website
  • Added separately for each account
  • May not be available to every user yet
  • Uses platform connection or login

Search Console property decision guide

Are you adding a website you own?

If yes, choose between a Domain Property and a URL-prefix Property.

Not adding a website? Use a Platform Property only when you are connecting an eligible creator account or channel.

Can you edit the domain's DNS records?

DNS access normally means you can verify a Domain Property.

Yes: A Domain Property is usually the strongest starting choice.
No: Use a URL-prefix Property and select an available verification method, such as an HTML file, HTML tag, Google Analytics or Google Tag Manager.

Do you want all subdomains and protocols included?

Yes: Choose a Domain Property such as example.com.
No: Choose a URL-prefix Property for the exact version or section you want to measure.

Do you need reporting for one directory?

A Domain Property cannot be limited to one path. A URL-prefix Property can include an exact directory prefix.

Example: Use https://www.example.com/blog/ to focus on the blog section.

Do you manage several versions of the same site?

You can use a Domain Property for the broad view and additional URL-prefix Properties for narrower analysis.

Recommended combination: Add example.com as the main property, then add selected prefixes when their separate reporting is useful.

Property types compared

Question Domain Property URL-prefix Property Platform Property
Tracks a website? Yes Yes No
Tracks a creator account? No No Yes
Includes all protocols? Yes No—only the entered protocol Not applicable
Includes subdomains? Yes Only the entered hostname Not applicable
Can target a directory? No Yes No
Verification DNS record Several possible methods Platform login or eligible connection
Typical recommendation Best general starting point for a website Best for narrow scope or flexible verification Best for supported creator accounts

Common examples

I own a simple website on one domain

Start with a Domain Property:

example.com

This keeps your reporting together if Google discovers www, non-www, HTTP, HTTPS or subdomain versions.

I use Netlify, Cloudflare or another host but control my DNS

Use a Domain Property. Search Console verification is performed through the DNS provider, not necessarily through the company hosting the site.

I cannot change DNS records

Use a URL-prefix Property and choose one of the verification methods available for your site.

https://www.example.com/

I want separate data for a blog or language section

Keep the Domain Property for the whole website and add a URL-prefix Property for the section.

https://www.example.com/blog/

https://www.example.com/es/

I run several subdomains

A Domain Property can include all of them:

  • www.example.com
  • shop.example.com
  • tools.example.com

Add separate URL-prefix Properties only when you need more focused reporting for an individual subdomain.

I want to track my YouTube, TikTok, Instagram or X presence

Use a Platform Property when the feature and platform connection are available to you. Add each account or channel separately.

SiteWatchlist recommendation: For most independent website owners, add a Domain Property first. It reduces the chance of accidentally monitoring only one site variation. Add URL-prefix Properties later when a specific protocol, subdomain or directory deserves its own report.
Do not add only the wrong protocol. A URL-prefix Property for http://example.com/ does not include https://example.com/. If your live site uses HTTPS, make sure the property matches it or use a Domain Property.

Frequently asked questions

Can I add both a Domain and URL-prefix Property?

Yes. The properties can coexist. Use the Domain Property for broad coverage and URL-prefix Properties for focused reporting.

Will duplicate properties hurt my rankings?

No. Search Console properties control reporting access. Adding overlapping properties does not create duplicate webpages or directly affect rankings.

Should I add www and non-www separately?

A Domain Property includes both. Separate URL-prefix Properties are optional when you need to inspect them independently.

Should I add HTTP if my site redirects to HTTPS?

A Domain Property includes both. When using only URL-prefix Properties, the HTTPS property is normally the important property for an HTTPS site, although an HTTP property can sometimes help investigate old URLs or migration issues.

Does a Domain Property include folders?

It includes URLs throughout the verified domain, but its reporting scope cannot be limited to one folder. Add a URL-prefix Property when you want a property dedicated to a directory.

Does adding Search Console make my site appear in Google?

A site can appear in Google without a Search Console account. Search Console helps you monitor discovery, crawling, indexing and performance, but adding a property does not guarantee indexing or rankings.

Property scopes and verification methods were reviewed against Google's property setup documentation and Google's ownership verification documentation. Features may change. Last reviewed: July 30, 2026.