Do not refresh a page because it looks old. Refresh it when a reader could make a worse decision because a meaningful fact, interface, offer, source, or search intent has changed.
Keep a change ledger
For each important page, record four things beside the URL: the claim or instruction that could go stale; the evidence that currently supports it; the event that should trigger a review; and the owner who can check it. A SaaS settings guide might be reviewed after a platform interface change. A seasonal promotion page needs a calendar date. A measurement method needs review when event definitions or consent behavior changes.
Then choose one of three actions:
- Verify and retain: Evidence and task remain current; no rewrite is needed.
- Update with a visible change: A key detail changed. Correct that detail, preserve accurate sections, and update the modified date only after substantive edits.
- Consolidate or redirect: Two pages now answer the same task, or the original task no longer exists. Check links and search impact before changing established URLs.
Example: an analytics setup guide
If the interface labels changed but the event definition is still accurate, update the screenshots or navigation labels and add a note about the tested environment. If the tracked event now fires twice, that is not a cosmetic refresh: replace the diagnosis, include a test path, and show how to confirm one event per action. If the guide relies on an old source, find a current official source before changing the claim. Do not silently rewrite history or imply you tested a setup you did not test.
Make refresh decisions from evidence
In Search Console, compare queries, impressions, clicks, and landing URLs over equivalent periods. In analytics, check whether readers reach the relevant next step; use support questions to find instructions that remain confusing. A traffic decline alone does not prove the article is outdated, and a date change alone does not make it fresh.
Keep a concise revision note: what changed, why, what source or test supports it, and who reviewed it. This creates a trail the next editor can trust.
Google recommends accurate, original information that satisfies the reader’s task; cosmetic changes to imitate freshness do not add that value. Review its people-first content guidance.
Separate decay from a deliberate change
Compare the page against its previous version and classify each issue: factual expiry, intent drift, missing evidence, confusing structure, or technical loss. Select one primary correction and keep a dated record of what changed and why. Update claims only from a source that can be checked; if the underlying service changed, correct the page before polishing keywords. After release, annotate the date in analytics and avoid judging the change from a few days of traffic. A refresh is successful when it better answers the task without erasing useful sections or creating unsupported claims.
Optional AI-assisted work brief — Evidence-led refresh plan
Compare this page and its dated evidence with its prior version. Classify each issue as factual expiry, intent change, missing proof, structure, or technical loss. Propose the smallest useful correction, list claims needing source checks, and define a review window. Preserve accurate useful material and do not add unsupported claims.
Refresh decision: update, consolidate, or leave alone
Update
A fact expired or the page no longer answers the task; verify the source and replace the affected section.
Consolidate
Two pages solve the same job; choose the stronger page and preserve useful details.
Leave
The page remains accurate, useful, and technically available; a quiet period alone is not a reason to rewrite it.
Log
Save what changed, why, when, and what comparison remains valid.
Worked scenario — An update that preserves useful evidence
A page contains a working event checklist but names a retired analytics interface. Keep the checklist if still valid, replace the obsolete navigation steps using current official documentation, date the substantial change, and test the revised route. Do not rewrite the entire article just to refresh its timestamp.
AI disclosure: AI tools assisted with drafting. The setup scenario is illustrative, not a verified client result.