Backlogs hide impact
Old posts, stale examples, and weak internal links pile up faster than small teams can review them.
Why "refresh the oldest posts" is the wrong rule
The common advice — update your oldest content, or whatever hasn't been touched in a year — ignores the only thing that matters: how much traffic is actually at stake. An old evergreen post that's holding its rankings needs nothing. A six-month-old post quietly sliding off page one is an emergency. Age tells you neither.
A real refresh priority queue is ordered by traffic at risk, not by date. It answers a single question for every page: if I refresh this one, how many clicks am I protecting or recovering?
How RankFade scores priority
RankFade reads your Google Search Console data and scores each decaying page on the factors that predict recovery value:
- Clicks lost — the size of the decline against the page's own baseline.
- Trajectory — how fast it's falling, so steep slides outrank slow drifts.
- Position band — pages near the page-one cliff (positions 5–10) are weighted up, because they're the easiest to recover and the most expensive to lose.
- Confidence — a noisy one-week wobble is ranked below a clear, sustained trend.
The result is a single ordered list. The top five items are your plan for the week; everything below the fold can wait. As pages recover and new ones decay, the queue reorders itself automatically — no spreadsheet maintenance.
Make refreshing a routine, not a scramble
Once the queue exists, the workflow gets simple: take the top item, update it to match current search intent, publish, and let RankFade confirm whether the position recovers. Route the top priorities straight into your weekly content planning so refreshing competes fairly with new-post production.
Get a feel for the inputs with the free domain rank snapshot, see the detection engine behind the queue on the content decay monitor page, or follow the full manual process in the content decay checklist.