Search Console risk tracker
Paste baseline and current Google Search Console CSV exports, or a single comparison CSV, to find query and page pairs where impressions rose while clicks or CTR fell. The output is a proxy risk report, not proof that AI Overviews caused the change.
Use either separate baseline and current exports, or paste a combined comparison CSV. Combined data takes priority when present.
Paste matching baseline and current GSC exports, or lower the minimum impressions threshold, if you expected rows to be flagged. A clean result does not prove there is no AI Overview exposure.
Export the same Search Console dimensions for two comparable date ranges. Query and Page are the best dimensions because the tracker can compare the exact search demand against the destination that earned visibility. Paste the older period into the baseline field and the newer period into the current field. If your export already contains baseline and current columns, paste it into the combined comparison field instead.
The analysis aggregates duplicate query and page rows, then compares clicks, impressions, CTR, and average position. It looks for patterns that are easy to miss in a raw CSV: impressions increasing while clicks or CTR drop, stable or improved rankings with weaker CTR, and informational queries where a quick answer may satisfy the searcher before the click.
A high severity row means the pattern deserves manual review. It does not mean Google showed an AI Overview, and it does not prove a SERP feature caused the drop. Use the diagnosis to build a review queue: check the live SERP, keep dated screenshots, compare title and snippet presentation, and look for competing tools, videos, forum answers, or other features that may reduce clicks.
Recommended actions are intentionally practical. Some pages need a clearer title and answer block. Others need a stronger reason to click, such as original data, examples, screenshots, a calculator, a template, or a checklist. Informational queries are most vulnerable when the page only repeats a short answer that the SERP can summarize.
Search Console does not label AI Overview exposure in standard query exports, so this tracker cannot attribute causality. CTR can change because of ranking mix, seasonality, brand demand, title changes, snippets, ads, local packs, images, videos, competitors, device mix, country mix, or measurement lag. Treat the output as prioritization for investigation and content work, not as final evidence.
Use the GSC Query Opportunity Finder to find broader refresh opportunities, the Website RPM Simulator to estimate revenue impact, and the Invalid Traffic Checklist when traffic quality, not SERP behavior, is the concern. Preserve dated observations in the AI Search Visibility Log Template.
No. This is a proxy risk tracker. It compares Search Console query and page metrics across periods and flags patterns that deserve SERP review, but it cannot prove AI Overview attribution by itself.
Use query and page exports with Query, Page, Clicks, Impressions, CTR, and Position columns for a baseline period and a current period. A combined comparison CSV can also work when it includes baseline and current metric columns or a period column.
No. The tracker runs client-side in the browser for this MVP. It does not connect to Google Search Console and does not upload your pasted CSV to RedBit SiteOps or Google.
Treat it as a review queue. Check the live SERP, capture dated evidence, compare snippets and AI Overview exposure where available, then improve the page with original data, clearer titles, tools, templates, checklists, or stronger internal links.