An old article is not automatically a problem. The real question is whether it still has a job.
Some pages should be updated because they still match a useful search intent but contain stale, incomplete, or underdeveloped information. Some should be consolidated because they overlap too closely with another page and split relevance. Some should be redirected because their value now lives somewhere else. Some should be left alone because they are stable, low-maintenance, and still serve a purpose. And some should be deleted because they no longer have enough value to justify keeping them in the system.
The mistake is treating every aging page as if it needs the same treatment. It does not. The decision depends on what the page is doing for users, for search, and for the site’s structure.
Start with the page’s current job
Before deciding what to do, identify the page’s present function.
Is it still attracting relevant search demand? Is it linked from important pages? Does it support a cluster or a conversion path? Does it answer a question that still exists, even if the facts have changed? Or is it a leftover asset with no clear role?
This is where a refresh framework helps. If you need a more systematic way to decide which pages deserve attention in the first place, how to decide which SEO content to refresh is the cleaner starting point. The key distinction is that not every page that looks old deserves a rewrite. Some pages are simply not worth the effort.
A useful way to think about this is to separate content value from content condition.
- A page can be valuable but outdated.
- A page can be accurate but redundant.
- A page can be thin but still strategically useful.
- A page can be well-written and still belong nowhere on the site anymore.
The treatment should follow the role.
Update when the page still deserves to exist
Updating is usually the right move when the page still matches a live intent and has some combination of existing demand, links, or usefulness, but the content no longer fully serves the query.
Typical signals:
- The topic is still relevant.
- The page has some organic visibility or backlinks.
- The information is stale, incomplete, or overly narrow.
- The page could be materially better with new examples, clearer structure, or more current guidance.
- The page is close to the right answer but not strong enough to deserve the current version.
Updating works because it preserves the page’s URL, historical signals, and internal references while improving its usefulness. It is usually the least disruptive option when the page already has a legitimate place in the site.
But update only when the page can be made meaningfully better. A cosmetic edit on a weak page is not a strategy. If the page is fundamentally misaligned with search intent, a rewrite may still fail because the underlying page type is wrong.
Consolidate when multiple pages are competing for the same job
Consolidation is often the best answer when you have several pages covering the same or nearly the same intent.
This is not just a content cleanup decision. It is an architecture decision. Multiple overlapping pages can dilute internal links, confuse crawlers, and make it harder for the site to signal which page should rank for a given topic. If that sounds familiar, it is worth thinking about the broader structure as well, not just the individual URLs. How to design an SEO content architecture is useful here because consolidation is often really about fixing topic ownership.
Consolidate when:
- Two or more pages target the same query pattern or user need.
- The pages each cover part of the topic, but none is complete.
- Internal links are split across competing URLs.
- One page has stronger authority and should absorb the useful material from weaker pages.
The tradeoff is that consolidation takes judgment. You need to preserve genuinely distinct subtopics, not just merge everything into one oversized page. If the pages serve meaningfully different intents, merging them can make the final page less useful, not more.
A good consolidation is selective. Keep what is distinct. Remove repetition. Redirect the retired URLs to the strongest destination only when the destination truly replaces them.
Redirect when the old page has been replaced
Redirects make sense when a page no longer needs to stand on its own, but its value should be transferred to another URL.
That often happens when:
- The topic moved to a better page.
- A product, feature, or service changed names.
- Two pages were merged into one.
- An old URL still receives links, traffic, or bookmarks, but the content is now obsolete.
A redirect is a routing decision. It says the old URL is no longer the canonical home for this idea, but the user and any residual signals should land somewhere more appropriate.
Use redirects carefully. Not every old page should point to the homepage or a loosely related article. The destination should be the closest true replacement. If there is no close replacement, a redirect may create more confusion than value.
Redirects also become messy when teams use them to avoid making a deletion decision. If a page has no real successor, forcing a redirect can disguise a structural problem instead of solving it.
Leave it alone when the page is stable and low-cost
Not every old article needs intervention.
Some pages are old but still accurate, still useful, and still connected to the site in a way that makes sense. If a page is not causing maintenance burden, not conflicting with other content, and not missing obvious updates, leaving it alone can be the right decision.
This is especially true for evergreen explainers, reference pages, or pages that serve a narrow but stable intent. A page does not need frequent edits just because it is not new.
The practical question is whether the page is expensive to keep around. If the answer is no, and the page still does its job, intervention may create more churn than value.
Delete when the page has no defensible role
Deletion is appropriate when a page no longer has enough value to justify keeping it in the index or in the site’s content system.
Common cases include:
- The topic is obsolete and has no meaningful replacement.
- The page has no traffic, no links, and no internal importance.
- The content is too thin or too off-topic to salvage.
- Keeping the page creates clutter, duplication, or maintenance overhead.
- The page would require more reconstruction than it is worth.
Deletion is not failure. It is maintenance.
That said, deletion should be deliberate. If a page still has external links, internal references, or residual demand, removing it without a plan can create broken paths and wasted signals. Sometimes a redirect is better. Sometimes a noindex period is useful before removal. Sometimes the right answer is to leave the page live but remove it from navigation and internal promotion.
The question is not whether the page is old. It is whether the page still has any reason to exist.
Evaluate the signals in combination, not one by one
Teams often make these decisions too mechanically: traffic means keep, no traffic means delete. That is too simplistic.
A page with little traffic may still matter because it supports a conversion path, has links from important pages, or covers a niche query that fits the business. A page with traffic may still be a liability if it is misleading, redundant, or hard to maintain. A page with strong backlinks may deserve consolidation rather than deletion. A page with no traffic but a clear strategic role may deserve an update.
The better approach is to evaluate a small set of signals together:
- Intent fit: Does the page still answer a real user need?
- Unique value: Does it add something distinct, or does another page already do the job better?
- Performance: Is it earning visibility, clicks, links, or conversions?
- Maintenance cost: How much work does it take to keep accurate?
- Structural role: Does it support internal linking, topic coverage, or a funnel?
- Replacement quality: If you remove it, is there a better destination?
That combination usually points to the right treatment more reliably than any single metric.
A practical decision pattern
If the page is still relevant and can be improved, update it.
If several pages are competing on the same topic, consolidate them and keep the strongest URL.
If the page has been replaced by another page, redirect it to the closest true successor.
If the page is stable, accurate, and low-maintenance, leave it alone.
If the page has no defensible purpose, delete it or retire it in a way that does not break the site.
That sounds straightforward, but the hard part is not choosing among five verbs. It is understanding what role the page plays inside the larger publishing system. Pages age differently depending on how they are linked, how they are maintained, and whether the site has a process for pruning and updating content over time. That is why SEO content maintenance is not a cleanup task after publishing; it is part of the publishing model itself.
Old articles are not a category. They are a decision tree.