usdigitalmarketingindex.com SEO
When should an outdated article be refreshed instead of permanently removed?
Updated November 15, 2026
Refresh it when the question it answers is still being asked and the article can be made correct again. Remove it when the subject itself has ended and nothing in the article serves anyone. Between those two sit two further treatments: merge it into a stronger article on the same need, or redirect it to the page that replaced it. The choice depends on four things you can check: whether the topic is still current, whether the content can be repaired, whether other pages link to it, and whether another page already covers the need. Low traffic alone is not a reason to delete. An accurate page that few people need is still useful to those few.
Measuring current usefulness
Establish what the article does today.
- Is the question still asked? Check Search Console for impressions on the article’s queries, and check whether the topic still exists in the world: the product is sold, the rule is in force, the method is used.
- Does anyone arrive? Look at clicks over a full year, so seasonal topics are not misjudged.
- What do visitors do? An article that leads readers on to other pages is contributing, even at low volume.
- Is it wrong, or only old? An old article that is still correct needs a review date, not a rewrite.
Checking recoverable claims and links
Then see what would be lost by removing it.
| What to check | Where | What it tells you |
|---|---|---|
| Links from other sites | Search Console links report, or a backlink tool | Removing the page breaks them unless it is redirected |
| Internal links pointing to it | A crawl | How many pages rely on it |
| Outdated claims | Read the article | Whether the errors are a few figures or the whole premise |
| Unique material | Read the article | Original data, examples, or images found nowhere else on the site |
| Another page on the same need | Site search, the content register | Whether a merge target exists |
If the errors are a handful of dated figures, the article is recoverable. If its central premise no longer holds, such as a guide to a discontinued program, it is not.
Selecting treatment
Follow the tree from the top.
Is the topic still current (the thing still exists, the question is still asked)?
no -> Does the page have links from other sites, or a clear successor topic?
yes -> redirect to the most relevant current page
no -> remove; return 404 or 410
yes -> Does another page on the site answer the same need better?
yes -> merge anything unique into that page, then redirect to it
no -> Can the content be made accurate with reasonable effort?
yes -> refresh in place, same URL
no -> rewrite from scratch at the same URL, or remove
if nobody can own it
Evidence required for each outcome:
| Outcome | Evidence to record |
|---|---|
| Refresh | Topic current; no better page; list of claims to update with their new sources |
| Merge and redirect | The target page; the unique material carried over |
| Redirect only | Topic ended; the successor page and why it is relevant |
| Remove | Topic ended; no external links of note; no relevant successor |
A worked case, with details invented for illustration. A site has a 2021 article, grants available for home battery storage, describing a program that closed in 2023.
- Topic current? The specific program has ended. The broader need, help paying for battery storage, continues.
- Links from other sites? Six, from local news and a community group.
- Better page on the site? Yes, a maintained guide to current home energy incentives.
- Unique material? A table explaining how eligibility was assessed, which is now of historical interest only.
Decision: redirect the old URL to the current incentives guide. Nothing needs merging, since the old table describes a closed program. The six external links now lead somewhere useful.
Had there been no successor guide, the choice would have been between rewriting the article at the same URL as a guide to current incentives, which keeps the links working, and removing it.
A redirect must lead to a page that serves the same need. Sending a retired article to the home page or to an unrelated article gives the visitor nothing they came for. Where no relevant destination exists, an honest not-found response is better.
Documenting outcome
Record each decision in a log, so the reasoning survives.
| Field | Entry |
|---|---|
| URL | The article's address |
| Date reviewed | When |
| Finding | Topic status, accuracy, links, overlap |
| Decision | Refresh, merge, redirect, or remove |
| Target | Redirect destination, if any |
| Actions | Claims updated, content moved, redirect added, sitemap updated |
| Next review | Date, for refreshed articles |
For a refreshed article, update the visible date only when the content changed in substance, and update internal links if the article’s focus shifted. For a removed or redirected one, fix internal links that pointed to it so that the site does not send its own visitors through a redirect or to an error.
Review old content on a schedule instead of in a purge. Deleting large numbers of pages at once on the basis of a traffic threshold removes accurate pages along with poor ones, and the effect of each removal cannot be seen.
Refreshing can come down to updating figures and sources, which has a method of its own. That is covered in the guide to what to recheck when an evergreen article’s statistics become outdated.
The rule: a page is removed because its subject has ended, not because its numbers are small.
Add your comment to this answer