Most teams never decide whether to date their testimonials — they just inherit whatever their tool does by default. Some review widgets stamp every quote with a date; some case-study pages omit it entirely. Neither default is right for every situation, and the choice matters more than it looks. A date is a credibility signal and an expiration signal at the same time. Get it right and a testimonial reads as real and current. Get it wrong and a strong quote quietly announces that your best proof is three years old.
Here is how to decide, page by page.
What a date actually signals
A visitor scanning testimonials is running a fast, mostly unconscious check: is this real, and is it still true? A date speaks to both questions at once, and the two answers pull in opposite directions.
- Real: An attributed date is hard to fake convincingly and easy to verify against a review platform. It reads as "this happened" rather than "the marketing team wrote this."
- Still true: A recent date says the praise reflects the current product. An old date raises the question the visitor was not asking until they saw it: has anything changed since then — and not for the better?
So the decision is never "dates are good" or "dates are bad." It is: does the freshness signal help or hurt this specific piece of proof, on this specific page?
When to show the date
Show the date when recency is itself part of the persuasion.
- Review feeds and rating widgets. On a live feed of reviews, dates are expected. Removing them looks like you are hiding something, and a steady stream of recent dates is one of the strongest trust signals you have — it proves customers are still choosing you now.
- Testimonials about a new feature or recent change. If a quote praises something you shipped this quarter, the date reinforces that the feedback is about the current product, not an old version.
- High-volume, fast-moving categories. In markets where buyers assume tools go stale quickly, a recent date does real work. It answers "is this still a going concern?" before the visitor has to wonder.
- Anything a skeptical buyer might try to verify. In B2B, a procurement-minded evaluator may cross-check a testimonial against LinkedIn or a review site. A date that matches the public record removes friction; a missing date invites suspicion.
The rule of thumb: if the date is recent, show it — you are leaving a credibility signal on the table by hiding it.
When to leave the date off
Omit the date when the value of the testimonial is timeless but the date would make it look stale.
- Evergreen outcome quotes. "It cut our onboarding from two weeks to two days" is true whenever a visitor reads it. Stamping it with a date from two years ago adds nothing and subtracts freshness.
- Foundational case studies you cannot easily refresh. A flagship customer story is expensive to produce and rarely re-recorded. If the outcome still holds, an undated version keeps working long after a dated one would look abandoned.
- Pages where every other element is undated. Consistency matters. A single dated quote in a row of undated ones draws the eye to the date and makes the reader wonder why only that one is stamped.
Leaving the date off is not deception — the quote is real either way. It is a judgment that the freshness dimension is not relevant here and the staleness risk is not worth taking.
The stale-testimonial trap
The worst outcome is the hybrid mistake: dating your proof and then never revisiting it. A wall of testimonials where the newest date is eighteen months old is worse than no dates at all. It does not just fail to prove recency — it actively signals decline. A visitor reads it as "they were doing great back then," which plants exactly the doubt you were trying to remove.
If you commit to showing dates, you commit to a maintenance rhythm:
- Audit dated proof on a schedule. Every quarter, scan your key pages for the oldest visible date. If your freshest dated testimonial is aging, that is a signal to collect new ones, not to quietly strip the dates.
- Lead with your most recent proof. Order dated testimonials newest-first on feeds so the first thing a visitor sees is current.
- Retire, do not just hide. When a dated testimonial mentions an old price, a renamed feature, or a version you no longer ship, retire it rather than removing only the date. A date is not the problem there — accuracy is. See our guide on when to retire a testimonial from your website.
A middle path: relative and coarse dating
You do not have to choose between an exact timestamp and nothing. Two softer options preserve most of the credibility signal while reducing the staleness risk:
- Year only. "2026" reads as current without pinning the quote to a specific month that will feel old by December. It is a reasonable default for case studies and outcome quotes you refresh annually.
- Relative phrasing on live feeds. "Reviewed 3 weeks ago" carries strong recency without a hard date, and it keeps looking fresh as long as the feed is genuinely active. Only use this where it is honest — relative dates on a feed that has not updated in a year are worse than an exact old date.
Avoid the temptation to remove dates only from your oldest testimonials while keeping them on recent ones. Attentive visitors notice the pattern, and it reads as concealment. Whatever rule you pick, apply it consistently within a page.
The decision in one line
Ask a single question for each testimonial: would a recent date make this more persuasive, or would an old date make it less? If recent helps, show it and keep it fresh. If old hurts and the value is timeless, leave it off. The date is a tool for signaling that your proof is current — use it where that message is true, and do the work to keep it true.
For more on keeping proof accurate as your product and customers change, see how to keep a testimonial accurate when the customer's numbers change later and how to refresh an old testimonial without making it sound fake.