When to Update, Rewrite, or Retire a Page
A decision framework for content refreshes — how to tell whether a page needs a tune-up, a full rewrite, or removal.
Key Takeaways
- Refreshing for usefulness is different from changing dates to fake freshness.
- Match the action to the diagnosis: update, rewrite, merge, or retire.
- Pruning weak pages can strengthen the rest of the site.
Maintenance Is Part Of Publishing
Every page you publish becomes something you own and maintain. As a library grows, the unattended pages quietly accumulate: advice that aged out, queries that shifted, posts that never found an audience. Left alone, they drag on the credibility and clarity of the whole site. A content-maintenance habit is what separates a library that compounds in value from one that slowly decays.
One principle keeps this honest. Updating a page because it is genuinely more useful is good work; swapping the date to look fresh while changing nothing substantive is the kind of manipulation Google's guidance warns against. The reader should be able to tell what improved.
Update: A Targeted Tune-Up
Choose an update when a page is fundamentally sound but has drifted out of date. The core argument still holds, it ranks or earns traffic, and it just needs accuracy and freshness restored. This is the lightest-touch option and usually the highest return on effort.
- Correct outdated facts, figures, screenshots, or platform references.
- Add a new section addressing a question readers now ask.
- Tighten or add answer blocks and internal links.
- Refresh the title and description if click-through rate has slipped.
Rewrite: Same Topic, New Foundation
A rewrite is the right call when the topic still matters but the existing page no longer does it justice — the structure is weak, the advice is shallow, or the original missed the actual search intent. Here you keep the URL and the topic but rebuild the content from a stronger outline, so you retain whatever authority the page has earned while fixing what made it underperform.
Rewrites take more effort than updates, so reserve them for pages with clear potential: a topic with real demand where you know you can produce something substantially better than what is live.
Merge Or Retire: Cutting The Dead Weight
Sometimes the best move is to stop maintaining a page. If two or three thin posts cover overlapping ground, merge them into one strong resource and redirect the old URLs — you consolidate authority instead of splitting it. If a page targets a topic with no demand, attracts no traffic, and serves no strategic purpose, retiring it can actually help, because a leaner site of strong pages is easier for search engines to evaluate than a large one padded with weak ones.
When you retire a page, redirect it to the most relevant alternative rather than leaving a dead end. Pruning is not failure; it is editing.
A Repeatable Refresh Routine
Make the decision systematic instead of reactive. On a regular cadence, pull your pages and sort them by trend: traffic declining, flat, or growing. For each underperformer, ask whether the topic still has demand and whether the page is the best version of itself. That single pair of questions routes you to update, rewrite, merge, or retire.
Prioritize pages that depend on things that change — platform behavior, structured-data rules, local policies, and AI search interfaces all move, and the pages built on them age fastest. Fold this routine into your content calendar so maintenance is scheduled, not improvised.