Google Search Console Essentials

Verifying your property

Before Search Console will show you anything, you need to prove you own the site. Google offers several verification methods: adding a small HTML file to your site's root, adding a meta tag to your homepage, verifying through your domain registrar's DNS records, or — the fastest option if you already have GA4 or Google Tag Manager installed — verifying automatically through one of those existing connections.

There are two property types: a Domain property, which covers every subdomain and protocol (http, https, www, non-www) under one roof and requires DNS verification, and a URL-prefix property, which covers only the exact URL pattern you verify (for example, only https://www.example.com) and supports the simpler verification methods. For most small businesses running a single site on a single domain, either works — the domain property is slightly more convenient long-term because it does not need re-verifying if you change protocols or add a subdomain later, and it automatically consolidates data that would otherwise be split across www and non-www versions of the same site.

It is worth verifying both the domain property and, if you already have one set up, keeping any existing URL-prefix property rather than deleting it — historical data tied to an old property is not automatically transferred to a new one, so removing a working property purely to "tidy up" can mean losing access to past performance history for no real benefit.

The Performance report — clicks, impressions, CTR, position

The Performance report is the core of Search Console, and it is the only place that shows you data from actual Google search results — GA4 cannot see this, because it only measures what happens after someone lands on your site. Four metrics drive it:

• Impressions — how many times a page from your site appeared in search results, whether or not anyone clicked it. A page can have high impressions and still be effectively invisible if it never earns clicks.
• Clicks — how many of those impressions turned into an actual visit. This is the number most directly tied to real traffic.
• CTR (click-through rate) — clicks divided by impressions. A page ranking well but with a weak CTR often has a title or description that is not compelling enough to earn the click, even at a decent position — this is one of the few places where a small copy change (rewriting a title tag or meta description) can have a measurable, checkable effect on traffic without needing to change the page's ranking at all.
• Average position — roughly where your page tends to appear in results for a given query. Treat this as directional rather than exact; it is an average across many searches, devices, and personalisation factors, and it will fluctuate even when nothing on your site has changed.

You can filter and segment this report by query (what people searched), page (which URL appeared), country, device, and date — which makes it possible to answer specific questions like "which search terms bring people to our pricing page" or "are we losing mobile visibility." Filtering by query is particularly useful for finding terms where a page already ranks reasonably well but has a low CTR — often the easiest wins to act on, since the page is already visible and only the presentation needs improving.

Coverage / Indexing report

The Coverage report (sometimes labelled "Pages" or "Indexing" depending on the current interface) shows which of your pages Google has successfully indexed, and — more importantly — which ones it tried to index and could not, along with the reason. Common issues it flags: pages blocked by robots.txt, pages with a noindex tag that may have been added unintentionally, server errors encountered during a crawl attempt, and duplicate pages where Google chose a different URL as canonical than the one you expected.

This report is worth checking whenever you publish something new, and on a periodic basis regardless — new indexing errors often appear after a site update, a plugin change, or a migration, and can sit unnoticed for months if nobody is watching this report. A page that used to be indexed and suddenly is not is a stronger warning sign than a brand-new page simply not being indexed yet — the former usually points to something that broke, while the latter is often just a matter of waiting for Google to crawl it.

Not every item flagged in this report needs urgent action. Some "excluded" pages are excluded on purpose — a thank-you page, an internal search results page, a staging duplicate — and seeing them listed is expected, not a problem to fix. The report is most useful for catching the pages you actually wanted indexed that are not, rather than treating every excluded URL as an error to chase down.

Submitting a sitemap

A sitemap is an XML file listing the pages on your site you want search engines to know about. Submitting one under Search Console's Sitemaps section does not guarantee indexing, but it gives Google a direct, reliable list to work from rather than relying purely on discovering pages through links — which is especially useful for new pages, or for sites where some pages are not well linked internally. Most modern website platforms and CMSs generate a sitemap automatically at a predictable URL (commonly /sitemap.xml); submitting it is usually a one-time, thirty-second task, though it is worth re-checking after a major site restructure to confirm the sitemap itself was updated correctly and did not silently break.

Why Search Console shows different numbers than GA4

It is normal — expected, even — for Search Console and GA4 to disagree on traffic numbers for the same period, and this confuses people new to both tools. The reason is that they measure fundamentally different things from different data sources:

• Search Console counts clicks from Google Search results specifically — not traffic from any other search engine, not direct visits, not social or referral traffic.
• GA4 counts all sessions from all sources that successfully loaded a page with the tracking tag firing — including visits that Search Console never sees, and excluding visits where the tag failed to fire, an ad blocker interfered, or the click never resulted in a full page load.
• They also use different definitions of a "visit" entirely — a Search Console click and a GA4 session are not the same unit of measurement, even before you account for tracking gaps, and a single click counted by Search Console can sometimes correspond to zero recorded GA4 sessions if the visitor left before the tag fired.

Do not try to reconcile the two numbers to match exactly — that is not the goal, and chasing an exact match is a waste of time that will not succeed regardless of how carefully the setup is checked. Use Search Console to understand your visibility and click behaviour within Google search, and use GA4 to understand what happens after someone arrives, from any source. Linking the two together inside GA4's admin settings lets you view some Search Console data alongside GA4 reports, which is convenient, but the underlying numbers will still never match perfectly.