Google Search Console Query Analyzer
Identify striking-distance queries (positions 8–20) and high-impression low-CTR opportunities from your Search Console performance exports.
Google Search Console Query Analyzer
The demo dataset is synthetic. Replace it with an export from your own Search Console property for real measurements.
These are editable screening cutoffs, not Google benchmarks. Re-run the analysis after changing them. Compare similar queries, positions, devices, locations, and date ranges before interpreting CTR.
No GSC data analyzed yet.
Paste your own Search Console queries or load the clearly labeled synthetic demo data.
Worked Example: Striking-Distance Query Analysis
Example workflow: select a query from your own export, check its landing page and search intent, then compare similar Search Console date ranges after any substantive update.
1. Check the query’s landing page and confirm it addresses the same intent.
2. Compare the page’s content and snippet with current results for that query.
3. Make a change only when you can identify a useful improvement, then compare equivalent Search Console date ranges.
This is a review process, not a traffic forecast. Average position and CTR can vary with query mix, device, location, and search-result features; a before-and-after comparison should use comparable filters and dates.
Frequently Asked Questions
What are "striking distance" keywords in Google Search Console?
“Striking distance” is an informal label, not a Google category. This tool uses average positions 8–20 as a screening range. A query in that range is not guaranteed to move after an update; review the landing page, intent, and current results before making changes.
Why should I optimize high-impression queries with low CTR?
There is no universal impression count or CTR that defines “low.” Choose the analyzer’s editable cutoffs for your report, then compare queries with similar positions, devices, locations, and time periods. A low CTR can have several causes, including the result layout and query intent; changing a title does not guarantee more clicks.
Is my Search Console data kept private?
For this analyzer, CSV parsing runs in your browser. The pasted export is not uploaded to our server by this tool.
How do I export data from Google Search Console for this tool?
Go to Google Search Console > Performance > Search results. Select your desired date range (e.g. Last 3 months), click the "Export" button in the upper right, choose CSV, open the "Queries.csv" file, and paste the rows into this tool.
Companion Strategy & Analysis Tools
Group GSC queries into transactional vs informational intent.
Cannibalization CheckerFind multiple URLs competing for identical search queries.
Content Decay CheckerDetect traffic degradation across historical blog posts.
GSC Regex Filter BuilderBuild RE2 regular expressions for advanced GSC query and page filters.
GSC Brand ClassifierSegment GSC search performance into brand vs non-brand search traffic.