Freshness means the information is maintained
A current date is useful when it reflects a significant change to the information. Replacing a year in a heading without checking the claims does not make an article reliable. Some questions need recent data; other explanations remain useful for longer.
Build a review register
Record the page, owner, evidence sources, last substantive revision, and what would trigger another review. A software guide may need a review when its interface changes. A case study may need a correction when attribution or client permission changes.
| Trigger | Substantive action | Date handling |
|---|---|---|
| Official guidance changes | Revise the affected recommendation | Update modified date |
| Original research added | Publish method and results | Preserve original publication date |
| Typo corrected | Correct the text | No artificial freshness campaign |
Review the claims first
Open the sources and check whether they still support the wording. Replace unsupported guarantees with a bounded explanation. Update screenshots or examples only when they represent actual observations.
Keep the implementation consistent
Visible modification dates, article JSON-LD, and sitemap lastmod should describe the same substantive revision. Store that date in the content record. A deployment timestamp is not a content update date.
Choose priorities
Start with commercially important pages and articles containing time-sensitive claims. Use search and conversion evidence to identify neglected information, but do not refresh a page solely to make it look newer than competitors. Track what changed so later observations can be interpreted responsibly.