An old article does not need a rewrite simply because its publication date looks old. It needs attention when the answer is inaccurate, incomplete, difficult to use or no longer aligned with the page’s purpose. A refresh review should identify that problem before choosing an action. Otherwise, an editor can spend a day changing sentences while leaving the actual weakness untouched.
Begin with the reader’s task. Open the article as someone trying to complete it today. Check the instructions, examples, references and linked destinations. Record what fails or feels unresolved. Then look at performance data for context. The content review and the numbers should inform each other, but neither should substitute for the other. A useful niche resource may attract little traffic and still deserve maintenance.
Classify the reason for review
Use specific triggers: a changed product interface, a broken source, an outdated recommendation, a repeated reader question, a drop in relevant visibility or overlap with another article. Several triggers may apply. Write them down separately so the eventual change can be evaluated against the actual problem rather than a vague request to make the page fresher.
Check whether the issue belongs to the article or the template. A broken table on every mobile page is a site repair. A single misleading comparison belongs in the editorial queue. Our technical audit method helps separate those scopes. Fixing a template first may resolve the usability problem without requiring a substantial rewrite of otherwise accurate content.
Update when the page still owns a clear answer
Keep the existing article when its purpose remains useful and distinct. Replace outdated steps, strengthen explanations and remove claims that cannot be supported. Preserve the parts that still work. A focused update is easier to review than a complete rewrite because the editor can identify exactly what changed and why.
Retest any procedure affected by the update to the extent your environment allows. If the piece relies on vendor documentation rather than hands-on use, maintain that distinction. A refreshed screenshot should depict the relevant current interface and have an appropriate caption. Do not add a new year to the headline unless the article’s scope and review justify presenting it as a current edition.
Merge when two pages compete for the same job
Compare the intended outcomes of overlapping articles. If both answer essentially the same question, choose the stronger destination and incorporate any useful material from the other. The surviving page should become more coherent, not simply longer. Remove duplicated introductions and reconcile conflicting advice before publishing the consolidated version.
Use a redirect mapping record to document the retired address, replacement and rationale. Review incoming internal links in context. A destination change can alter what the anchor promises, particularly when a narrow tutorial becomes part of a broader resource. Retain the original source and revision history internally so future editors can understand where the consolidated material came from.
Retire when there is no useful current answer
Some pages describe discontinued products, expired offers or a subject the publication no longer covers. Retirement may be appropriate when the page has no remaining reader value and no relevant replacement. Do not force it into a vaguely related guide merely to avoid a missing-page response. The absence of a suitable successor is a legitimate editorial conclusion.
Consider archival value separately from search potential. A clearly labeled historical explanation may still help readers understand an older reference. If you keep it, make the outdated status visible and avoid presenting obsolete instructions as current advice. If you remove it, retain an internal record of the decision and any important links that motivated the review.
Use performance data as a diagnostic clue
Compare equivalent periods and inspect the affected queries and pages. A decline may reflect seasonality, a change in demand, technical exclusion or a different mix of searches. It does not automatically mean the prose is poor. Read the page against the questions it now attracts and identify the missing answer before commissioning a rewrite.
Our measurement baseline provides the context needed for this comparison. Log the refresh date and the specific hypothesis. For example, a revised introduction might clarify that the guide applies to a particular CMS. The expected benefit is a better match between the promise and the answer, not an assured percentage increase in traffic.
Keep dates and attribution accurate
Use the actual original publication date and a modified date when a meaningful revision occurs. Google’s Article structured-data documentation describes publication and modification properties alongside author information. Align machine-readable dates with the visible page and the real editorial history. A changed date should not imply a substantive review when only punctuation was adjusted.
For a major correction, explain what changed where readers need that context. Keep the author attribution accurate; a new editor does not automatically become the original author. A publication can credit a review or update separately. This is particularly useful when a technical guide is maintained by a team over time and readers need to know who is currently responsible for its accuracy.
Make the refresh queue sustainable
Prioritize pages with consequential inaccuracies, broken workflows or clear reader demand. Group related updates when a product change affects several articles. Assign a maintenance owner and a review trigger to each important resource. Avoid a calendar that requires the entire archive to be rewritten every quarter regardless of need; that rewards activity over editorial value.
Close the task only after previewing the updated page, checking links and recording the change. Schedule a later observation when the hypothesis depends on search behavior. If the result remains inconclusive, retain that finding rather than inventing a success story. A well-maintained archive grows stronger through accurate decisions, including the decision to leave a useful article largely alone.
Explore more in Publishing.
Written by
Mara Ellis
Mara Ellis is an editorial pen name used by Approve SEO for publishing and search guidance. The byline covers article planning, content repurposing, corrections, internal linking and maintaining useful evergreen resources. Articles attributed to Mara follow the publication’s sourcing and review process, with clear distinctions between documented facts, editorial recommendations and worked examples. The name gives this coverage a consistent byline; it does not identify an individual contributor. The accompanying portrait is an original AI-generated illustration. Readers can find the underlying sources in each article and send questions or corrections through the publication’s contact page.