"I need to put a Google Search Console HTML code on the pages of the company website. I can't remember the procedure and the developer at our agency can't help." That message, from a small-business owner, describes a common situation. Everyone knows the site is supposed to be "verified". Nobody remembers how it was done, or what to look at afterwards.
Google Search Console is free. It shows how Google crawls, indexes and displays your site, using Google's own measurements rather than a third-party estimate. For a company with no in-house SEO team, it is the most reliable source on organic search — and the channel Google uses to warn you about manual actions, hacked content or indexing failures.
What the tool gives you that others cannot
Third-party tools such as Semrush or Ahrefs estimate your rankings and traffic from their own crawls and click models. Search Console reports what Google recorded: the queries that produced impressions and clicks, the average position, which pages are indexed and which are not, any manual action, any security issue. Measurements, not models.
Step 1: choose the property type
Sign in to search.google.com/search-console with a Google account and add a "property". There are two kinds, and the choice decides which verification methods you can use.
| Type | What it covers | Verification available |
|---|---|---|
| Domain property | Every variant of the domain: http and https, with or without www, plus subdomains | DNS record only |
| URL-prefix property | Only URLs starting with the exact prefix entered, for example https://www.example.co.uk/ | HTML file, meta tag, Google Analytics, Google Tag Manager, DNS |
If you can reach the DNS zone at your registrar, create a domain property: it gathers every variant in one place. Otherwise create a URL-prefix property matching your canonical address exactly, in https. To Google, "http://example.co.uk" and "https://www.example.co.uk" are two different properties with two different sets of data.
Step 2: verify ownership
Verification proves you control the site. Google rechecks the token, so if it disappears during a redesign, the property is unverified and the data stops.
HTML meta tag
Google gives you a tag for the <head> of the home page:
<head>
<meta name="google-site-verification" content="your-token-here">
</head>It only needs to be on the home page. You need access to the source code, or a plugin that inserts it for you.
HTML file
You upload a file supplied by Google to the root of the site, over FTP or through your host's file manager, and it must stay reachable without authentication. Robust, but it assumes hosting access — often the missing piece.
Google Analytics or Google Tag Manager
If the Analytics snippet (gtag.js) or a Tag Manager container is already on the site, Google can use it as proof, provided you sign in with the same Google account and that account holds edit rights. Where measurement exists, this is the fastest route.
DNS record
You add a TXT record (sometimes a CNAME) to the domain's DNS zone. It is the only method accepted for a domain property. Propagation can take hours, so if verification fails at first, wait and retry before deleting anything.
Setting it up on WordPress
Most small-business sites run on WordPress. Two approaches avoid editing theme files — a theme update should never be able to break your verification.
Paste the tag into your SEO plugin
Yoast SEO has a dedicated field under Yoast SEO > Settings > Site connections. Paste the tag, save, then click Verify in Search Console. One confusion survives in older tutorials: Yoast no longer pulls Search Console data back into the WordPress dashboard. The field inserts the tag, nothing more. Rank Math, SEOPress and All in One SEO offer the same.
Site Kit by Google
Site Kit is Google's own WordPress plugin, with more than five million active installations according to the WordPress.org plugin directory. It connects the property through an authorisation flow, with no tag to copy, and shows a summary of Search Console, Analytics and PageSpeed Insights data inside the admin. For an owner-manager running the site alone, it is the least fragile option.
Step 3: submit the sitemap
Once the property is verified, open Sitemaps and submit your XML sitemap address. WordPress generates one at /wp-sitemap.xml; Yoast SEO, Rank Math and SEOPress replace it with their own, usually /sitemap_index.xml. Google's documentation sets a limit of 50 MB uncompressed or 50,000 URLs per file; beyond that, split it and reference the parts from an index.
Include only canonical, indexable URLs that return 200. A sitemap full of redirects and noindex pages makes the indexing reports much harder to read.
The reports worth your attention
Performance
Clicks, impressions, click-through rate and average position over the last three months by default, broken down by query, page, country, device and search appearance. Google states that data is generally available within two to three days, and that interface tables display a maximum of 1,000 rows. For a large catalogue, use the Search Console API, which returns rows in batches of 25,000, or an export into Looker Studio.
A practical use: filter for queries with high impressions, an average position between 5 and 15, and a weak click-through rate. Those are pages Google already shows. Reworking the title, meta description and on-page content moves them faster than anything else, which is why most content work should start here.
Page indexing
This replaced the old Coverage report. It separates indexed from non-indexed URLs, with a reason for each: "Crawled — currently not indexed", "Discovered — currently not indexed", "Soft 404", "Blocked by robots.txt", "Excluded by noindex tag", "Duplicate page", plus 404 and 5xx errors.
Not every non-indexed URL is a problem — a basket page carrying noindex is a deliberate choice. What matters is spotting the useful pages missing from the index.
URL inspection
For a single URL, this shows the indexing status, the last crawl date and the canonical URL Google selected — not always the one you declared — and lets you run a live test and request indexing. Google caps requests per day without publishing the figure, so keep them for pages you have just published or fixed.
Core Web Vitals
URLs are grouped as Good, Needs improvement or Poor, from real Chrome user measurements (the CrUX dataset). Google's documented thresholds are 2.5 s for LCP, 200 ms for INP and 0.1 for CLS. On low-traffic sites it often stays empty for lack of data, which is not a fault. When groups of URLs turn Poor, that is the starting point for a performance project.
What Google has removed
The Mobile usability report, the Mobile-Friendly Test and its API were retired on 1 December 2023. Mobile rendering is now checked with Lighthouse, in Chrome or through PageSpeed Insights. A tutorial that still tells you to open it predates that change.
Linking Search Console to Google Analytics 4
In GA4, the link is made from Admin > Product links > Search Console links. You need the Editor role on the Analytics property and verified owner status on the Search Console property. Two reports then appear: Google organic search queries, and the landing pages that received that traffic. Useful context, not a reconciliation.
What about Bing Webmaster Tools?
Bing carries far less volume than Google in most markets, but adding it costs little: Bing Webmaster Tools imports your properties straight from Search Console. Imported sites are verified automatically, up to 100 per import, and Microsoft states that traffic data appears within 48 hours.
Verification failures and their usual causes
- The tag sits in the body of the page, or on an internal page, instead of the
<head>of the home page. - A server cache or CDN is still serving the previous version. Clear the cache before retrying.
- The URL prefix does not match the real address — http instead of https, or a missing www — so the home page redirects and Google never sees the token.
- The DNS record was added to the wrong domain, or has not propagated yet.
View the page source (Ctrl+U) or query the DNS directly to see what Google sees, rather than clicking Verify repeatedly. If verification keeps failing on a site you did not build, the real problem is usually an unclear hosting or DNS setup — untangle it before any technical audit.
A routine you can actually keep
Turn on email notifications so Google can reach you. Read the Performance report once a month, comparing with the previous period rather than staring at absolute numbers. Check Page indexing after any change to the site — a redesign, a plugin swap, a new section.
One governance point. If you delegate search work, add your provider as a user on the property — not as the sole owner, and not by letting them create it on their own account. Ownership of the data should follow the domain, which means it stays with you. It becomes expensive the day the relationship ends, and is worth raising when choosing a provider.
Common questions
Is Google Search Console free?
Yes. It needs nothing more than a Google account, and there is no paid tier. The only cost is analysis time — yours or a provider's.
How long before data appears after verification?
Google states that collected data is generally available within two to three days. A new property does not backfill history from before verification, so the report builds up week by week — a good reason to verify a site early.
Where exactly does the verification tag go?
The google-site-verification meta tag belongs in the head section of the home page only. On WordPress, Yoast SEO, Rank Math and SEOPress all provide a field for it, so you can paste it without editing the theme.
Should I choose a domain property or a URL prefix?
A domain property covers every variant — http, https, www and subdomains — but can only be verified by DNS record. A URL-prefix property covers just the exact address entered, and accepts several methods. If you can edit the DNS zone, the domain property is the better default.
Has the Mobile usability report been removed?
Yes, along with the Mobile-Friendly Test and its API, on 1 December 2023. Mobile rendering is now checked with Lighthouse and PageSpeed Insights, and mobile performance appears in the Core Web Vitals report.
Why don't Search Console numbers match Google Analytics?
Because they measure different things. Search Console counts clicks in Google's results; Analytics counts sessions recorded by a script on your site. Trends should agree; exact values will not.