Search Console is free, it's the only first-party data Google gives you about your own search performance, and most people open it, look at the big graph, feel vaguely reassured or vaguely worried, and close it again.
The big graph is the least useful thing in there.
Five reports do the actual work. Here's what each one tells you, the thresholds that mean something, and what to do when a number goes wrong.
The short version
- Performance → Pages — which pages are winning, slipping, or badly pitched
- Performance → Queries — what people actually search to find you
- Pages (Indexing) — what's indexed and what isn't, with reasons
- URL Inspection — the single-page diagnostic
- Core Web Vitals — performance grouped by URL pattern
Everything else is either niche or informational.
1 — Performance → Pages
The most useful report in the tool, and it becomes far more useful once you start comparing date ranges.
Set the comparison to last 6 months versus previous 6 months. Now you're looking at change rather than a snapshot, and change is where the actionable information lives.
Three lists to pull:
Pages that lost clicks. These had something and lost it — which means the fundamentals worked once. Cheapest possible wins.
Pages at average position 11–20. Page two, which is invisible. These are already deemed relevant by Google and often need one decent update to break through. Usually the highest-return list.
Pages with high impressions and low CTR. Google is showing these to plenty of people who then click someone else. That's a title and description problem, not a content problem — a much cheaper fix. The formulas.
On average position: treat it as directional, not precise. It's averaged across every query, device, and country where you appeared, so a single number blends a first-place ranking for one query with a fortieth-place ranking for another. Chasing it as a headline metric leads you astray. Filter by individual query before drawing conclusions.
2 — Performance → Queries
What people actually type to find you — which is frequently not what you thought you were targeting.
Two things to look for:
Queries you rank for but didn't write for. If a page is picking up impressions for a question it only glances at, that's a validated content opportunity. Real search demand, confirmed relevance, and no keyword tool required. Either expand the existing page or write a dedicated one.
Queries with high impressions and no clicks. You're appearing and being ignored. Sometimes that's a title problem. Increasingly it's an AI Overview answering the question above you.
The limitation worth knowing: Search Console suppresses low-volume queries for privacy, so you're seeing a filtered view. The long tail is bigger than what's shown, and comparing "total clicks" against your per-query totals will never reconcile. That's expected.
The AI Mode filter, added in June 2025, is your only first-party window into Google's AI surfaces — worth checking, since GA4 folds that traffic into Organic Search. Tracking AI traffic properly.
3 — Pages (Indexing)
Formerly called Coverage. It splits your URLs into indexed and not indexed, with reasons for each.
The reasons that matter:
"Crawled – currently not indexed" — Google read the page and chose not to store it. Usually thin, duplicative, or purposeless content. A content problem, not a technical one.
"Discovered – currently not indexed" — Google knows the URL exists but hasn't prioritised crawling it. Usually a crawl-priority or internal-linking issue.
"Excluded by 'noindex' tag" — fine if deliberate. Check that it is.
"Alternate page with proper canonical tag" — normal and expected for duplicates.
"Page with redirect" — normal.
What to actually watch: the ratio and the trend. A site where 60% of URLs sit in "crawled – currently not indexed" has a quality problem, not a technical one. And a sudden jump in any not-indexed category means something changed — check what shipped that week.
4 — URL Inspection
The single-page diagnostic, and the fastest answer to "what's wrong with this page."
Paste a URL and it tells you whether the page is indexed, when it was last crawled, which canonical Google chose versus which you declared, whether it's mobile-usable, and what structured data was detected.
The most valuable feature is buried: Test Live URL → View Crawled Page. That shows you the rendered HTML Googlebot actually sees.
If your main content isn't in there, you have a JavaScript rendering problem — and no amount of content work fixes it. This is the check that saves people weeks.
Also watch the canonical comparison. When Google's chosen canonical differs from your declared one, your signals contradict each other — usually your internal links or sitemap point somewhere your canonical doesn't.
Request Indexing is worth doing once after a meaningful update. Doing it repeatedly on the same URL achieves nothing.
5 — Core Web Vitals
Groups your URLs into Good, Needs Improvement, and Poor, by URL pattern rather than individually.
That grouping is the useful part. It tells you whether you have a template problem or a page problem. If every blog post fails, your post template is the issue and one fix solves everything. If one page fails, that page has an oversized image.
Two caveats:
It uses field data from real Chrome users, so it needs traffic to populate. Low-traffic pages show nothing.
It lags. The data covers a 28-day rolling window, so a fix takes weeks to show. Don't panic when nothing moves in three days — use PageSpeed Insights' lab data for immediate feedback instead. Reading that report.
What to ignore
To save you time: Links is interesting but not actionable — third-party tools give you better link data. Enhancements varies by what's on your site and is largely informational; note that the FAQ report was withdrawn in June 2026 after Google retired FAQ rich results. Removals is for genuine emergencies only, and it's temporary rather than a substitute for noindex.
A monthly routine
Fifteen minutes, once a month, catches almost everything.
Performance → Pages, 6-month comparison. Pull the three lists. Note anything that dropped materially.
Pages (Indexing). Has the not-indexed count jumped? If so, what shipped?
Core Web Vitals. Any URL group moved into Poor?
One spot-check with URL Inspection on your most important page.
Then act on one thing. A single page refreshed properly beats a spreadsheet of observations nobody actions.
Frequently asked questions
What is a good average position?
Less meaningful than it looks, because it averages across every query, device, and country where you appeared — blending a first-place ranking for one term with a fortieth-place ranking for another. Use it directionally, and filter by individual query before drawing conclusions. The more actionable view is pages sitting at average position 11–20, which are ranking but invisible on page two.
Why do impressions rise but clicks fall?
Usually an AI Overview appearing above your result and answering the question, which is the characteristic pattern — Ahrefs measured roughly 58% lower click-through for top-ranking pages when an AI Overview is present. Other explanations include ranking for broader queries where you're less relevant, or losing a featured snippet. Check whether the affected queries trigger AI Overviews before assuming your titles are the problem.
How often should I check Search Console?
Monthly is enough for most sites, with a fifteen-minute routine covering the Pages report, indexing counts, and Core Web Vitals. Check more often after a migration, a redesign, or a suspected ranking drop. Checking daily isn't useful — the data lags, Core Web Vitals uses a 28-day rolling window, and day-to-day fluctuation is noise you'll misread as signal.
What to do next
Open Performance → Pages, set the comparison to 6 months versus previous, and filter for average position between 11 and 20.
That list is your next month of work. Those pages already rank — Google has already decided they're relevant — and they're invisible only because nobody visits page two.
Free: The SEO audit checklist.
Related guides
- Technical SEO: what actually breaks rankings — the wider audit
- Why isn't my page indexed? — acting on the indexing report
- How to refresh old blog posts — acting on the three lists
- How to track AI search traffic — the AI Mode filter
Join the Newsletter
Get practical marketing tactics delivered straight to your inbox.
Written by
Muhammad Basim
Related Articles
Schema Markup for Blogs: What to Add and How
If you learned schema markup before mid-2026, some of what you know is now wrong. Google retired FAQ rich results entirely on 7 May 2026. Not restricted — retired. The documentation carries a banner saying FAQ rich results no longer appear in Google Search, and Search Console's FAQ reporting and Rich Results Test support were […]
robots.txt and Meta Robots: The Mistakes That De-Index Sites
Two lines of text in a file most people never open can remove your entire website from Google. That's not hyperbole. robots.txt sits at your domain root, it's usually generated by something automatic, and a single Disallow: / pushed from staging to production takes everything down. Quietly. Your site keeps loading perfectly for humans. But […]
Why Isn’t My Page Indexed? A Diagnostic Walkthrough
You published it three weeks ago. It's good. And it isn't in Google. The temptation at this point is to start changing things — resubmit it, add some links, rewrite the intro, submit the sitemap again. Most of that does nothing, because you haven't yet established which problem you have. There are about seven reasons […]