Search Console is the only place Google tells you directly how it sees your site: which queries you appear for, where you rank, which pages it indexes and why it skips the others. It’s free, it’s authoritative, and most sites use a fraction of it, usually the total clicks line.
This guide covers what each report is for, the limits you need to know before trusting the numbers, and five workflows that turn the data into SEO work. Each workflow links to a detailed guide.
What does Search Console show?
| Report | What it tells you | Where to go deeper |
|---|---|---|
| Performance (Search results) | Clicks, impressions, CTR and position by query, page, country, device, search appearance and date | This guide |
| Generative AI performance | Impressions in AI Overviews and AI Mode | AI search traffic |
| Page indexing | Which URLs are indexed, and why the rest aren’t | Crawled - currently not indexed |
| URL Inspection | How Google sees one URL: index status, canonical, last crawl, live test | Crawling and indexing |
| Core Web Vitals | Real-user LCP, INP and CLS by URL group | Core Web Vitals |
| Sitemaps, robots.txt, Crawl stats | How Google reads your sitemaps and robots.txt, and how much it crawls | XML sitemap audit, robots.txt, crawl budget |
The Search Console Insights guide explains how to use its trend cards as a starting point, then confirm a change in Performance. For large properties with query-group cards, query groups explains what a grouped theme includes and why its label is not a separate ranking signal.
The rest of this guide is about the Performance report, where most SEO decisions start.
How do you read the Performance report?
Four metrics, defined in Google’s Performance report help:
| Metric | Definition |
|---|---|
| Clicks | “The number of times a user clicked your site from Google Search results” |
| Impressions | “How many times your site appeared in Search results” |
| CTR | “The click count divided by the impression count” |
| Average position | “The average position of the topmost result from your site” |
You can group them by queries, pages, countries, devices, search appearance and dates, filter by any of them (including regular expressions for queries and pages), and compare two date ranges or two values of a dimension. A comparison adds a Difference column, which is what most of the workflows below sort by.
For a same-day diagnosis, the Search Console 24-hour data guide explains how to read recent performance without treating incomplete hours as a confirmed trend.
To isolate changes in product, video or other result features, the Search Appearance guide explains feature filters and why their rows should not be added up as separate traffic channels.
Discover is a separate, interest-driven surface rather than a query report. Use the Google Discover Performance report guide to read its clicks, impressions, page breakdowns and reporting limits without treating them as Search rankings.
What are the limits of Search Console data?
Know these before drawing conclusions:
- Anonymized queries. Queries searched by very few people are hidden “to protect the privacy of the user making the query.” They’re left out of the tables but included in chart totals, so table rows never add up to the total (Google’s deep dive on performance data).
- Chart and table are aggregated differently. “Data on the chart is aggregated by property,” while data grouped by pages “is aggregated by page”, so totals can differ.
- Row limits. “The maximum you can export through the Search Console user interface is 1,000 rows of data.” The API goes up to “50,000 rows per day per site per search type”; the bulk export to BigQuery is the option for very large sites.
- Average position is an average of the topmost position across all queries, so a page’s single number can hide very different rankings.
- 16 months of history. Enough for year-over-year comparisons, not more; export what you want to keep.
For properties whose analysis runs into row limits or needs repeatable URL-level joins, the Search Console BigQuery export guide explains the daily bulk tables, missing anonymized queries and cost controls.
Five workflows that turn Search Console into SEO work
1. Find pages just off page one
Pages averaging positions 11–20 with plenty of impressions are the cheapest rankings to win: Google already considers them relevant. Filter to those positions, sort by impressions, check the queries, then strengthen the page and its internal links. Full method: striking distance keywords. Work on non-branded queries, where you compete for the click; see branded vs non-branded traffic.
2. Fix snippets that don’t earn clicks
A page in the top five with a CTR far below what’s typical for its position usually has a title or description problem. Compare CTR with position, read the queries, rewrite the snippet. Full method: how to improve organic CTR.
3. Diagnose a traffic drop
Compare the drop period with the one before it and with the same period last year, then break it down by page, query, device and country to see where it’s concentrated. Google’s own guide to debugging traffic drops lists the causes: technical issues, security issues, spam problems, algorithm updates, seasonality and site moves. Full method: why organic traffic drops.
4. Find pages competing for the same query
Filter by a query and open the Pages tab: if several of your URLs share its impressions, or the ranking URL keeps switching, they may be splitting the signals Google would otherwise give one page. Full method: keyword cannibalization.
5. Catch content decay early
Compare the last three months with the same period a year ago, group by page and sort by click difference. Pages losing clicks steadily, not seasonally, are your refresh list. Full method: content decay.
Why join Search Console with a crawl?
Search Console tells you how a URL performed. It doesn’t tell you what the URL is today: whether it now redirects, returns an error, carries a noindex, or has a canonical pointing elsewhere. A crawl does. Put them together and the data becomes actionable:
| Check | What it finds |
|---|---|
| Pages with search traffic return errors | URLs that earned clicks and now return 4xx or 5xx |
| Pages with search traffic are not indexable | URLs with clicks that are now noindexed, canonicalised, redirected or blocked |
| URLs with impressions the crawl did not find | Pages Google shows that your internal links don’t reach |
| Pages ranking just below page one | Positions 11–20 with at least 100 impressions, indexable today |
| Low click-through rate for the ranking position | Top-10 pages with at least 200 impressions and less than half the typical CTR |
| Indexable pages with no search impressions | Pages Google didn’t show at all in the period |
In Crawlens, connect your Google account under Settings → Integrations, choose the property, and fetch Search Console data for a crawl over the last 28 days, 3 months or 16 months. Crawlens pulls page data through the API in batches, so it isn’t limited to the 1,000 rows the interface exports, and matches it to every crawled URL. The overview shows clicks, impressions, average CTR and position, and the top pages by clicks, including pages that weren’t found in the crawl. Each URL’s Search tab shows its numbers, its top queries and a Google index status check with Inspect URL.
Add Google Analytics and two more checks appear: Landing pages with visits return errors and Landing pages with visits the crawl did not find. For the on-site view of organic visits and key events, use GA4 landing page analysis for SEO alongside Search Console clicks and impressions.
How do you build a monthly routine?
- Week 1: check for breakage. Run a crawl with Search Console data; fix any page with traffic that now errors or isn’t indexable.
- Week 2: quick wins. Work through striking distance pages and low-CTR snippets.
- Week 3: losses. Compare the last 28 days with the previous period and with last year; investigate any section or page that dropped.
- Week 4: overlap and decay. Check your main queries for competing pages; pick decaying pages to refresh.
Then crawl again and use Compare to see what changed: fixed issues, new ones, and URLs whose status, indexability or title changed.
Checklist
- Search Console verified for the site
- Performance data read with its limits in mind: anonymized queries, row limits, averaged positions
- Search Console joined to a fresh crawl
- No pages with search traffic returning errors or non-indexable
- Striking distance pages and low-CTR snippets worked through
- Traffic changes checked against the previous period and last year
- Main queries checked for competing pages
- Decaying pages identified and scheduled for a refresh
- Page indexing, Core Web Vitals and crawl stats reports reviewed monthly
All Search Performance guides
- Google Discover Performance report: what the data meansLearn when the Discover report appears in Search Console, how to compare pages and dates, and why Discover clicks differ from Search traffic.
- Branded vs non-branded search traffic: how to separate them in Search ConsoleWhy to split branded and non-branded search traffic, how Search Console's branded queries filter works, and how to use regex when it isn't available.
- GA4 landing page analysis for SEO: find pages that earn traffic but lose outcomesUse GA4's landing page report to isolate organic sessions, compare engagement and key events, and pair Search Console data with on-page fixes.
- Search Console 24-Hour Data: Read Fresh Trends SafelyUse the Search Console 24-hour Performance view without mistaking preliminary hourly data for a final traffic trend. Includes a practical triage workflow.
- Search Console Insights: turn trend cards into content decisionsRead top and trending pages, queries, countries and traffic sources in Search Console Insights, then validate opportunities in the Performance report.
- Search Console query groups: what the Insights cards really meanUnderstand AI-grouped queries in Search Console Insights, group clicks, examples, availability limits and how to validate each theme in Performance.
- Search Console Search Appearance: read the report correctlyUse the Search Appearance dimension to diagnose feature-level changes without confusing rich-result impressions, clicks and page-level totals.
- Content decay: how to find pages losing traffic and refresh themHow to spot pages slowly losing search traffic in Search Console, tell decay apart from seasonality and technical problems, and refresh pages so they recover.
- How to improve organic CTR: find pages with a low click-through rateFind pages that rank on page one but get fewer clicks than their position should earn, work out why, and fix the title, description and rich results.
- Keyword cannibalization: how to find it in Search Console and fix itWhat keyword cannibalization is and isn't, how to spot pages competing for one query in Search Console, and when to merge, differentiate or canonicalise.
- Why did my organic traffic drop? How to find the causeHow to diagnose an organic traffic drop step by step: confirm it, find where it's concentrated, then check technical changes, updates, seasonality and demand.
- Striking distance keywords: how to find your page-two winsPage-two rankings get almost no clicks but are often the cheapest wins. How to find them with Search Console and a crawl, and what to fix first.
Frequently asked questions
What is Google Search Console used for in SEO?
It shows how your site performs in Google Search (clicks, impressions, click-through rate and average position by query, page, country and device) and how Google crawls and indexes it. SEOs use it to find opportunities, diagnose traffic drops and check indexing and page experience problems.
How far back does Search Console data go?
The Performance report lets you look at up to 16 months of data. That's enough to compare the same period year over year and separate seasonal dips from real losses.
Why don't the Search Console table rows add up to the chart total?
Two reasons. Anonymized queries, which few people searched, are left out of the tables but counted in the chart totals. And the chart is aggregated by property while page tables are aggregated by page, so totals can differ.
How many rows can I export from Search Console?
The interface exports up to 1,000 rows. The Search Analytics API returns up to 50,000 rows per day per site per search type, and the bulk data export to BigQuery has no daily row limit, though it still omits anonymized queries.
Is Search Console data the same as Google Analytics data?
No. Search Console counts clicks and impressions in Google Search results; Analytics counts sessions on your site from every channel. The numbers differ because they measure different things and handle privacy and tracking differently.