Reading your Google Search Console data

Four Google Search Console reports deserve regular attention: Performance (what actually drives clicks), Indexing (what's really indexed), Sitemaps (what Google managed to crawl), and Core Web Vitals (loading experience). Together, they give you a complete diagnosis without needing any third-party tools.

The Performance report: queries, pages, clicks, impressions

This is the most-viewed report, and often the most poorly read one. It crosses four metrics: impressions (how many times a page showed up in results), clicks, CTR (click-through rate, clicks divided by impressions), and average position.

A few useful readings:

• A page with a lot of impressions but a low CTR usually points to a weak title tag or meta description, not a content problem.
• An average position stuck around page 2 (positions 11-20) signals a page Google considers relevant enough to exist, but that's missing the signal needed to break into page 1 — often internal linking or content depth.
• The query filter lets you spot keywords you're already ranking for without realizing it, sometimes unexpectedly — a solid starting point for complementary content.

Always segment by device type (mobile vs. desktop) and by country if your audience is international: global averages often hide significant gaps.

Coverage / Indexing: what's indexed and what isn't

The "Pages" report (formerly "Coverage") lists your URLs by status: indexed, or excluded with a specific reason. The most common reasons worth watching:

• "Crawled – currently not indexed": Google visited the page but chose not to index it, usually due to low perceived value or duplicate content.
• "Discovered – currently not indexed": Google knows the URL exists but hasn't crawled it yet, generally a sign of limited crawl budget or low perceived priority.
• "Page with redirect" or "404 error": fix it or leave it as-is, depending on whether it's intentional or an oversight.
• "Duplicate, Google chose different canonical than user": Google picked a different canonical URL than the one you declared, often a sign of poorly managed duplicate content.

The goal isn't 100% of pages indexed at any cost: some pages (filters, technical pagination, internal search results) have no reason to be. The goal is for the pages that matter to be indexed, and to understand why the ones that aren't, aren't.

Sitemaps: checking everything is accounted for

In the Sitemaps report, Google shows the number of URLs discovered in the submitted sitemap. A large gap between the number of URLs in the sitemap and the number of pages actually indexed (visible in the Pages report) is a warning sign — it can point to a poorly generated sitemap, outdated URLs, or low-quality pages Google refuses to index despite their presence in the sitemap.

Core Web Vitals in Search Console

The Core Web Vitals report aggregates real user data (from the Chrome User Experience Report) and buckets your pages into three categories — good, needs improvement, poor — across three metrics: LCP (loading time of the largest visible element), INP (responsiveness to interactions), and CLS (visual stability). Unlike a one-off testing tool, this report reflects actual visitor experience, grouped by URL pattern, which helps with prioritization: it's more valuable to fix a page template used by 500 URLs than to fix one isolated page.

Secondary reports worth not ignoring

Beyond the four main reports, two others deserve a regular look even though they get checked less often:

• The Links report lists your most frequent external backlinks, your most internally linked pages, and the anchor text used. A central page on your site that gets very few internal links is a sign it risks being under-prioritized by bots, regardless of how good its content is.
• The "Security Issues" report flags any detected hacking or misleading content identified by Google. A compromised site can see its crawl frequency drop sharply, an easy thing to miss if this report never gets checked for lack of a visible alert elsewhere.

These two reports are rarely the priority on a first pass, but ignoring a security issue for several months can undo all the effort put into every other lever.

Cross-referencing the data to prioritize

The most effective method is cross-referencing reports rather than reading them in isolation:

1. Spot high-potential pages in Performance (lots of impressions, average position 8-20).
2. Check in Pages whether they're fully indexed without restriction.
3. Check in Core Web Vitals whether their template is being held back by a speed issue.
4. Prioritize fixes on the templates that affect the most high-potential pages at once.

This cross-reading is exactly the foundation of a full technical audit: the next lesson details how to audit your site with generative AI and GSC data to speed up this prioritization, before moving on to the complete technical checklist.