Field notesFreshnessContent trust
Undated content cannot be judged, so it gets skipped
Freshness is not about publishing constantly. It is about making currency assessable — and most sites make that impossible without realising it.
AI Detective5 min read
Freshness is widely misread as a demand to publish constantly. It is not. It is about whether a reader can tell if what you wrote is still true — and if they cannot, cautious readers discount it.
The asymmetry that matters
Consider two pages making the same claim about pricing in your industry. One is dated eight months ago. One carries no date.
The dated page can be assessed: eight months is recent enough for some claims and too old for others, and a reader can decide. The undated page cannot be assessed at all. It might be from last week or from 2017. Faced with a choice, drawing on the assessable one is the safer decision.
What to show
- Published date, visible on the page, not only in markup.
- Last substantively updated date, where it differs, labelled as such.
- Both in structured data as datePublished and dateModified, so the values are unambiguous rather than parsed out of prose.
- For pages that are deliberately evergreen, a brief note on what is periodically reviewed and when.
Showing published and updated dates separately matters. A single date labelled ambiguously invites the suspicion that it is being refreshed cosmetically.
The automatic-update trap
Some systems set the modified date on every deployment, so a typo fix or an unrelated template change marks every page as freshly updated.
This is worse than showing nothing. It asserts currency that was never established, and once the field is understood to be automatic it stops carrying information entirely. Update the date when the content changes in substance, not when the file changes.
Not everything needs a date
Freshness matters in proportion to how time-sensitive the claim is. Prices, statistics, regulations, integrations, product capabilities, and comparisons decay. A definition of a stable concept largely does not.
The practical approach is to identify which of your pages make claims that expire, date those clearly, and put them on a review cycle. That is a much smaller set than 'all content', which is why treating freshness as a publishing-volume problem produces so much unnecessary work.
A review cycle that is actually sustainable
Sorting pages by how fast their claims decay makes the work tractable. A rough grouping most businesses can apply in an afternoon:
| Content | Decays | Review |
|---|---|---|
| Pricing, plan limits, availability | Immediately on change | At the moment it changes, not on a schedule |
| Integrations, capabilities, comparisons | Fast — competitors ship | Quarterly |
| Statistics, market figures, benchmarks | Annually, and visibly | Yearly, with the source year stated |
| Regulations and compliance guidance | On regulatory change | Yearly, plus on known changes |
| Definitions, concepts, how-to fundamentals | Slowly | Every two years, or when superseded |
Most sites find the top two rows contain a small number of pages and account for nearly all of their genuine staleness risk. That is a manageable list, and it is a far cry from reviewing everything.
Date the claim, not just the page
There is a second kind of date worth showing, and it is more useful than the page date: the date attached to the claim itself.
'The average is 34%' invites the question of when. 'The average was 34% in 2025, according to the linked survey' answers it, and stays accurate even when the page is old. Claims dated in the sentence survive their page going stale, which page-level dates cannot do.
Maintenance as the actual strategy
The highest-return freshness work is usually revisiting existing pages that already earn attention: correcting what has changed, removing what no longer applies, and updating the date honestly.
This is less satisfying than publishing something new, and it reliably outperforms it. An accurate, maintained, well-referenced page is a better asset than another page competing with it.