Measuring SEO: Google Search Console and key metrics
Every technique in this series so far is a hypothesis until it's actually measured. Google Search Console — free, and the only tool with a direct line into how Google itself sees a site — is where that measurement happens.
Verifying ownership
Search Console requires proving ownership of a site before showing any data for it — typically a DNS TXT record, an HTML file upload, or a meta tag in the site's <head>. This is a real, necessary security boundary: without it, anyone could view another site's private search performance data.
The Performance report: four numbers that mean different things
- Impressions — how many times a page appeared in search results, regardless of whether it was clicked. A page can rank well and have high impressions with a poor click-through rate if the title and description (part 2) don't earn the click.
- Clicks — actual visits from search. The number that matters most directly, but only in the context of impressions.
- CTR (click-through rate) — clicks divided by impressions. Low CTR with high impressions is specifically a title/description problem, not a ranking problem — the page is being shown, just not chosen.
- Average position — where a page tends to rank for a given query, averaged. Useful directionally, less precise than it looks, since it blends a page's position across many different queries with very different competitiveness.
The URL Inspection tool: the direct debugging path
URL Inspection → "URL is on Google" or "URL is not on Google"
→ View Crawled Page (see exactly what Googlebot rendered)
→ Request Indexing (for a new or recently updated page)This is the most direct way to answer "why isn't this specific page ranking" — it shows whether the page is indexed at all, when it was last crawled, and (via "View Crawled Page") the actual rendered HTML Googlebot captured, which is exactly what part 15's JavaScript-rendering discussion recommends checking directly rather than assuming.
Coverage and sitemap reports
The Coverage (or "Pages") report lists every URL Google has attempted to crawl, grouped by outcome — indexed, excluded, or an actual error — which is the fastest way to spot a robots.txt mistake (part 9's "accidentally blocked the whole site" scenario) or a widespread noindex tag applied somewhere it shouldn't be, across the entire site at once rather than one URL at a time.
Core Web Vitals: real field data, not a single lab test
Search Console's Core Web Vitals report shows real anonymized data from actual visitors (Chrome User Experience Report data), not a single Lighthouse lab run — the more reliable version of part 12's metrics, since it reflects real devices and real network conditions in aggregate, rather than one simulated run's specific throttling profile.
What actually indicates a real problem vs. normal noise
A single day's traffic dip is very often normal variance — search traffic naturally fluctuates. A sustained, multi-week decline, a sudden drop coinciding with a known algorithm update, or a specific page's impressions dropping to near-zero (suggesting a deindexing event) are the patterns actually worth investigating directly, rather than reacting to daily noise.
Checking Search Console once after making a change and concluding it either worked or failed within days. Google's own data in Search Console reports with a real lag (typically 2-3 days), and ranking changes from a genuine content or technical improvement often take weeks to fully materialize — judging a change too early is one of the most common ways to draw the wrong conclusion from real data.
Next: the mistakes and manipulative tactics that actively hurt rankings — some subtle, some the kind of thing that gets a site penalized outright.