Search Console: 7 Reports Almost Nobody Uses

Google Search Console is the only official Google tool for website owners. It is free and has no real equivalent. Yet 80% of owners only look at one or two reports — Performance and Coverage — while ignoring everything else. Those other reports contain practical analytics that most paid SEO services cannot match.

This article covers 7 Search Console reports that deliver real, actionable insights in 2026.

1. Performance — a deep dive into queries

The standard Performance report shows queries, pages, clicks, and impressions. Most people look at the top-level numbers — "here's how many clicks we got this month."

The real value is in the filters:

Filter → Query → contains — all queries containing a specific word. For example, "how to" surfaces all informational queries; "buy" surfaces all commercial ones.
Position 1–10 vs Position 11–30 — split queries by where the site currently ranks. Queries in positions 11–30 are the "growth zone" — they can be moved into the top 10 with relatively minor content improvements.
Comparison vs previous period — immediately shows where rankings dropped and where they grew.

Practical takeaway: once a week, review queries in positions 11–20 that have a high CTR. These are untapped opportunities — a few days of content work can push them into the top 10.

2. Pages with structured data — why your rich snippets are not appearing

Under the Enhancements section you will find reports for schema markup: Article, Product, FAQPage, BreadcrumbList, Video, Recipe, and others. Each report shows pages that carry that markup along with any errors.

What to look at:

Valid items — how many pages are correctly marked up
Errors — critical issues where the markup is not functional
Warnings — non-critical issues that reduce the chance of appearing in rich results

For Article specifically: errors are most often caused by a missing datePublished, author.url, or image.url. Google requires all three fields to show article cards in search results.

For Product: a missing price.priceCurrency or availability is the most common error. Without these, Google will not display the product in Shopping cards.

Practical takeaway: check Enhancements once a month, fix all Errors, and your rich snippets will start appearing in search results.

3. Page Experience — Core Web Vitals from real users

The lab metrics from PageSpeed Insights represent a "benchmark measurement" under ideal conditions. Page Experience in Search Console shows real metrics collected from actual visitors to your site.

The report divides pages into three categories — Good, Needs Improvement, and Poor — based on the 75th percentile across all visits.

What matters:

If more than 10% of pages fall into the Poor category, real users are experiencing a slow site. Google penalises this in rankings.
The Mobile vs Desktop split frequently differs — mobile performance tends to be worse.
Specific URLs in the Poor category pinpoint exactly where the problem lies.

Practical takeaway: review Page Experience every two weeks. Identify the top 5 worst-performing pages, run them through DevTools Performance, and find the specific blocking resources. More detail in the post on Core Web Vitals 2026.

4. Crawl Stats — where your crawl budget is being spent

This report is hidden under Settings → Crawl Stats. Many people do not even know it exists.

It shows:

Total crawl requests over the past 90 days
Average response time — how fast your server responds to Googlebot
Crawl requests by response code — how many 200s, 3xx, 4xx, and 5xx responses
Crawl requests by file type — HTML, CSS, JS, image
Crawl requests by purpose — Discovery (new pages) vs Refresh (known pages)

What to look for:

If 4xx > 5% — you have many broken links; Googlebot finds them and wastes crawl budget
If 5xx > 1% — your server is failing; Googlebot will reduce its crawl rate
If Average response time > 1000 ms — the server is slow and crawl budget will shrink
A poor Discovery vs Refresh ratio — Google is not finding new pages

Practical takeaway: check Crawl Stats once a month. Any anomaly is a signal to dig into server logs and understand what is happening.

5. Removals — an emergency tool

If a confidential URL is accidentally indexed — for example, an admin page or an internal document — the normal deindexing path through noindex or a 404 response can take weeks to take effect.

Removals (Indexing → Removals) provides urgent deindexation — the URL will disappear from search results within a day. The removal is temporary, lasting 6 months, and during that time you need to implement a permanent solution (404, noindex, or content deletion).

You can also cancel the request if you made a mistake.

There is also a Cached URL removal option, which clears the cached copy from search results. This is useful when you have updated sensitive information and do not want Google to display the old version.

Practical takeaway: know that this tool exists. In the event of an incident, you can hide a page in minutes — not weeks.

6. Sitemaps — more than just a list of URLs

The Sitemaps report looks simple at first glance — "here is your sitemap.xml, this many URLs are indexed." But there are important nuances.

Submitted vs Indexed — a large gap (for example, a sitemap with 5,000 URLs but only 1,500 in the index) signals content quality issues or crawl budget problems.
Last read — when Google last downloaded the sitemap. If it was a long time ago, robots.txt may be blocking it or the link may be outdated.
Errors — sitemap parsing errors (malformed URLs, wrong protocols, incorrect format)

Best practice is to maintain several separate sitemaps organised by content type:

/sitemap-products.xml — products
/sitemap-blog.xml — articles
/sitemap-categories.xml — categories
/sitemap-index.xml — index file linking to all of the above

With this structure, the Sitemaps report shows statistics for each content type individually, making it easy to see where the problem lies. This is especially important for large sites.

7. Manual Actions — manual penalties

Most site owners assume everything is fine. But if you did have a manual action from Google, you would know immediately from a sharp drop in traffic. Check Manual Actions once a month.

What can appear:

Unnatural links to your site — someone is building low-quality links pointing to your site, or you purchased such links yourself
Unnatural links from your site — your site contains paid links without rel="sponsored"
Hacked content — the site has been compromised and spam content has appeared on it
User-generated spam — spam in site comments that is not being removed
Cloaking — showing different content to search engines versus users

If a manual action exists, Search Console will state it clearly and require a Reconsideration Request after the issue is resolved. This process typically takes 2–4 weeks.

Practical takeaway: visit this section once a month and check it. If there is nothing there — great, move on.

Bonus reports

International Targeting — for multilingual sites: hreflang validation
Mobile Usability — deprecated in 2023, now part of Page Experience
Security Issues — alerts if malware or phishing has been detected on the site

Summary

Search Console is an underused tool. If you increase the frequency of your checks from "occasionally" to "once or twice a week," you will get more practical SEO analytics than any paid service can provide.

If you would like us to handle the regular monitoring and respond to these signals on your behalf — get in touch. This is part of our standard ongoing SEO retainer.