Free tool

Query coverage

Of the clicks and impressions in your Search Console report, how many are in the query rows it returned. Read from the export itself, in your browser, with the remainder called what it is.

How to get the export

1. 01

   In Search Console, open Performance, then Search results.

2. 02

   Set the date range you want read. The export carries the dates only as rows, so the range you pick is the window.

3. 03

   Choose Export, then Download CSV. A zip arrives with seven files in it.

4. 04

   Drop the zip here as it is, or the CSV files from inside it.

What it reads

The seven files as Search Console writes them, recognised by their headers and nothing else. A file with a header the tool does not know is named as such, not guessed at.

Chart.csv

one row per date, the total the others are compared with

Queries.csv

the returned query rows, at most 1,000 of them

Pages.csv

aggregated differently from the chart, so it is expected to differ

Countries.csv and Devices.csv

each adds up to the chart exactly

Search appearance.csv

rows can describe the same page more than once, so it is never added up

Filters.csv

the search type and the date preset the export was made with, quoted as written

What it will not say

That the queries file is complete: exactly 1,000 rows signals possible truncation at the export limit, and fewer rows do not establish completeness, because Search Console also leaves queries out for reasons that have nothing to do with the cap. How much of the remainder is the cap and how much is queries not returned: the export cannot separate them, so neither can this. Anything about what to do: it reports what the files support, and the diagnostic is where the rest of the reading happens.

Google documents four reasons a query table may fall short of the chart, each with a condition on when it applies, and a share of that difference means nothing without the population it was taken against: which reason applies when, and why the denominator has to be stated.

What is counted

Your files are parsed in this browser and never sent anywhere or kept. The one thing recorded is that the tool ran and how it ended, from a fixed list of outcomes, so nothing from a file can be in it. The build that publishes this page fails if that list grows a free-text field.