Free tool
The searches you already rank for and get nothing from
Google is probably showing your pages to people already. The question is which of those near misses you can turn into clicks without writing anything new. Drop in the CSV Search Console already exports and read the three answers.
No sign-up, no account, no API key. The file never leaves your browser.
Or drop your own below. Everything runs in this page; no file is uploaded.
Questions
How do I export the CSV from Google Search Console?
Open Search Console, go to Performance, set the date range to the last three months, and press Export at the top right. Choose CSV and you get a zip containing Queries.csv and Pages.csv. Drop both into the page above. Queries.csv on its own runs one of the three checks; adding Pages.csv runs all three.
Is my Search Console data uploaded anywhere?
No. The file is read by your own browser and the checks run there. Nothing is sent to a server, nothing is stored, and closing the tab discards it. You can confirm this by opening the network tab while you use it, or by turning off your connection first.
Why do two pages with the same slug matter?
When two of your URLs end in the same slug they are usually about the same thing, so they compete for the same search. Google then has to choose, and it frequently ranks neither well. We had exactly this: a blog post and a docs page on the same topic, both sitting past position 75. Consolidating one into the other is a morning of work and it recovers a ranking you already paid to earn.
What counts as a search you "nearly win"?
A query whose average position is inside the first two pages of results, with at least five impressions, that is earning few or no clicks. The position is already there, so the work is the title, the opening lines and whether the page actually answers the question, rather than a new page.
Does it tell me whether a search is worth winning?
No, and that is deliberate. It cannot tell a buyer from a bot. Our own sample is full of searches we rank well for that will never produce a customer, including a competitor-monitoring robot and some plain junk strings. Read the actual searches before acting on any of them. A tool that scored intent for you would be guessing.
Why does it not just tell me what to fix?
Deciding whether a theme deserves a new page or a section on an existing one is the judgement the tool cannot make, and guessing it is how a site ends up with pages competing against each other in the first place. The finding is the useful part. The fixing is a separate job, and it is the job we do for teams who would rather not keep doing it themselves.
Is there a command line version?
Yes, and it is free and MIT licensed at github.com/hrshitkunwar-tech/gsc-gap-audit. It is standard-library Python with no dependencies. It also takes a query-and-page export, which lets it report true query-level collisions rather than the duplicate-slug check this page runs.
Turn your Search Console gaps into closed pipeline
Once you know which high-intent searches you rank for, the next step is building the high-converting comparison pages, prompt-map workflows, and post-call automation layers that turn impressions into booked revenue. We engineer that first workflow free inside your own tools.