Stale content: when to refresh, redirect, or retire old posts

Every post you have ever published is still working for you, whether you remember it or not. Old articles pull in search traffic, get linked to, get cited, and answer questions you wrote about years ago and have not thought about since. That is the asset. The liability is the same sentence read differently: a post you have not thought about in years is still telling visitors what you knew years ago, even if it is no longer true.

That is what makes stale content awkward. It is not broken in any way a tool can simply repair. A five-year-old tutorial still loads, still ranks, still reads as authoritative. The problem is not that it is there; the problem is that nobody has looked at it lately, and you cannot fix what you have forgotten you own. The first step is just getting the list.

What "stale" actually means

Stale is not the same as old. Plenty of old posts are evergreen, accurate the day they shipped and accurate now. A piece on a timeless idea does not rot. So "stale" is not a verdict on age alone; it is a flag that says this post has not been touched in a long time, so someone should check whether it still holds up.

RecapWP treats it exactly that way. Inside the Content area there is a detect-only check for stale content, aging posts that have gone a long stretch without an edit. It is marked Low severity on purpose, because age by itself is not a defect. The check is not telling you the post is wrong. It is telling you the post is overdue for a human to confirm it is still right.

The real risk lives in the gap between those two things. A post that was accurate when you wrote it can quietly drift out of true: a price changes, a feature is renamed, a recommended plugin is abandoned, a screenshot shows an interface that no longer exists. And because the post still ranks, it keeps sending visitors confident, outdated answers. The traffic is the trap. A wrong page nobody visits is harmless. A wrong page that still ranks is the one worth your attention.

Three doors: refresh, redirect, retire

Once a post is on the list, there are really only three things you can do with it. The skill is matching the post to the right one.

Refresh it

This is the default for anything still pulling its weight. The topic is alive, the post ranks, people read it, and the only problem is that the details have aged. So you bring it current: update the facts, replace the dead references, redo the stale screenshots, add what you have learned since, and republish. The url stays, the inbound links stay, the search history stays, and the page goes back to being true. Most aging posts that matter belong here.

Redirect it

Sometimes the post is not worth updating because you have already said it better somewhere else. Two thin articles on the same topic compete with each other and split whatever authority they have earned. When a post is redundant, the move is to fold it into the stronger page and point a redirect at it, so anyone arriving at the old url, and any link still aimed there, lands on the page you actually want them to read. You keep the value; you stop maintaining two of the same thing.

Retire it

And some posts have simply finished their job. A write-up of a one-off event, a promotion that ended, coverage of a product you no longer offer, a take you no longer stand behind. If it has outlived its purpose and nothing useful redirects to, retiring it is the honest answer. Pruning content that no longer serves anyone is a real edit, not an admission of failure.

The scan can tell you which posts have gone untouched for years. It cannot tell you which of them are still true. Only you know that.

Why this stays your decision

It would be easy to imagine a tool that just deleted old posts, or rewrote them automatically, and a lot of the content-cleanup pitch out there leans that way. RecapWP deliberately does not. Refresh, redirect, retire is an editorial judgment, and it depends on things no rule can read: whether the topic still matters to your audience, whether the post still reflects what you believe, whether two articles are genuinely redundant or just adjacent, what you want your archive to say about you.

This is the line the plugin draws across its whole Content area. The deterministic checks elsewhere can apply a configuration fix because the right answer is the same on every site. "Is this post stale?" has no right answer the code can compute, so it stays detect-only. RecapWP surfaces the aging posts and gets out of the way. The decision is yours, and so is the writing. That is not a limitation; it is the correct division of labor. A machine should never decide what your archive says.

Mark the ones you are keeping on purpose

Here is the part that keeps the list useful instead of nagging. Some of your aging posts are aging on purpose. The evergreen explainer that has not needed an edit in three years because it was right the first time. The cornerstone piece you revisit deliberately on your own schedule. Those are not problems, and you do not want them resurfacing on every scan to be re-decided.

So when you have looked at an aging post and chosen to keep it as-is, you can Mark OK. That tells RecapWP the decision is made, and the post drops off future stale-content results. What is left on the list is genuinely what you have not reviewed yet, which is the whole point. The flag is there to drive a decision once, not to pester you about a call you already made.

Make it a habit, not a project

Content audits get a reputation as a giant once-a-year ordeal because that is usually when people finally do one, all at once, against an archive that has drifted for twelve months. It does not have to work that way. Run the scan, open the Content findings, and look at whatever aging posts have surfaced since last time. For each one, ask a single question: is this still true? Refresh the ones that matter, redirect the redundant ones, retire the finished ones, and mark the deliberate keepers OK. A handful of posts at a time, and the archive never falls far enough behind to become a project.

RecapWP will not write any of this for you, and it will not decide which door a post goes through. What it does is the part that is genuinely hard to do by hand: remember every post you have stopped thinking about and put the aging ones in front of you. The quickest way to find out which of your old articles are quietly out of date is to run a scan and read your own list.