Setting up Google Search Console: properties, verification, users and first checks

What a Search Console property is

Everything in Search Console is organised by property. Google defines it this way: “A property is Search Console's term for an individual asset that you can examine or manage in Search Console.” Each property has its own reports, settings, users and verification status, and you switch between them with the property selector at the top of every page.

There are two kinds. “Website properties are websites, including all pages that share the domain or URL prefix you specify.” Platform properties are your presence on supported platforms such as Instagram, TikTok, X and YouTube, aimed at creators; Google says it is rolling them out gradually. This lesson is about website properties.

Two facts help beginners relax. First, “You can have up to 1,000 properties in your Search Console account,” so creating several properties for one site is normal. Second, “Adding a property does not affect your website or platform property on Google Search, it only enables you to track your site's performance on Google.” A property is a window onto your site, not a switch that changes rankings.

Domain property vs URL-prefix property

This is the first and most important decision in the setup. The two website property types cover very different sets of URLs.

A Domain property is entered as a bare domain such as example.com. Google describes it as “A domain-level property that Includes all subdomains (m, www, and so on) and multiple protocols (http, https, ftp).” One Domain property therefore shows http://example.com/, https://www.example.com/, https://m.example.com/ and https://shop.example.com/ together, with every path under each of them.

A URL-prefix property is entered as the start of a URL, such as https://www.example.com/. It “Includes only URLs with the specified prefix, including the protocol (http/https).” Anything with a different protocol, a different subdomain or a different starting path is outside it.

Syntax rules

• Domain property: “Do not include the protocol (http/https) or a path (/some/path/) in your property definition.” Do not type www either: “Domain properties automatically include both www and non-www prefixes”. If you enter www.example.com, Search Console creates example.com.
• Domain property for a subdomain: you can create one for shop.example.com, but “a child domain doesn't contain data about the parent domain”.
• URL-prefix property: “Specify the full URL prefix for your property, including the final / mark.” Type https://www.example.com/, not www.example.com.
• Several protocols or hosts: for URL-prefix properties, “If your site supports multiple protocols (http and https), you must add a separate property for each protocol.” The same applies to each subdomain.

When to use both

For most sites the best setup is a combination, not a choice:

1. One Domain property, example.com, as the master view of the whole site.
2. A URL-prefix property for the canonical origin, for example https://www.example.com/. Its reports show only the version you actually want in search.
3. URL-prefix properties for key sections, such as https://www.example.com/blog/ or https://www.example.com/de/, and for important subdomains such as https://shop.example.com/. This gives each team its own clean reports and lets you give access to just one section.

URL-prefix properties are also your fallback when nobody in the company can edit DNS: they accept the HTML file, HTML tag, Google Analytics and Google Tag Manager methods, while a Domain property needs DNS.

What Google officially says

How to add a property step by step

1. Open the property selector on any Search Console page and choose + Add property.
2. Choose Website property, then Domain or URL prefix.
3. Enter the property: example.com for a Domain property, or the full prefix with protocol and final slash, https://www.example.com/, for a URL-prefix property.
4. Choose a verification method. For a Domain property the DNS method is selected automatically.
5. Verify now or later. Follow the steps and click Verify, or click Verify later to save your progress, then come back, select the unverified property in the property selector and click Verify.

If someone else already owns the property and adds you as a user, you skip all of this: the property simply appears in your property selector. If you remove a property and add it again later while it still has a verified owner, Google says you should be re-verified automatically.

Every verification method

The verification page shows which methods are available and recommended for your site. Google checks them with its own crawler: “Google uses the Google Site Verifier user agent to perform site verification.” Each token (record, file or tag) is personal: it is tied to the Google Account that generated it.

DNS TXT record

This is the standard way to verify a Domain property. Google describes the domain name provider method as “More complex, but is the only way to verify a Domain property.” Search Console gives you a string; you add it as a TXT record with the host field blank or set to @, depending on your provider.

# DNS zone for example.com (illustrative value)
example.com.   3600   IN   TXT   "google-site-verification=abc123EXAMPLE"

Records are not always visible straight away: “For manually installed records, it can take up to two or three days for your provider to start serving the record.” If the first attempt fails, wait and try again. The DNS method also scales: “Verifying ownership of a root domain automatically verifies ownership of all subdomains, but verifying ownership of a subdomain does not verify ownership of a parent domain.” If you use it on a URL-prefix property, you are also verified for the matching Domain property.

DNS CNAME record

Some configurations need a CNAME record instead of TXT. Search Console then gives you two values, a name (label, host) and a destination (target), and the target includes dv.googlehosted.com. Google's help explains how to check with the Google Admin Toolbox which format to use; in the most common case no CNAME is found and you use TXT.

Domain provider in the list

If Search Console shows your provider in a list, choose it, click Start verification and log in to the provider. Verification should then happen immediately. If the provider shown is not yours, choose Any DNS provider and add the record by hand.

HTML file upload

You download a personal file and upload it, unchanged, to the root of the property, so that it opens at an address like https://www.example.com/google1234abcd.html. Check it in a private browser window: the file must not require a login. Two rules matter: “Search Console does not follow redirects when looking for this file,” and “Removing this verification file from your site will cause you to lose verification for the site.”

HTML tag

You paste a <meta> tag into the <head> of the homepage that a logged-out visitor sees.

<head>
  <title>Example homepage</title>
  <meta name="google-site-verification" content="abc123EXAMPLE" />
</head>

“Search Console will periodically check for the presence of this tag.” It must also appear early in the page: “The tag must be included less than 2MB into the file.” For tag-based methods Google looks at the page a logged-out user is redirected to from the property URL, so if https://www.example.com/ redirects to /home, the tag must be on /home.

Google Analytics tracking code

If the homepage already has your Google Analytics tag, you can verify with it, signed in with the same Google Account you use in GA. Two requirements trip people up: “You must have "edit" rights for the Google Analytics account used by that page,” and “The tracking code must be in the <head> section, not the <body> section, of your page.” Use the code exactly as Google provides it.

Google Tag Manager

The same idea with a GTM container: “You must have Publish or Admin permission for the Google Tag Manager container on the page.” Placement is strict: “The <noscript> portion of the Tag Manager code must be placed immediately after the opening <body> tag of your page.”

Google Sites and Blogger

Sites built on Google products are verified automatically when you are signed in with the account that manages them. Older blogs and classic Google Sites, or sites with a custom domain, may need the HTML tag method instead.

Hosting platforms and plugins

On WordPress, Wix, Shopify, Squarespace and similar platforms, check the platform's own documentation first: some methods are blocked, and some platforms offer a built-in setting. For WordPress, Google points to Site Kit, adding: “Note that Site Kit is the only plugin that is officially sponsored by Google”. Research any other plugin before you install it.

Keeping verification in place

Verification is not a one-off event. Search Console re-checks your token from time to time, and when it disappears your access ends after a grace period. The realistic risks are ordinary site work: a redesign that ships a new theme without the tag, a migration that does not copy the file, a move to a new DNS provider that leaves the TXT record behind. Google is clear about the DNS case: “Important: To stay verified, don't remove the DNS record from your provider, even after verification succeeds.”

Protect yourself in three ways:

• Add a second method. Google recommends it: “You might want to add more than one verification method in case one of your existing verification methods fails (for example, if you verified using a Google Analytics tracking code, and someone changes a template on your website that omits the tag).” Add it under Settings, Ownership verification. A sensible pair is DNS plus an HTML file.
• Put the tokens in the deployment checklist. List the TXT record, the verification file name and the meta tag next to robots.txt and redirects, so they are carried into every new theme, server and DNS zone.
• Keep more than one verified owner. “If all verified owners lose access to a property, all users will lose access to the Search Console property.”

Child properties make life easier: “Once you have verified a property, any child properties that you add will be auto-verified using the same verification method as the parent.” Once example.com is verified, adding https://www.example.com/blog/ needs no new token. That also means that one lost token can take several properties with it.

Owners, full users and restricted users

Each person on a property has one permission level:

• Owner. “Owners can add and remove other users, configure settings, view all data, and use all tools.” There are two kinds with the same rights: a verified owner proved ownership with their own token, and a delegated owner was made an owner by another owner without a token.
• Full user. “Has view rights to all data and can take some actions.”
• Restricted user. “Has simple view rights on most data.”
• Associate. Not a person browsing your reports but a linked account or service, such as a Google Analytics property or a Merchant Center account. Associates cannot open your Search Console data directly.

One row deserves attention: the permission table lists sitemap submission for owners and full users, while the Sitemaps report page says “You must have owner permissions on a property to submit a sitemap using the Sitemaps report.” If a full user cannot submit, ask an owner, or list the sitemap in robots.txt, which the Sitemaps page names as the alternative.

Limits: “A property can have a maximum of 100 non-owners.” Delegated owners can be added until a property reaches 500 verified plus delegated owners, and verified owners have no maximum. Every user needs a valid Google Account, and “An email group cannot be added as a user.”

Managing access safely

Access to Search Console lets people remove URLs from search, disavow links and change settings, so treat it like access to the server.

Adding people

Owners add users in Settings → Users and permissions → Add user: enter the Google Account email and choose the role. Good practice:

• Keep at least two verified owners who work for the company, on company Google Accounts rather than personal ones.
• Give agencies and freelancers full user access for hands-on work, or restricted user access for reporting. Ownership is rarely needed.
• If a person only works on one section, add them to that section's URL-prefix property instead of the whole domain.

Removing ex-staff and former agencies

1. Remove access. In Users and permissions, open the menu next to the person and choose Remove access.
2. Remove their tokens. Removing a verified owner does not delete their record, file or tag, and while it remains they can re-verify. Click Unused ownership tokens and delete each of that person's tokens: their HTML file, their meta tag, their DNS record. For Google Analytics or Tag Manager verification, remove their edit, Publish or Admin rights in GA or GTM.
3. Check Ownership history. It lists owners added and removed, verification attempts and removed tokens. If a removed owner re-verifies, all current owners are notified.

If you see an owner nobody recognises, take it seriously: “If you've found an owner that you don't recognize, you might have been hacked.” Google warns that an attacker can put a token back after you remove it, so secure the site itself, not just the user list.

Linking Search Console with GA4

Linking is done in Settings → Associations in Search Console: click Associate and follow the dialog. It lets you see Search Console data in Google Analytics. Three rules from Google:

• Who can link: “To create an association between Search Console and Google Analytics, you must be an owner of the Search Console property and have edit permission on the Google Analytics property.”
• One to one: “A Google Analytics property can be associated with only one Search Console property at a time, and vice-versa.” Choose the property that matches the site the GA4 property measures, usually the Domain property or the canonical URL-prefix property. If an association disappears, another owner removed it or replaced it with a different one.
• Who sees the data: “When you associate a Search Console property with a Google Analytics property, anybody with access to that Google Analytics property may be able to see Search Console data for that site.” Review the GA4 user list before you link.

How to read Search Console data inside GA4 is covered in the lesson “GA4 for SEO”.

First-day setup checklist

Once the property is verified, spend an hour on the checks below. They tell you whether Google can reach the site, whether anything is already wrong, and whether you will hear about problems in future.

Submit the sitemap

In the Sitemaps report, paste the sitemap URL and click Submit. “You cannot actually upload a sitemap to Google.” You only tell Google where the file is, so it must be live and reachable without a login. Small, well-linked sites may not need one at all; how to build a good sitemap is covered in the lesson “XML sitemaps”.

Check Page indexing

“Your goal is to get the canonical version of every important page indexed.” Not every URL should be indexed: duplicates, redirects and pages with noindex are excluded on purpose. On day one, check that the homepage and key pages are indexed and that the reasons for the rest make sense. Every status is explained in the lesson “Page indexing report: every status”.

Check Manual actions and Security issues

Both reports should show a green check mark. A manual action is serious: “If a site has a manual action, some or all of that site will not be shown in Google search results.” For hacked content and malware, Google says “you should rely on the Security Issues report as the source of truth to verify whether any security issues exist for your site”. If you have just bought a site, these two reports show problems you may have inherited.

Open Crawl stats

“You can reach the Crawl Stats report in Search Console by clicking (Property settings) > Crawl stats.” Note that “This report is available only for root-level properties”, so you will find it in example.com or https://www.example.com/, not in https://www.example.com/blog/. Check host status for robots.txt, DNS or server connectivity problems.

Make sure alerts reach you

Search Console emails owners and users about new issues, manual actions and new owners. Notification settings are per person, in User settings → Email preferences. Google explains the master switch: “If unchecked, no emails will be sent to you for any of your properties, though they will be available in the message panel in Search Console.” Make sure at least one person who reads email daily has it switched on.

When data appears

Google gives two timeframes, and both are short and vague on purpose:

• “Data should begin to appear in your property in a few days. Data collection for a property starts as soon anyone adds the property to their Search Console account, even before verification.”
• “If your property has no data several days after verification, it is possibly because the site hasn't been seen in Google Search, or that you have specified the wrong URL (for example, you specified http instead of https for your URL-prefix property).”

So an empty property after a few days usually means one of two things: the site is not in Google yet, or you created the wrong property. Compare the property URL with the address in your browser bar character by character: protocol, www, final slash.

Common mistakes

• ✕Only a URL-prefix property for the wrong versionhttp://example.com/ while the site lives on https://www.example.com/. The reports stay empty or show only redirects. Add a Domain property.
• ✕Only a Domain propertyFine as a master view, but sections, subdomains and the canonical origin are easier to analyse in their own URL-prefix properties.
• ✕Verification removed in a redesignA new theme drops the meta tag, a migration skips the HTML file, a DNS move loses the TXT record. Access ends after the grace period.
• ✕A single verification method and a single ownerOne lost token or one departed employee and nobody can get in.
• ✕Verification file behind a redirect or loginSearch Console does not follow redirects for the file, and it must open for logged-out visitors.
• ✕Ex-staff removed but tokens leftTheir file, tag or DNS record still lets them re-verify.
• ✕Agencies made owners by defaultFull or restricted user access is enough for most work.
• ✕Ownership on a personal Gmail accountWhen the person leaves, so does access. Use company accounts.
• ✕GA4 linked to the wrong propertyThe link is one to one; link the property that matches the site GA4 measures.
• ✕Email notifications switched offManual actions and security issues still appear in the message panel, but nobody notices.

FAQ

Sources

• Search Console Help — Add a website or platform property to Search Console
• Search Console Help — Verify your site ownership
• Search Console Help — Managing owners, users, and permissions
• Search Console Help — Associations
• Search Console Help — Sitemaps report
• Search Console Help — Page indexing report
• Search Console Help — Manual actions report
• Search Console Help — Security issues report
• Search Console Help — Crawl Stats report
• Search Console Help — Email Preferences page

Quotes checked against the official pages on 30 October 2026.