How to use the Google Search Console Performance report
The report shows clicks, impressions, CTR and average position for your property, grouped by query, page, country, device, search appearance or date. Most surprises come from how the numbers are aggregated, filtered and cut.
✓ Checked against Google Search Console Help · October 2026
Open the Performance report, pick the metrics, a dimension tab and a date range, add filters, compare two groups if you need to, and read the chart and the table as two different aggregations. That last point is where most surprises come from. Google describes the report in its overview and explains how the numbers are grouped in About the data.
Metrics, dimensions and dates
The report has four metrics: clicks, impressions, CTR and average position. Dimensions group the table by Queries, Pages, Countries, Devices, Search appearance or Dates. The default view covers the last three months. Search type can be web (text-based or multimodal), image, video or news.
The 24-hour view is hourly and includes preliminary data. For longer periods, weekly or monthly granularity smooths the swings between days, and it has a practical benefit: it stops a Monday from being set against a Saturday.
Filters and regular expressions
You can filter by several dimensions at once. The options “Queries containing” and “URLs containing” take one substring and ignore case. For several values, or for exclusions, use Custom (regex). Search Console uses the RE2 syntax, which has no lookahead such as (?!...), so a pattern copied from another tool may be rejected; to exclude something, choose Doesn’t match regex instead. Matching is partial and case-insensitive unless you add (?-i). Details are in the help on advanced filtering and comparison.
Comparing two groups
Compare two values of one dimension, such as two countries or two periods. Only one comparison works at a time. For dates, prefer weekly or monthly granularity or matching weekdays, so that the weekly rhythm of your traffic does not pose as a trend.
Why the chart and the table disagree
The chart is aggregated by property. The table is aggregated by property for queries, countries, devices and dates, and by page for pages and search appearance, so their totals can differ. Take one user who sees three pages of your site for a query and clicks all three. By property that is one impression, one click and position 1, so CTR is 100 percent. By page it is one impression for each URL, a click on each, positions 1, 2 and 3 and a CTR of 33 percent per URL. Neither is wrong; they answer different questions.
Two more reasons add to the gap. The table shows at most 1,000 rows, and anonymized (rare) queries are left out of the table but kept in the chart totals unless you filter by query (troubleshooting data discrepancies). The same article is behind our own piece on why SEOKit numbers differ from Search Console.
History and the newest days
Search Console keeps data for the last 16 months (Analytics help), so save an export or use the API if you need more. The newest data can be preliminary and may change within hours; the report shows complete days by default and a last updated date. Daily data are in Pacific Time, which is why a day can shift against other tools.
Exports, the API and Looker Studio
The interface exports to Google Sheets, Excel or CSV, truncated to 1,000 rows of representative examples, while the totals stay actual (export help). The API returns up to 50K rows per day per search type per property, and a bulk export to BigQuery removes that ceiling. The Looker Studio connector offers Site Impression (aggregated by property) and URL Impression (aggregated by page); one data source can use only one, so build two to see both (connector help). Our piece on export rows and columns covers the SEOKit side.
Discover and keyword research
The Discover report appears only after the property reaches a minimum number of Discover impressions; rows below the threshold are hidden but still counted in the totals (Discover performance report). As for keyword research, the report can help, with care: the queries are real, but rare queries are anonymized and omitted from the table, and a query you see may not show your site when you search it yourself, because results depend on time, place, device and history.
The SEOKit side
SEOKit’s default filters use the same RE2 syntax, and its export tool goes beyond the 1,000-row interface limit through the API. For the numbers themselves, clicks versus impressions and what a good CTR is explain how to read them.
Go further
Data and metrics: Clicks, impressions, CTR and position. Reports and tools: How the SEOKit reports work.
Official sources
- Search Console help: Performance report overview ↗
- Search Console help: About the data ↗
- Search Console help: advanced filtering and comparison ↗
- Search Console help: data discrepancies ↗
- Search Console help: export data from a report ↗
- Search Console help: Discover performance report ↗
- Looker Studio help: connect to Search Console ↗
- RE2 syntax ↗
- Analytics help: Google organic search traffic report ↗