Skip to the content
searchboar.

Crawling and indexing

Search Console property: scope, types and verification

A Search Console property is a defined reporting and access unit for a website, part of a website or supported platform presence. Domain and URL-prefix website properties cover different sets of URLs. Property ownership in Search Console is an access concept, not legal ownership.

Also known as: Domain property · URL-prefix property

At a glance

  • A Domain property includes the domain’s subdomains and protocol variants.
  • A URL-prefix property includes only URLs beginning with the specified protocol, hostname and path.
  • Verification grants access to data; it does not grant indexing permission or improve rankings.
On this page
A wide frame contains several website sections while a smaller frame highlights one branch.
A Search Console property defines the website scope covered by access permissions and reports.

Why the selected property matters

A report’s scope is part of its meaning. One business can have a property covering its whole website and another covering only its Hungarian section. Both can be valid, but they answer different questions. Their figures may overlap, so adding their totals can double-count activity.

Before interpreting a blank report or a traffic difference, check which URLs the selected property actually includes. The Google Search Console interface cannot report a section through a property that excludes it.

Domain or URL-prefix property?

A Domain property covers the domain across subdomains and protocol variants. It requires DNS verification. A URL-prefix property covers URLs beginning with the exact prefix entered, including its protocol and hostname; several verification methods are available. Property types

PropertyTypeExample scope
example.comDomainIncludes www.example.com and blog.example.com
https://example.com/URL prefixHTTPS URLs on the hostname without www
https://example.com/hu/URL prefixOnly URLs under the Hungarian section

Search Console also supports certain platform properties. Their availability and reporting rules should be checked separately from these two website property types.

Example: the apparently invisible blog

Imagine a tool-rental company using example.com for its main website and blog.example.com for advice. The owner opens the https://example.com/ URL-prefix property and assumes the blog has no search impressions.

The immediate issue is the reporting scope. Selecting a property that includes the blog makes the appropriate data available; it does not repair an indexing problem. Whether a particular post is indexed remains a separate question for URL Inspection.

Who can access the property?

Access requires verification or permission from an existing owner. Verification does not transfer a company, domain or copyright to the verified person. Give collaborators the access appropriate to their work. Ownership verification

Avoid accidentally removing a verification file or DNS record during a website update. Google can recheck verification, so retaining access evidence matters after initial setup as well.

What adding a property does not fix

Creating a property does not change a website’s canonical URLs, HTTPS configuration or indexability. Those are properties of the actual website and its responses.

For an empty performance report, first check the selected property, dates, filters, actual search activity and processing delay. An empty report alone does not establish a technical fault. Performance reporting

Sources

  1. Google Search Console: Add a website property
  2. Google Search Console: Verify site ownership
  3. Google Search Console: Performance report