Tools

Each one answers a question from a Search Console export you already have, in your browser, and says what the export cannot answer. No login, no key, nothing uploaded and nothing kept.

1. Query coverageOf the clicks and impressions in your report, how many are in the query rows it returned.It never calls the remainder missing or anonymised: the export cannot separate the row cap from the queries Search Console does not return.Open the tool
2. Comparison calendar checkFor two periods you name, what the calendar of the comparison supports: length, coverage, overlap and weekdays.It never calls a comparison fair. Demand, filters, the page and query mix and whether the newest days are final are outside the file, and it says so every time.Open the tool

What every tool holds to

A file is recognised by its header and nothing else, so a file the tool does not know is named as such rather than guessed at. Every figure comes with its source file, its window and its row count. A rate a file states is never used for arithmetic, only checked against the counts. Where the file cannot support an answer, the tool says what it cannot say and why, instead of saying less about it. The one thing recorded when a tool runs is that it ran and how it ended, from a fixed list of outcomes; the build that publishes these pages fails if that list grows a free-text field.

None of them returns a single number for how visible a site is, which is the shape most tools in this area take: what a search visibility score estimates, and what it cannot see.