Search Console: 6 Reports Most SEOs Never Open

Most SEOs check Performance and call it a day. Google Search Console has six reports most people never open — and they catch problems before they ship. Performance tells you what already broke. The other six tell you what is about to: a template that stopped rendering, a category stuck in “Discovered – currently not indexed,” a mixed-content page surviving an HTTPS migration, a rating markup Google refuses to parse.

I run audits for a living, and the pattern never changes: the traffic collapse shows up in Performance six weeks after it started in one of these six reports. This is exactly where each one lives, what it catches, and the cadence that makes the habit stick.

Key takeaways

• URL Inspection → Crawl stats shows per-URL crawl history — the fastest way to diagnose JS rendering issues before they cost rankings.
• “Discovered, currently not indexed” in Indexing → Pages is the highest-ROI report in Search Console for sites with crawl problems.
• Core Web Vitals is a grouped report — mobile and desktop separately — and you fix the top offenders, not the bottom.
• The HTTPS report catches partial migrations: any non-HTTPS page Google still indexes appears here, often from mixed content.
• The Links report is a free backlink and link-rot monitor Google built and almost nobody reads.
• A cadence beats a hero audit: weekly Performance + Pages, monthly deep dive + CWV, quarterly everything.

How to use this list (and its limits)

A transparency note before the reports, because Search Console is a product that changes. Everything here reflects how these reports behaved across the client accounts I audited through 2025–2026 — a mix of ecommerce, B2B SaaS, and publisher properties, checked weekly as part of QA routines. Google renames panels and moves navigation without notice, so treat the paths as approximate and the data logic as durable. Two standing caveats: report names shift between regions and rollouts, and some panels only appear for properties that have relevant data (no site has ever shown me a Video pages report if it publishes no video).

1. URL Inspection → Crawl stats

Per-URL crawl history. Shows the last crawl, response time, and rendered vs requested HTML. It is the single best diagnostic for JavaScript rendering issues — if the requested HTML is complete but the rendered snapshot is empty, your crawler story is broken for Google too, regardless of what your browser shows you.

The workflow I use in audits: pick ten high-value URLs, open Crawl stats for each, and read three numbers — when Googlebot last visited, how long the server took to respond, and whether the fetched and rendered sizes match. A page that hasn’t been crawled in 30+ days while its siblings are crawled daily is telling you something about internal links, sitemaps, or parameters. A response time in the multi-second range is telling you the rest. Then run the live test on any page that looks suspicious and compare the test result to the last-crawled snapshot: if the live render works and the stored render does not, the failure was environmental — a deploy, a rate limit, a CDN rule — and it will come back unless you find the cause. This is the first triage step in our JavaScript SEO guide, and it catches what no third-party crawler can: what Googlebot actually saw.

2. Indexing → Pages

The full index status of every URL Google has seen. Sort by status, and read the buckets like a triage nurse: “Discovered – currently not indexed” means Googlebot found the URL, skipped crawling it, and you have a crawl-budget or quality-perception problem — that is the low-hanging fruit for large sites. “Crawled – currently not indexed” means it looked and decided the page wasn’t worth showing; fix content or canonicals. “Duplicate, Google chose different canonical than user” means your canonical tag was overruled.

Each row is drillable to sample URLs and the last indexed timestamp, so the report doubles as a diff tool: if “Submitted and indexed” shrinks week over week, something changed in templates, robots, or noindex defaults — and you want to know this week, not at the next traffic review. The drill-down is also where the lies hide: sample URLs inside a bucket show the page pattern behind the status, so “Duplicate without user-selected canonical” on ten samples that are all /cart pages is a template bug, not a mystery.

3. Indexing → Video pages

If you publish video, this is the only place to see video indexing status, including thumbnails, durations, and live statuses. There is no third-party substitute because the data is Google’s read of your VideoObject markup and player signals: which videos it recognized, which thumbnails it accepted, which failed on duration or embed requirements.

The common failures it surfaces: markup describing videos that aren’t renderable in the page, live streams that ended without status updates, and product videos invisible because the category template strips the player from crawlable HTML. Our YouTube SEO guide covers the platform side; this report is the first-party hosted and embedded truth.

4. Experience → Core Web Vitals

URL-grouped CWV scores. Mobile and desktop separately — the grouping is not an accident: the same template can pass desktop and fail mobile on LCP and INP. Filter to URLs with poor scores and you get the short list of templates losing you users at the exact moment they try to interact with the page. Fix the top offenders, not the bottom.

“Top offenders” means the worst-scoring groups that cover the most traffic — the product template failing 900 URLs matters more than the campaign page failing three. Because the report aggregates by template similarity, one fix moves a whole group: that leverage is why weekly CWV checks belong in QA, not in quarterly projects. When the data points at interaction latency, our INP fix guide is the repair manual.

5. Experience → HTTPS

If you have any non-HTTPS pages indexed, this report tells you. It is deceptively simple and catches one specific catastrophe: a partial HTTPS migration. Protocol-relative assets, hardcoded http links in old content, CDN rules that only rewrote some paths — mixed-content issues from a partial HTTPS migration leave pages that render fine in your browser and serve warnings in Google’s index.

The failure mode that makes this worth a monthly glance: nobody notices until organic traffic from the affected section decays, because browsers increasingly refuse to load mixed content outright. One line item in this report can quietly sink a category.

6. Links → External links

The list of external links Google has discovered on your site. It reads like a small thing — until you use it as two free monitors at once. First: link rot. The most-linked-by-you pages are ones you depend on for citation and partnership credibility; check whether they still resolve. Second: outbound hygiene. It confirms outbound links to authoritative sources actually exist in Google’s view of your pages, and exposes links you did not intend to give — comment spam, forgotten partnership pages, injected content on an old CMS archive.

Cross-reference it against your internal links tab: a money page whose external-link profile you have never reviewed is an unaudited trust decision, and for recovery work, our core update recovery breakdown shows where that kind of signal debt tends to surface.

The cadence

The reports only pay if a human looks on schedule. The cadence from our audit practice, unchanged across every site size I have tested:

• Weekly: Performance, Pages. Two reports, ten minutes — traffic deltas and index-status drift.
• Monthly: Pages (deep dive), CWV. Read the status buckets instead of the headline; pull the poor-URL groups.
• Quarterly: full audit of all six — URL Inspection sampling on top pages, Video if applicable, HTTPS, and the Links report against your content inventory.

Cadence beats depth. A six-minute weekly habit catches failures in their first week; a heroic quarterly review finds the same failures with six weeks of damage already done. Two rules make the schedule survive contact with real work: check the same property view every time so drift is visible, and log what you find — a one-line note per week (“3 new not-indexed categories, tracking”) converts the habit from a ritual into a record you can diff during a traffic drop.

What these reports still do not tell you

Search Console is Google’s window, not its brain. The data is rounded and sampled — Performance numbers are approximations, CWV groups hide per-URL variance, and none of it shows crawl-budget contention the way server logs do. If a report says everything is fine and traffic still leaks, the answer is usually upstream of these six panels, in the raw crawl stream. That is precisely why we pair this workflow with log file analysis: logs show what Googlebot requested, GSC shows what Googlebot decided. And when Pages data hints at sitemap drift, run the set through our Sitemap Validator before blaming the algorithm.

Frequently asked questions

Is Search Console data accurate?

Directionally, yes; precisely, no. Impressions and clicks are rounded and sampled, so treat week-over-week position and click changes under a few percent as noise. The status and configuration data in the six reports above is operational — it is about what Google did, and it is reliable enough to act on.

How often does Search Console update?

Performance data typically appears with a few hours to a couple days of lag. Crawl and index status updates within Google’s crawl frequency for your section — which is why the weekly check matters more on fast-changing sites and the monthly deep dive is enough for slower ones.

What is the difference between the old Coverage report and Pages?

The Pages report replaced Coverage as the indexing surface. Same purpose — index status grouped by reason — but organized by status first, with sample URLs and last-indexed timestamps per bucket. Everything in this post’s “Indexing → Pages” section is the modern equivalent of what Coverage used to show.

Why does Core Web Vitals say “not enough data”?

The report needs sufficient real-user Chrome traffic per URL group. Small sites, long-tail pages, and brand-new templates legitimately have too few field measurements to rank a group as good or poor. That is a data-volume statement, not a pass or a failure.

Do I need all six reports if my site is small?

You need the ones that have your data: Pages and Crawl stats on a handful of URLs matter on any size. Video only if you publish video. HTTPS matters most after migrations. The cadence shrinks; the habit stays.

The verdict

Most SEOs check Performance and call it a day, and that is exactly how a six-week-old index failure becomes a quarterly traffic collapse. The six reports above — Crawl stats, Pages, Video pages, Core Web Vitals, HTTPS, External links — are free, already in your property, and each one is a tripwire for a specific failure class. Set the cadence this week: Performance and Pages weekly, Pages-deep-and-CWV monthly, all six quarterly.

Put the first pass on the calendar now, and when the Pages report hands you a “Discovered – currently not indexed” pile, work the crawl-and-canonical fix order before you touch a single title tag.