Introduction
If you only learn one report in Google Search Console, make it the Performance report. It is the only first-party source of the actual queries people typed before Google showed your site — and it connects those queries to the pages that earned them, the countries they came from, and the devices used.
Used badly, it is a wall of numbers. Used well, it answers four practical questions: what are people finding us for, which pages are doing the work, where are the near-misses we can improve, and is anything suddenly going wrong? This guide shows you how to read it, filter it, and turn it into a short action list.
Open the report and read the four metrics
Open Search Console, choose your property, then go to Performance, and make sure you are on the Search results view (Discover and Google News have separate reports). By default you will see the last three months, though you can choose a range of up to 16 months.
The chart shows four metrics you can switch on and off:
- Total clicks — how often someone clicked a result leading to your site.
- Total impressions — how often your site appeared in search results at all.
- Average CTR — clicks divided by impressions, as a percentage.
- Average position — where your results ranked on average (lower is better; position 1 is the top).
The golden rule: never read one metric alone. High impressions with low clicks usually mean a title or snippet problem, not a ranking problem. High clicks with a low average position means a small number of strong pages is carrying the site. A falling click count with steady impressions points to lost visibility or weaker snippets, while falling impressions point to fewer queries showing your pages at all.
Data also arrives with a delay of a couple of days, so do not panic over the most recent day or two — check the trend over weeks instead.
The six tabs: what each one answers
Below the chart, tabs break the same data down by dimension:
- Queries — the exact search terms people used. Start here when you want to know what demand you already earn.
- Pages — which URLs appeared in search. Start here when you want to know which pages carry your visibility.
- Countries — where impressions and clicks came from. Use it to check whether a page meant for one market is quietly ranking elsewhere, or whether a new audience is emerging.
- Devices — mobile, desktop, and tablet splits. A page that performs well on desktop but poorly on mobile may have a mobile experience problem, not a content problem.
- Search appearance — how results appeared (for example, with rich results or other features).
- Dates — performance over time, useful for spotting a change on a specific day.
A reliable working order is: Queries → Pages → Countries → Devices. Clicking a row in one tab filters the whole report to that row, which is the fastest way to drill down — click a query to see which pages rank for it, then click a page to see which queries it earns.
One caution: the table stops at 1,000 rows, and rare queries are hidden for privacy, so the rows will not always add up exactly to the chart total. That is normal, not an error.
Filtering and comparing without getting lost
Click + Add filter to narrow the report by query, page, country, device, or search appearance. Query and page filters accept exact matches, “containing” matches, and custom regular expressions for pattern matching. A “containing” filter is usually enough: filter queries containing your brand name to separate branded from non-branded demand, or filter pages containing “/blog/” to isolate blog performance.
Comparison is where the report earns its keep. Use the date control to compare two periods side by side — for example, the last 28 days against the previous 28 days — and the report adds a difference column so gains and losses are visible at a glance. You can also compare one country against another, or one page against another. Note that you can run only one comparison at a time, so do one question per pass: trying to compare dates and countries simultaneously is how reports get confusing.
Practical tip: before changing anything on your site, take a screenshot or export of the current view. Without a baseline, you cannot tell later whether a change helped.
Three checks that produce real actions
1. The quick-win check (high impressions, positions 8–20)
Sort the Queries tab by impressions and look for queries with plenty of impressions and an average position roughly between 8 and 20 — just off page one, or at its bottom. These are the closest to a meaningful gain. For each one, switch to the Pages tab to find the page that ranks, then improve that page: sharpen its answer to the query, strengthen its title, add the missing subtopic, or add internal links from related posts. Improving the page that already ranks is almost always faster than writing a new one for the same query.
2. The low-CTR check (impressions without clicks)
Sort by CTR (ascending) on pages or queries with meaningful impressions. A page with many impressions and a low click-through rate is being shown but not chosen. Before rewriting content, check the snippet first: is the title clear about what the page delivers? Does the meta description answer the searcher’s question or merely repeat keywords? Does the page actually deliver what the title promises? Fix the snippet and the opening section before assuming the whole article is wrong.
3. The “what changed?” check (compare periods)
When traffic moves sharply, compare the current period with the previous one and sort by the difference in clicks. If one page accounts for most of the change, investigate that page: was it edited, did its ranking slip for its main queries, or did demand itself change? If many pages fell together, look site-wide — indexing, a template change, or a Search Console coverage issue are more likely than dozens of simultaneous content problems.
Turning the report into keyword research
The Performance report doubles as a keyword research tool for a site that already has some visibility, because it shows real queries rather than estimates:
- Open Queries, sort by impressions, and note queries your site already appears for but does not yet answer well.
- Group related queries into topics instead of chasing each phrasing separately.
- For each topic, decide: improve the existing page, expand it with a new section, or — only if the intent is genuinely different — write a new page.
- Avoid creating a new page that competes with one you already have for the same query; that splits your own visibility and confuses readers.
This is exactly how a small site grows sensibly: it earns a little visibility, reads what real searchers typed, and then serves those searchers better — rather than guessing at keywords from scratch.
What the Performance report cannot tell you
Search Console shows how your site appears in Google Search. It says nothing about competitors, and it does not track what visitors do after they land — that is Google Analytics’ job. It also does not tell you why Google ranks a page where it does; position is an outcome of many factors, not a score you can adjust directly. Treat the report as a diagnostic instrument, not a ranking lever: it tells you where to look and what to fix, and the fixes themselves are better content, clearer titles, working pages, and honest answers to real queries.
A 15-minute weekly routine
For most small sites, this is enough:
- Open Performance → Search results, last 28 days, and glance at the chart for anything dramatic.
- Check Queries sorted by impressions for new or rising terms.
- Run the quick-win check (positions 8–20, high impressions) and pick one page to improve.
- Run the low-CTR check and pick one title or description to sharpen.
- Note the one change you made, so next week’s comparison means something.
That routine, repeated weekly, beats a quarterly deep dive every time — because search performance moves gradually, and small, steady improvements compound.
Frequently asked questions
Why do the table rows not add up to the chart total?
Rare queries are hidden for privacy and the table is capped at 1,000 rows, so totals will differ. Use the chart for totals and the table for patterns.
How far back does Performance data go?
Up to 16 months. Use longer ranges for seasonal comparisons and shorter ones (28 days) for recent changes.
Does requesting indexing change Performance data?
No. Indexing affects whether a page can appear; the Performance report then measures what happens once it does.
Is a low average position always bad?
Not necessarily. Average position blends all queries, including obscure ones. Judge a page by its position for its main queries, not by a site-wide average.
