What content decay means
Content decay is a slow drop in a page's search traffic over months, not a sudden fall. A page that once ranked well gets outranked by newer pages, goes out of date, or covers a topic that fewer people search for.
Search Console shows it when you compare two periods page by page. The hard part is telling the causes apart, and that is where the split into impressions and CTR helps.
What you need
- A Search Console property with more than a year of data, so you can compare with the year before.
- An AI app that supports MCP servers, such as Claude, ChatGPT, Codex or Cursor.
- A Search Console MCP server. This guide uses QuerySail's hosted Google Search Console MCP server. Setup takes about five minutes, and the steps for each app are in how to connect Search Console to ChatGPT and Claude.
Five steps
1. Find the pages that lost the most clicks
For sc-domain:example.com, compare the last 3 months with the same 3 months a year earlier, by page. Show the 25 pages that lost the most clicks.
Tool: compare_performance
Comparing with the same weeks a year earlier keeps seasonal changes out of the result. The comparison returns both periods' totals and the pages that gained or lost the most, up to 50 each.
2. Split each loss into impressions and CTR
Compare the same two periods for each of the 5 pages that lost the most, one page at a time. Did the clicks fall because of fewer impressions, or a lower CTR? Show the average position in both periods.
Tool: compare_performance
Filtered to one page, the comparison splits that page's click change into an impressions part and a CTR part. Fewer impressions with a worse position usually means lost rankings. Fewer impressions at the same position usually means fewer people search for the topic. A lower CTR at the same position can mean a weaker title or new search features above the result.
3. Find the queries behind one page
For the page https://example.com/guides/pricing-tips, compare the same two periods by query. Which queries lost the most clicks?
Tool: compare_performance
Filter to one page and break the comparison down by query. One or two lost queries point to a competitor or a change in what people want. A loss spread across all queries points to the page as a whole.
4. Check the page is still indexed
Inspect https://example.com/guides/pricing-tips. Is it indexed, when did Google last crawl it, and is Google's canonical the same as mine?
Tool: inspect_urls
URL Inspection checks up to 20 URLs of one property per call. A page that dropped out of the index, or that Google folds into another page, needs that fixed before any content update helps.
5. Measure the update later
Compare clicks, impressions and average position for https://example.com/guides/pricing-tips over the last 28 days with the 28 days before.
Tool: compare_performance
Run it a few weeks after you update the page. Google may take some time to recrawl the page before the change shows.
Example result
Made-up example. We invented these numbers to show the shape of a result. They do not come from a real site or a QuerySail customer. For sc-domain:example.com, July 28 to October 25, 2026 against the same weeks of 2025, /guides/pricing-tips lost 412 clicks (from 1,630 to 1,218). Most of the loss came from impressions, and its average position fell from 4.1 to 7.8. Two queries, "cupcake pricing" and "bakery price list", made up two thirds of the lost clicks.
Decide what to change
Start with the pages that lost the most clicks and still get impressions. For each one:
- Lost rankings. Look at the pages that now rank above it for the lost queries, and update yours with what it is missing or what has changed.
- Lost searchers. If the position held but impressions fell, fewer people search for the topic. An update may not bring the traffic back, so spend your time on other pages first.
- Lost clicks. If impressions held but CTR fell, check the title and description against what people search for now.
The data shows what changed, not why. Treat your assistant's suggestions as ideas to test, and update one page at a time so you can measure the result.
Check the visits in Google Analytics
Search Console only counts clicks from Google Search. To see whether a page lost visits from other sources too, ask the same question of your Google Analytics data, for example sessions by landing page for the same two periods. QuerySail's Google Analytics MCP server is included on the same plan.
Limits of the data
- History. Search Console keeps about the last 16 months, so a year-over-year comparison covers at most about 4 months.
- Top rows only. Google returns only top rows for query and page breakdowns and leaves out rare queries, so small losses can be missing.
- Average position. Google averages the page's top position across all impressions, so a change of one or two places can be noise.
- Fair use. QuerySail limits requests per day. The limits are on the pricing page.