Search Console export to dashboard

Clicks, impressions and a position you cannot average.

Export the performance report from Search Console and drop the CSV here. CTR arrives as a percent string that no spreadsheet will total, and Position is already an average, so averaging it again gives every query equal weight regardless of whether it had two impressions or twenty thousand. This page recomputes CTR from clicks and impressions, weights position properly, and tells you when the export hit its row cap.

Prefer the full explorer? Open the app, or start from the generic dashboard builder.

CTR recomputed

Clicks over impressions for whatever you have grouped, rather than parsing and averaging a percent column.

Position weighted

Average position is weighted by impressions, so a query with three impressions cannot move the number.

Row cap surfaced

An export sitting at exactly the cap is flagged, because that means the tail was cut off.

No account access

You export the file; the page reads it locally and connects to nothing.

The two most misread columns in SEO

Search Console gives you four metrics and two of them are traps. Clicks and Impressions are honest counts that add up. CTR is a derived percentage written as text, complete with a percent sign, so it sums to zero in Excel and has to be recomputed anyway if you group rows together. Position is the one that causes real damage: it is the average position across all impressions for that row, and averaging a column of averages is not the same operation as computing the average over the underlying data.

That distinction matters because SEO reporting lives on it. A page ranking third for a query with fifty thousand impressions and fortieth for a query with three should not have those two positions averaged into 21.5 and reported as its rank. Weight by impressions and you get something closer to 3.0, which is also closer to the truth. This page does the weighting on every position figure it shows, and it never presents position as something that improved because a bad long-tail query dropped out of the export.

How to export from Google Search Console

Open the Performance report Sign in at search.google.com/search-console and pick the property. Domain properties and URL-prefix properties give different totals for the same site, so know which one you are looking at before you compare against anything.
Set the date range The default is three months and the maximum is sixteen. Longer ranges are more useful for seasonality and slower to load. Comparison mode adds a second period, which the export includes as extra columns.
Apply the filters you want baked in Query, page, country and device filters all travel into the export. Filtering to one page before exporting is often the only way to get useful query detail for that page without hitting the row limit.
Click Export, then Download CSV The Export control is at the top right. It produces a zip containing one CSV per tab: Queries, Pages, Countries, Devices, Dates and Filters. There is no single combined table in the interface export.
Drop the CSV on this page Whichever tab you loaded, CTR is recomputed from the counts and position is weighted before anything is drawn.

For a genuinely combined table of date, query, page, country and device you need the bulk data export to BigQuery, or a Looker Studio connection. The interface export always splits the dimensions into separate files.

Try with sample Google Search Console data (the same columns, 120 rows, no upload needed).

What the dashboard shows

Every panel below is built from a column that is actually in the export, named the way Google Search Console names it.

Clicks and impressions over time. Date on the axis with both series, since a rise in impressions without a rise in clicks is a different story from both moving together.
Query performance. Query ranked by clicks, with recomputed CTR and impression-weighted position beside each, which is the table most SEO work actually happens in.
Page performance. Page grouped the same way, and the queries feeding each page available as a cross-filter where the export carries both dimensions.
Device split. Mobile, desktop and tablet compared on CTR and position, because the same query often ranks differently and converts very differently by device.
Country spread. Country on the map, using the three-letter codes Search Console writes rather than the two-letter ones most other exports use.
Opportunity view. High impressions with a position just outside the first page, which is the classic list of pages worth an afternoon of work.

Sample header row

Date,Query,Page,Country,Device,Clicks,Impressions,CTR,Position

Six Search Console export behaviors

The export caps at 1000 rows. An unfiltered query export gives you the top thousand and silently drops the rest. If your row count is exactly a thousand, you are looking at a truncated file and the long tail is missing.
CTR is a percent string. Written with a percent sign, so it is text. It is also derived, which means recomputing it from clicks over impressions is both easier and more correct than parsing and averaging the column.
Position is an average of averages. Averaging the column gives a three-impression query the same weight as a fifty-thousand-impression one. Weight by impressions or the number is decorative.
Query clicks do not sum to total clicks. Google omits rare queries that might identify an individual searcher, so the queries table always adds up to less than the dates table. The gap is normal and can be sizable on a small site.
Dates are Pacific time. Search Console reports on America/Los_Angeles regardless of where your site or audience is, so the day boundary is not the one your other analytics uses.
The interface export splits dimensions. You get separate files for queries, pages, countries and devices rather than one table with all of them. Joining query to page needs the bulk export or a filtered export per page.

Recompute CTR, weight position by impressions, and check whether your row count landed on a suspiciously round thousand. Those three habits remove most of the wrong conclusions people draw from this report, and the fourth is remembering that missing queries are missing on purpose.

Frequently asked questions

Why does my Search Console export stop at 1000 rows?

That is the row limit on the interface export for each dimension table. You get the top thousand rows by clicks and nothing below. The workaround is to filter before exporting, by page or by country or by a query substring, so each export covers a narrower slice of the tail. For genuinely complete data you need the bulk export into BigQuery, which has no such cap.

Can I average the Position column?

Not straight. Position is already an average across the impressions in that row, so a plain average across rows gives a query with two impressions the same influence as one with twenty thousand. Weight each position by its impressions and divide by total impressions. That is what this page does, and the resulting figure usually looks a lot better and is a lot more honest.

Why do my query clicks add up to less than my total clicks?

Google withholds queries that are rare enough to potentially identify the person who typed them, so they never appear in the queries table but their clicks are still counted in the site totals and the dates table. On a small or highly specialized site the missing portion can be a third of all clicks. The gap is expected and cannot be recovered from any export.

How do I see which queries brought traffic to a specific page?

Filter to that page in the Performance report first, then export. The interface splits dimensions into separate files, so a plain export gives you queries and pages as two unrelated tables with no way to join them. Filtering by page before exporting is the practical route, and it has the useful side effect of keeping you well under the thousand row cap.

Why does Search Console disagree with my analytics?

Several reasons at once. Search Console counts clicks from Google search results in Pacific time, while your analytics counts sessions that actually loaded, in your own timezone. Bounced loads, blocked scripts, redirects and referrer stripping all widen the gap. Expect the two to differ by a noticeable margin and use each for what it is good at rather than trying to reconcile them.

Does this page need access to my Search Console property?

No. There is no Google sign-in and no OAuth grant. You export the CSV from Search Console yourself and drop it here, where JavaScript in your browser tab parses it. That means an agency can look at a client export without being added to the property, and a client can look at what an agency sent without needing an account anywhere.