You ship fast, so your product changes. Features get renamed in a rebrand, folded into a bigger workflow, split into two, or quietly retired when the data says nobody used them. None of that is a problem until you reread your testimonials page and notice that your most persuasive quote — the one a prospect screenshots and sends to their boss — praises "the Pulse dashboard," and Pulse hasn't existed for eight months. It's now called Insights, and half of what it did got absorbed into the reporting module.
The instinct is to either leave it alone (it still sounds great) or quietly delete the feature name from the quote. Both are wrong in different ways. Leaving a dead feature name in a live testimonial sends prospects looking for something they can't find, which reads as a bait-and-switch the moment they sign up. Editing the customer's words to match your current naming is a quieter problem, but a real one: the second you alter what a customer actually said, the quote stops being a testimonial and becomes copy you wrote and attributed to someone else. The fix lives between those two extremes, and which path you take depends on what actually changed.
First, classify what changed
A testimonial that references an outdated feature is not one problem — it is one of three, and they have different fixes.
Renamed, same thing. The feature does exactly what it did; only the label changed. "Pulse" became "Insights," but the dashboard the customer loved is still there, doing the same job. This is the easiest case and the one teams most often overreact to.
Renamed and changed. The feature was renamed and reworked — split, merged, or significantly altered. The customer praised a workflow that no longer maps cleanly to anything in the current product. The quote is partly true and partly stale.
Removed entirely. The feature is gone. The customer is praising something a new signup will never experience. The quote is now a promise you cannot keep.
You cannot pick a fix until you have placed the testimonial in one of these three buckets, because the credibility risk rises sharply from the first to the third.
If it was only renamed: re-anchor, don't rewrite
When the feature is unchanged and only the name moved, the customer's praise is still completely true — they just used the old word. Do not edit their quote. Editing a customer's words, even to "correct" a product name, crosses a line you do not want to cross, because once you are comfortable changing one word you have lost the bright-line rule that protects every testimonial you publish: the words are exactly what the customer said.
Instead, re-anchor with context the customer did not have to write. Add a small, clearly-yours editorial note next to the quote:
"The Pulse dashboard saved my team six hours a week." — Pulse is now called Insights.
The bracketed or italicized note is in your voice, not theirs. It keeps the testimonial verbatim while quietly bridging the prospect from the old name to the current one. This is the same principle that governs handling a testimonial whose language no longer lands — when a quote uses jargon prospects won't understand, you clarify around the quote rather than inside it. The customer's words stay sacred; your context does the translating.
If the rename is recent and well-known to your audience, you may not even need the note — a prospect who reads "Pulse" and sees "Insights" in your nav will usually connect them. The note matters most in the window right after a rename, when the old name still appears in screenshots, reviews, and the customer's memory but no longer in your UI.
If it was renamed and changed: re-verify before you keep it
When the feature was reworked, the quote is in a gray zone, and the honest move is to go back to the source rather than guess. Reach out to the customer, tell them the feature evolved, and ask one question: does this still reflect your experience?
Three things can happen. They say yes, the new version is even better, and you now have a refreshed quote about the current product — strictly an upgrade. They say the new version doesn't work the way it used to and they preferred the old one, in which case you have learned something important about your product and should not be publishing a quote that implies otherwise. Or they don't respond, in which case you fall back to the rule for removed features below.
Re-verification is the same discipline that keeps attribution honest as customers move on. The operational habit of periodically checking testimonials against current reality — covered in our testimonial attribution decay piece — applies to features as much as to job titles. A testimonial is not a fixed asset; it is a claim about a relationship between a real person and a current product, and both halves can drift.
If it was removed entirely: retire the quote
When the feature is gone, the path is unambiguous: the testimonial comes down, no matter how good it is. A quote that praises a capability a new customer will never get is not a testimonial — it is a false promise with a real person's name attached, and the cost of a prospect discovering the gap after signing up is far higher than the cost of one fewer quote on the page.
Before you delete it, do two things. First, check whether the outcome the customer described still holds through a different path. If they praised a removed feature but the result — "we cut onboarding time in half" — is still achievable with the current product, ask the customer for a refreshed quote framed around the outcome rather than the retired mechanism. Outcomes survive product changes that features do not. Second, if you cannot refresh it, retire it cleanly and make sure your collection pipeline is replacing it. A testimonials page thins out over time if you only remove and never replenish; our guide on how to collect testimonials from customers covers building the steady intake that keeps the page current as the product evolves.
Build the maintenance habit, not just the one-time fix
The deeper issue is that this will keep happening. Every rename and every retirement creates new stale references across every testimonial, case study, and landing page you have published. The fix is a cadence, not a heroic cleanup: whenever you rename or remove a feature, add "scan published proof for references" to the launch checklist, the same way you would update the docs and the marketing site. The contextual difference between a testimonial and a longer-form proof asset matters here too — a case study that walks through a now-removed feature step by step is far more misleading than a one-line quote, and should be reviewed first.
A testimonial that mentions a stale feature is not an embarrassment to hide — it is a signal that your proof and your product have drifted apart, and the teams that treat that drift as routine maintenance keep a page that always describes the product a prospect will actually get.
The one-sentence version
When a testimonial praises a feature you've renamed, re-anchor it with an editorial note instead of editing the customer's words; when the feature was reworked, re-verify with the customer before keeping it; and when the feature is gone, retire the quote — refreshing it around the surviving outcome if you can, and replacing it if you can't.