Revision dates remind you who changed what when
I spent twenty minutes yesterday updating a pricing page that still mentioned a service we discontinued in 2022. Nobody caught it because the page looked fine — clean layout, decent copy, no obvious errors. The content had just quietly aged out.
A visible revision date would have flagged it months ago.
What a revision date actually does
It's not about compliance or looking official. A "Last updated" timestamp near the top of a page tells readers — and your team — when someone last reviewed the content. That single piece of metadata creates accountability that "Published on" dates don't provide.
Publish dates mark creation. Revision dates mark maintenance. The difference matters when you're managing pages that need to stay current.
Set it up in your CMS
Most systems track this automatically in the backend. You just need to surface it on the page. Add a field to your template that pulls the last-modified timestamp. Format it clearly: "Last updated March 15, 2024" works better than raw ISO dates.
If your CMS doesn't auto-update this field when you save changes, add it to your editing checklist — update the date manually when you make substantive changes. Skip bumping it for typo fixes.
When to display it
Not every page needs a visible revision date. Blog posts can rely on publish dates. But pages with facts that expire — pricing, features, hours, contact details, policies — benefit from showing when they were last confirmed accurate.
Service pages, resource guides, documentation, and anything referencing time-sensitive information should display it by default.
How teams actually use it
Revision dates become a scanning tool. When you're auditing content, sort by last-updated and you immediately see what's been neglected. Pages untouched for eighteen months probably need a review, even if they don't look broken.
It also settles the "who changed this?" question faster. Pair revision dates with version control and you can trace changes without digging through email threads.
What counts as a revision
Don't overthink it. If you're changing meaning, updating facts, or rewriting sections, update the date. If you're fixing a typo or adjusting spacing, leave it alone. The goal is to signal "we checked this recently," not to log every keystroke.
Some teams set a review interval — every six months, they touch the date even if nothing changed, just to confirm accuracy. That works for high-stakes pages where staleness carries risk.
The honesty problem
Showing revision dates only helps if you actually revise things. An accurate "Last updated 2019" is more honest than a fake current date, but neither is great. If seeing old dates embarrasses you, that's useful information — it means you need a content maintenance schedule, not better date formatting.
Revision dates work when they reflect reality. Add the field, keep it current, and let it remind you which pages you're actually maintaining.