Google Search Console: The Complete Guide for SEOs

Google Search Console is the only analytics tool where the data comes from inside the machine: Google telling you, directly, how it crawls, indexes and ranks your site — which queries you appeared for, where, and who clicked. It's free, it's first-party, and it powers half the workflows in this library; yet most owners open it twice a year to stare at a graph. This guide walks every report worth knowing and the specific job each one does, so Search Console becomes what it should be: your SEO instrument panel.

Setup, correctly, once

Verify a Domain property (DNS verification) — it aggregates every protocol and subdomain, immune to the http/https/www fragmentation that scatters data across the older URL-prefix properties. Then submit your sitemap, connect the property to your analytics tool, and add the colleagues who need access. Data accrues from verification forward (16 months of retention), so the best day to set it up remains yesterday.

The Performance report: where the strategy lives

Queries, pages, countries and devices, measured in clicks, impressions, CTR and average position. The workflows it powers:

1. The CTR mine: filter to high-impression, low-CTR pages — rankings you own whose titles are failing; rewrite and re-measure. The cheapest wins in SEO, quarterly.
2. The page-two list: queries at positions 8–15 — one refresh from page one; the audit's priority queue, pre-sorted.
3. Keyword reality-check: the queries you actually appear for versus the ones you mapped — new intent discovered (spin it into content) and mismatches exposed (page ranking for the wrong thing).
4. Cannibalization detection: one query, multiple URLs trading places — the flip-flop signature, visible nowhere else this cleanly.

Two reading rules: average position is an average across all impressions (a jump from 40 to 15 often means you started ranking for more queries, not that one improved), and clicks are the metric that pays — impressions are potential, not performance.

The index reports: the plumbing gauges

Page indexing shows every URL's status and — the valuable part — the reason for every exclusion: "Crawled — currently not indexed" (a quality conversation, per the pipeline guide), "Duplicate without user-selected canonical" (a canonical job), "Blocked by robots.txt" (intended, or the classic disaster). URL Inspection is the same machinery per-URL: how Google last saw the page, its rendered HTML, its chosen canonical, plus the request-indexing nudge — the first tool in every diagnostic ladder in this series. Sitemaps tracks discovered-vs-indexed per sitemap file — the per-section instrument the sitemap guide builds around.

The health reports

Core Web Vitals — field data by URL group, the report of record for speed work. Mobile usability — parity and tap-target failures by template. HTTPS — the migration leak-check automated. Enhancements — validity of your structured data types, where eligibility silently dies when a template change breaks the JSON-LD. Security & manual actions — the report you want permanently empty; it's where penalties announce themselves, and the reason notifications should reach a mailbox someone reads.

The Links report

Top linked pages, top linking sites, and anchor texts — Google's own (sampled) census of your backlinks plus your internal link distribution. It's the free foundation of the audit workflow: coarser than commercial indexes, but it's the only view of what Google counts — and the internal-links table doubles as a check that your architecture concentrates equity where you intend.

The habit

Monthly, thirty minutes: performance trends versus last period (clicks by page-group, the CTR and page-two mines), page-indexing deltas (new exclusions = new problems), enhancements valid, manual actions empty. That cadence catches almost everything this tool can catch while it's still cheap to fix — the same early-warning philosophy as every audit habit in this library, fed into the KPI reporting the next guide covers.

Frequently asked questions

Why don't Search Console numbers match my analytics?

Different instruments: Search Console counts search-results clicks (Google's side); analytics counts sessions (your side, minus blocked scripts, plus every other channel). Directionally they agree; reconciling them to the digit is a fool's errand. Use Search Console for search behaviour, analytics for on-site behaviour.

Is "average position" my rank?

No — it's the mean position across every impression, including the query variants and geographies where you rank poorly. A tracked keyword's rank and its GSC average will differ; both are true, measuring different slices.

Search Console shows queries my keyword tool never suggested. Why?

Because it's a census of reality rather than a database estimate — the long tail in the wild. Harvest it: those queries are demand you've already been shortlisted for; content and authority decide whether you win them (we're the authority part).