Refresh, combine or leave an article alone?

Start with the problem, not the date

An old publication date does not automatically make a guide unhelpful. Review the page's purpose, factual accuracy and fit with the current site before deciding to rewrite it. A refresh should solve an identifiable problem: outdated instructions, unanswered questions, broken references or overlapping content. Changing a date without improving the article creates the appearance of maintenance without its substance. Keep a short record of what changed and why so the next review starts with context.

Collect a small evidence pack

Read the article from beginning to end before opening performance charts. Follow its links and try any steps that still apply. Note stale interface instructions, unexplained assumptions and examples that no longer fit the audience. Then review the information available in your search and analytics tools, comparing sensible periods rather than reacting to one quiet day.

Separate measurement changes from content problems. A tracking update, a seasonal demand shift or a site migration can alter reported activity without making the article worse. Write down these possibilities instead of assuming every decline requires a longer introduction or more keywords.

Choose the smallest useful intervention

If one instruction is wrong, correct it and inspect nearby references. If the article's structure no longer matches its purpose, plan a broader revision. If the page still answers the question accurately and clearly, leaving it alone can be a reasonable choice. Maintenance effort is limited; use it where a reader will benefit.

A refresh is not an excuse to add unrelated sections. Preserve the main task and improve the route to completing it. If a new topic deserves detailed treatment, create a separate resource only when it serves a distinct need and connect the two with descriptive links.

Combine only when the purposes overlap

Two articles with similar wording may serve different readers. Compare their actual promises before merging them. When both answer essentially the same question, choose the destination that makes the most sense within the site and preserve the useful material from each. A developer should plan any necessary redirects and test them after the change.

Do not redirect an unrelated retired article to the homepage merely to avoid a not-found response. Where no relevant replacement exists, an honest removal can be clearer. Review internal links so readers are not sent through unnecessary redirects or toward deleted material.

Update evidence, examples and accessibility

Check source pages for substantive changes rather than only confirming that their URLs load. Replace obsolete screenshots if the interface has changed and a screenshot is still necessary. Verify that tables work on small screens and that alternative text describes the visual's purpose. A refresh is an opportunity to remove friction, not just update prose.

Keep examples clearly labeled. If an old hypothetical number is no longer useful, change the example and its explanation together. Do not add an unsupported success story to make the revised article feel more current or experienced.

Publish and evaluate without rushing

Review the revised title, description, main heading and internal links as one package. Preserve the URL when the purpose is unchanged unless there is a strong reason to move it. Test the page after publishing and note the date of the actual substantive update.

Give changes time to be discovered and read. Look for a pattern across appropriate periods, then consider whether readers are completing the intended next step. A single ranking movement does not establish cause. Keep qualitative observations alongside numbers so the next decision is based on more than a chart.

A practical exercise

Choose one article and write a short maintenance note with three headings: still useful, needs verification and proposed change. Require a reader-facing reason for every proposed edit. Then estimate the risk of changing the URL or removing a section. If you cannot identify a material improvement, defer the rewrite and review a page with a clearer problem. This exercise prevents a content calendar from turning maintenance into routine cosmetic changes that consume time without helping readers.

Refresh questions

Should every page be updated monthly? No. Use the volatility of the topic and evidence of a problem to set priorities.

Does adding words make a refresh better? Only when the added material helps fulfill the page's purpose.

What can I do in one focused session? Correct broken facts, test links and improve one confusing section, then record those changes honestly.