Google Search Console Setup: Property, Verification, Users

Setting up Google Search Console takes four steps: add a property (a Domain property if you can edit DNS, a URL-prefix property if you can't), verify that you own the site, give the right people access, then submit your sitemap and link Google Analytics. It's free, and "Google Webmaster Console" is simply the old name people still search for. This guide covers each step, every verification method, and the choices that decide whether your setup still works a year from now.

Sev LeoLinkedInTwitter

Sev Leo is an SEO expert and IT graduate from Lapland University, specializing in technical SEO, search systems, and performance-driven web architecture.

Google Webmaster Console is now Google Search Console

Google renamed Google Webmaster Tools to Google Search Console on May 20, 2015. It’s the same product: “Google Webmaster Console”, “webmaster tools” and “GSC” all point to search.google.com/search-console.

Three facts worth knowing before you start, all from Google’s Search Console overview and property help:

• It’s free. All you need is a Google account. There is no separate “webmaster account” to create.
• It’s optional for indexing. Google says you don’t have to sign up for Search Console to be included in Google Search. You set it up to see your data and get alerts, not to get indexed.
• Data starts collecting as soon as anyone adds the property, even before it’s verified. Expect a few days before the reports fill in. One account can hold up to 1,000 properties.

Step 1: Choose a Domain or URL-prefix property

A property is what Search Console reports on. For a website there are two types, and the difference is scope (Google’s property help):

When Google launched Domain properties in 2019, it said: “We recommend using domain properties where possible going forward” (Search Central blog). The only real reason not to is that you can’t get a DNS record added.

When a URL-prefix property is still the right call

URL-prefix properties are not legacy. They make sense when:

• Nobody can touch DNS. Common on client sites where the registrar login belongs to someone unreachable. Start with URL-prefix and add the Domain property later.
• You want a section on its own. Google suggests creating a property for each subsection you track separately, plus one that covers everything, such as a Domain property. A https://example.com/blog/ property gives the blog its own reports and its own users.
• Different people own different parts. A URL-prefix property for https://shop.example.com/ lets you give a team access to the shop without exposing the rest of the domain.

You can have both types for the same site, and you don’t lose anything by doing so. If you only need to split data occasionally, a page filter in the Performance report does the job inside a Domain property. If your site really does serve several protocol or host variants, also tell Google which version is canonical.

How to add the property

1. Open Search Console and sign in with the Google account that should own the property.
2. Open the property selector and click + Add property (or use the link on the welcome page).
3. Choose Domain and enter the domain without the protocol or www, such as example.com (a subdomain such as shop.example.com also works), or choose URL prefix and paste the exact address including https:// and the final slash.
4. Pick a verification method (next step). You can also click Verify later and finish another time; data still starts collecting.
5. If the reports are still empty a few days after verification, Google gives two likely reasons: the site hasn’t been seen in Google Search yet, or the URL was entered wrong, typically http for an https site.

If someone already gave you access, the property is in your selector and you can skip this step entirely.

Website properties vs platform properties

If your property menu shows Instagram, TikTok, X or YouTube, that’s a newer platform property type. It shows how people find your posts or videos through Google Search (plus Discover and News, if they appear there). It doesn’t show views on the platform itself. Google says it’s rolling out gradually, so not every account has it. Platform properties are verified by signing in to the platform or connected through an existing website property, and each account or channel is a separate property, not part of your website property. The rest of this guide is about website properties.

Step 2: Verify ownership with the right method

Verification proves you control the site, and it’s what gives you owner rights. Google checks periodically that your token is still there. If it disappears, you get a notice, and if it isn’t fixed your permissions expire after a grace period. Google doesn’t publish how long that is. So the question isn’t which method is quickest today. It’s which token will survive the next redesign.

DNS is the most durable choice because it lives outside the website. Redesigns, CMS migrations and tag cleanups never touch it. It’s also the only method for a Domain property, and using it on a URL-prefix property auto-verifies the matching Domain property too.

DNS verification, step by step

1. In the verification dialog, pick your DNS provider if it’s listed and click Start verification. For some providers Google can add the record for you.
2. Otherwise choose TXT (most sites) and copy the record. In your provider’s DNS settings, add a TXT record with the host left blank or set to @, and paste the value exactly.
3. Use CNAME only when Google Admin Toolbox finds an existing CNAME record for your domain whose target is a parent domain of it. Search Console then gives you a name/value pair, and the value includes dv.googlehosted.com.
4. Click Verify. Google notes that manually added records can take up to two or three days to be served. If it fails, wait a day or two and retry.
5. Leave the record in place. Google is explicit: don’t remove it, even after verification succeeds.

Verifying the root domain also verifies every subdomain. Verifying a subdomain like m.example.com does not verify example.com.

Google Search Central has a short walkthrough of this method:

HTML file, HTML tag, Analytics and Tag Manager

• HTML file: download the file Search Console gives you and upload it unmodified to the root, so it loads at the site root (for example https://example.com/google1234abcd.html). Open it in an incognito window before clicking Verify. Same-domain and http-to-https redirects are fine; a redirect to another domain fails.
• HTML tag: the “verification code” is a <meta name="google-site-verification"> tag. Paste it into the <head> of the homepage that a logged-out visitor sees, within the first 2 MB of the page. Check the rendered source, not your local copy.
• Google Analytics: works if the homepage already has gtag.js or analytics.js in the <head> and you use the same Google account in both tools with edit rights in Analytics.
• Google Tag Manager: works if the container’s <noscript> snippet sits immediately after the opening <body> tag and you have Publish or Admin permission on the container.

The tag-based methods (meta tag, Analytics, Tag Manager) all depend on your templates. That’s why Google suggests adding a second method under Settings > Ownership verification, so that a template change that drops one tag doesn’t cost you access.

WordPress, Shopify, Wix and other hosted platforms

On a hosted platform you may not be able to upload files or edit the <head>. Google’s advice is to search your host’s documentation first (“Shopify Search Console”, “Wix Search Console verification”), because many platforms have a setting or plugin that handles verification. For WordPress, Google points to Site Kit, which it notes is “the only plugin that is officially sponsored by Google.”

These shortcuts usually set an HTML tag for you, so they last only as long as the setting or plugin stays enabled. If you can reach the domain’s DNS, add a DNS record as well. It’s the method that survives a platform change.

When verification fails

Google lists the failure reasons for each method. The common ones:

Google runs these checks with the Google Site Verifier user agent. If the file or page loads for you but verification still fails, make sure a firewall, bot protection or login wall isn’t blocking that agent.

Step 3: Make verification survive redesigns and handoffs

A green checkmark today doesn’t mean access next year. A few habits keep a property from going dark:

1. Have at least two verified owners, and if one of them is an agency, make the other someone at the company. Google warns that if all verified owners lose access, every user loses access too. Data keeps collecting, but nobody can see it until someone verifies again.
2. Add a second verification method under Settings > Ownership verification. A DNS record plus an HTML tag means one change can’t lock you out.
3. Add sections as child properties after the parent is verified. Once example.com is verified, child properties like m.example.com or https://example.com/some/path are auto-verified with the same method.
4. Put the token on your launch checklist. Before any migration, theme swap, DNS move or tag-manager cleanup, confirm the record, file or tag carries over.
5. Use real accounts. Each user must be a valid Google account, and Google says an email group can’t be added as a user. Ownership tied to a shared inbox nobody watches is the same as no owner.

Step 4: Add users and set the right permissions

Search Console has three permission levels (owner, full user and restricted user), and owners come in two types (Google’s permissions help):

Google also has an associate type: an account linked to the site, such as a Chrome Web Store account, that can act on the site’s behalf but can’t open the Search Console data directly.

To add someone, go to Settings > Users and permissions (only owners see it), click Add user, enter their Google account email, choose the permission level and save. A property can have up to 100 non-owner users, and delegated owners can be added until there are 500 owners in total.

Agency and client access that survives a handoff

The setup that holds up best:

• The client verifies the Domain property with DNS on their own Google account, so ownership stays with the business.
• The agency gets delegated owner if it needs to manage users, or full user if it only does the SEO work. No agency token on the site means nothing to clean up later.
• Reporting-only people get restricted. Executives, writers and freelancers rarely need more.

Offboarding is where most setups leak. Removing a person from Users and permissions isn’t enough if they verified with their own token: Google says to remove them as a delegated owner first, then delete all of their verification tokens, or they can re-verify. You also can’t downgrade a verified owner. You can only remove them.

Third-party tools connect through the Search Console API, using the Google account you authorize, and they see what that account’s permission level allows. The API reports it as siteOwner, siteFullUser, siteRestrictedUser or siteUnverifiedUser, and lists a Domain property as sc-domain:example.com. If a tool can’t find your property, check which account you connected and whether it was added to the Domain or the URL-prefix property.

Step 5: Submit your sitemap

With the property verified, tell Google where your XML sitemap lives (Sitemaps report help):

1. Find your sitemap URL. Most CMSs generate one automatically, often at /sitemap.xml or /sitemap_index.xml. Run it through a sitemap validator if you’re not sure it’s clean.
2. Inspect the sitemap URL with a live test in URL Inspection and confirm Page fetch is successful.
3. Open Sitemaps, paste the URL into Add a new sitemap and click Submit.
4. Check the status: Success means every URL was queued for crawling, Has errors means it was read with problems, and Couldn’t fetch means Google couldn’t retrieve the file.

Two setup details matter here. Restricted users can’t submit sitemaps (Google’s permissions table allows owners and full users; the Sitemaps help page says owner), so if the button isn’t available to you, list the sitemap in your robots.txt instead. And the report only shows sitemaps for the current property, so a sitemap submitted under http://example.com won’t appear under https://example.com. A Domain property avoids that split.

A single sitemap can hold up to 50,000 URLs or 50 MB uncompressed. For when to use a sitemap versus a one-off indexing request, see request indexing vs XML sitemaps. For the bigger picture on sitemaps and site structure, the SEO guide covers the fundamentals.

Step 6: Link Search Console to GA4

Linking puts Search Console’s query and landing-page data inside Google Analytics, next to engagement and conversions (Analytics help).

Before you start: you need the Editor role on the GA4 property and must be a verified owner of the Search Console property (you can verify during linking). Both should cover the same pages, so link the property that matches your GA4 web data stream.

1. In GA4, open Admin and, under Product links, click Search Console links.
2. Click Link, then Choose accounts and pick the Search Console property you own. Click Confirm, then Next.
3. Select the web data stream for the site, click Next, review and submit.
4. In GA4’s Library, publish the Search Console collection. It’s unpublished by default, which is why many people link successfully and then can’t find the reports.

Three limits trip people up:

• It’s one-to-one. A web data stream links to one Search Console property, and a Search Console property links to one web data stream. If you have both a Domain and a URL-prefix property, pick the one you’ll keep using, usually the Domain property.
• History depends on order. If the stream existed before you verified the site, data starts from the verification date. If you verified first, it starts from the stream’s creation date. Data appears 48 hours after Search Console collects it, and covers at most 16 months.
• Links can’t be edited. To switch properties, delete the link and create a new one.

For the tracking setup around it (tags, consent, key events and the organic reports to read), see how to track SEO traffic in GA4.

Your Search Console setup checklist

Run through this once per site, and again after any migration or agency change:

• Domain property added (example.com), plus URL-prefix properties only for sections you want to see separately
• Verified by DNS record, with a second method added under Ownership verification
• At least two verified owners, one of them inside the business
• Agency and team members added as delegated owners, full users or restricted users, not with their own tokens
• Sitemap submitted and showing Success
• GA4 linked to the right property and the Search Console collection published

Once that’s in place, data takes a few days to arrive. When it does, the report-by-report guide linked at the top of this page explains what each one shows. If something looks empty, these seven mistakes that hide Search Console data cover the usual causes, starting with the wrong property.