Does this tool connect to Google Search Console?
No. This MVP does not use Google OAuth or connect to your Search Console account. Paste two CSV exports into the browser and the comparison runs client-side.
Search Console workflow
GSC Page Decay Detector
Paste an older and newer Google Search Console CSV export to find pages losing clicks, impressions, CTR, or average position. The output is a practical refresh queue with the next action for each page. CSV data is processed in your browser and is not uploaded.
Paste Search Console CSV Exports
Paste an older export and a newer export with the same Page dimension. Query rows are fine: the detector aggregates them into page-level decay signals.
Use Page, Clicks, Impressions, CTR, Position, and optional Query columns.
No page decay found
Paste matching exports with Page data, lower the thresholds, or compare longer periods if you expected declines. A clean result only means the pasted rows did not match these decay rules.
Copyable action list
CSV export text
How To Use This Detector
Export the same Search Console dimensions for two comparable periods. For page decay work, the Page dimension is required. If you include Query as well, the detector aggregates query rows into page-level metrics and keeps a few sample queries in the action list.
Use the older period as the baseline and the newer period as the current export. The detector compares clicks, impressions, CTR, and average position, then flags pages where traffic dropped enough to deserve a refresh, snippet rewrite, internal-link pass, or demand investigation.
How To Interpret Page Decay
A ranking decay result usually means the page needs a content refresh, stronger topical coverage, or more internal links. A snippet decay result means visibility is still present, but clicks or CTR weakened, so title, meta description, intro, and SERP promise should be reviewed. Demand decay means impressions fell without a clear ranking loss, so seasonality, country and device mix, indexing, and query shifts should be checked first.
Limitations
This tool does not prove the reason for a decline. Search Console exports can lag, aggregate data, and shift with query mix. Always review the live SERP, page changes, internal links, indexability, and competing pages before rewriting or consolidating important URLs.
Related Tools
Use the GSC Query Opportunity Finder to find query-level refresh candidates, the Search Console Daily Report Generator to summarize the day, and the CTR Rewrite Lab to prepare snippet experiments.
FAQ
What columns should my CSV include?
Use Page, Clicks, Impressions, CTR, and Position. Query is optional, but useful when you want sample query context for each decaying page.
Can this prove why a page lost traffic?
No. Search Console data can show decay patterns, but the cause may be ranking changes, snippet changes, seasonality, SERP features, indexing, country mix, device mix, or competitors.
What should I do with a high priority page?
Open the page and current SERP, check whether rankings, snippets, and intent changed, then refresh the page, rewrite the snippet, add internal links, or investigate demand before making large changes.