Free content decay checker

Export your Search Console pages

1. Open Performance > Search results for the same property. Select an earlier custom date range, then open the Pages tab.
2. Export as CSV and select the Pages.csv file from the downloaded archive. Repeat for the recent range, keeping search type, country, device and other filters identical.
3. Count every calendar day in each range, including both endpoints. Use complete periods; avoid partial recent days.

See Google's export documentation. Report exports are truncated to 1,000 rows, so missing URLs do not establish lost traffic.

Compare your exports

Required columns: Page (or Google's Top pages) and Clicks. Each URL must occur once per file. URLs match exactly; redirects and canonical variants are not merged.

Measured results

Interpret your review candidates

Earlier clicks/day = earlier clicks / earlier days. Recent clicks/day = recent clicks / recent days. Daily clicks lost = max(0, earlier daily clicks - recent daily clicks). Percentage decline = daily loss / earlier daily clicks * 100. Zero baselines have no defined percentage decline.

Results include stable and growing matched URLs, sorted by daily clicks lost. For example, 280 versus 140 clicks over two 28-day periods means 10 versus 5 clicks/day: 5 lost clicks/day and a 50% decline. Over 28 versus 14 days, those totals have equal daily rates.

Declining clicks identify review candidates rather than prove content decay. Inspect queries, impressions, rankings and indexing, then use our website traffic drop diagnosis guide. For ongoing monitoring, see MrKeyword traffic drop alerts.

Comparison limitations

Use the same property and filters. Seasonality, holidays, weekday mix, changing demand, Google updates and search result features can affect clicks without stale content. Daily normalization corrects period length, not these causes. Small baselines can produce large percentage swings.

Export truncation can remove pages from either file. This tool compares only URLs present in both exports and cannot estimate site-wide losses from incomplete tables. It checks file structure, not your selected date ranges or filter settings.

FAQs