Fixes and Playbooks

Should You Refresh, Retire, or Hold a Decaying Page?

A traffic drop does not automatically mean a page needs rewriting. Use Search Console and a live-page review to choose the action the evidence supports.

A webpage connected to five options: refresh, consolidate, retire, hold, or investigate.

Quick answer

A traffic drop is a signal to investigate, not an instruction to rewrite. Compare consistent periods and filters in Google Search Console, check alternative explanations, and inspect the live page. Then choose the smallest supported action: refresh, consolidate, retire, hold, or investigate a different cause.

Before you rewrite a declining page

Traffic falls, and the instinct is immediate: add a few paragraphs, change the date, and republish.

But a content update only helps if the content is part of the problem. A seasonal drop, an indexing issue, and an outdated answer can produce similar-looking charts. They need different responses.

Start by identifying what changed. Then choose the smallest action the evidence supports.

Why a traffic drop is a signal, not an instruction

A drop tells you where to investigate. It does not tell you what caused it.

In Google Search Console, compare equal-length periods using the same filters. Look at clicks, impressions, click-through rate, and average position together. Where seasonality could matter, also compare with the same period a year earlier.

Treat the patterns as clues:

  • Clicks fall while impressions and position remain broadly stable: investigate click-through rate, the queries bringing impressions, and changes in the search results. This pattern alone does not prove that an AI Overview caused the decline.
  • Impressions fall while position remains broadly stable: check whether demand has fallen or the page is appearing for a different mix of searches.
  • Position and impressions decline together: investigate ranking changes, competing results, and whether the page still answers the relevant queries.
  • Traffic drops suddenly across several pages: check indexing, technical changes, and wider site patterns before rewriting individual articles.

Page-level averages can hide differences. Break the comparison down by query, country, and device where needed.

Google's guidance on traffic drops identifies several possible causes, including technical issues, ranking changes, seasonality, and changing search interest. Use those possibilities to guide the investigation rather than treating every decline as content decay. Read Google's guide to diagnosing search traffic drops. (https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops) Read Google's guide to diagnosing search traffic drops. ↗

Choose the action the evidence supports

Inspect the live page alongside the search data. Identify what remains useful, what is materially wrong or missing, and whether another page already serves the same reader need.

Choose one of five routes:

  • Refresh: the page still serves a useful purpose, but its facts, examples, instructions, or coverage need a meaningful update.
  • Consolidate: two pages substantially overlap in purpose, and combining their useful material would create a clearer destination. Sharing a keyword is not sufficient reason to merge them.
  • Retire: the page no longer serves a useful purpose. Check relevant links, conversions, and continuing reader needs before removing it. Redirect only when there is a genuinely relevant replacement.
  • Hold and monitor: the evidence does not yet justify a change. Record what you will watch and when you will review it.
  • Route elsewhere: the problem needs a different response, such as an indexing fix, search-snippet review, or investigation of overlapping pages.

Changing the date or adding filler does not resolve an outdated answer. A useful refresh changes something that matters to the reader.

Record the decision before changing the page

Write a short decision note:

  • What changed, and over which comparison periods?
  • Which alternative explanations did you check?
  • What does the live page get right or wrong?
  • Which action will you take, and why?
  • When will you review the result, and what would make you reconsider?

AI can help organise exports, compare page versions, and suggest gaps to investigate. Check those suggestions against the actual page and data before acting.

Put the method into practice

Use Altiv.AI's Content Recovery Play to work through the diagnosis and document your decision.

Work through a declining page

Use a structured process to investigate the decline and document your next action.

Open the Content Recovery Play →

To examine your work more broadly, start with the AI Readiness Score. It helps you consider which tasks could be automated, which could be improved with AI assistance, and which require human judgment.

Choose what to practise next

Explore tasks in your role with Altiv.AI's AI Readiness Score.

Get your AI Readiness Score →
Written by Varun Dhamija

Founder, Altiv.AI