You fixed the page. You did not fix the copies

A seller changes one sentence. The old blurb said the strap was leather; a supplier change made it a leather-look coated canvas, so the sentence had to go. It took four minutes: open the product, fix the description, save, reload the page to check. The page now says the right thing, and it will keep saying the right thing. That part genuinely is finished.

What is not finished is everything else that was holding a copy of that sentence. On a working shop there are usually five or six, and the number surprises people, because the product page is the only one of them a seller ever looks at on purpose.

Where the duplicates actually are

• Your shopping feed. Google Merchant Center, Meta's catalogue, Pinterest — each takes a product title and description and keeps its own copy, refreshed on a schedule you probably set once. Between refreshes it serves the old text, and if a field was ever overridden in the feed settings it serves the old text permanently.
• The SEO fields. Most platforms let the meta title and description be set separately from the body copy, and most sellers filled them in once at launch. Editing the description does not touch them. This is the copy that shows up in search results.
• The social preview. The Open Graph title and description attached to the product URL, which is what renders when anyone pastes the link into WhatsApp, Instagram or Slack. Often a third independent field, and often cached by the platform for weeks after you change it.
• Marketplace listings. The same product on Etsy, Amazon or eBay, written separately and maintained separately, usually by whoever set that channel up.
• Email and automation templates. Abandoned-cart, back-in-stock and post-purchase emails that quote the product blurb inline, written months ago and never opened since.
• Your own category and landing pages, where the product's one-line summary was typed by hand into a grid.

Six copies, one of which you proofread. The other five are not wrong because anybody was careless — they are wrong because an edit to a product record has no mechanism to reach them. They were populated by a copy-paste or a sync that ran once, and a copy-paste has no memory of where it sent things.

Why this is a different problem from the other two

It is worth separating this from two failures it gets confused with, because the fix for each is different. One is the claim that was always a setting: a dispatch time or a pack size that is typed into your copy and held as a number somewhere else, so it goes stale the moment the setting moves. The other is the promise with no figure in it, which nothing can be compared against at all.

This one is neither. The claim has a correct version, you know what it is, and you have already written it down. The failure is purely in distribution: the true sentence exists in one place and the false one exists in five, and the five are the ones doing the talking to anybody who did not arrive on the product page. A shopper who sees your product in a Shopping ad, or gets your back-in-stock email, or has the link sent to them by a friend, is reading a copy you have not looked at this year.

The cheapest way to find yours

Do not try to build a system for this. Take one product you changed recently and chase that single sentence through every channel you sell on, writing down each place you find it. It takes about twenty minutes and it produces the only thing you actually need, which is the list — because the list is the same for every product on your shop. Once you know your copy lives in six places, a copy change becomes a six-item job instead of a one-item job, and that is the whole fix.

Two shortcuts while you do it. Paste a product URL into a chat app and look at the preview that comes up, which tells you what the social fields say without your having to find them in the admin. And open the product in whichever channel has the fewest edits — usually a marketplace — because that is where the oldest surviving version of your copy normally is.

The version of this we had to fix

This is not a seller-only problem and it is worth saying that plainly. Every public claim on this site is checked against the code that implements it before anything ships, which is how a price or a limit here cannot quietly go stale. That check ran over our pages. It did not run over the feed this blog publishes, or the small web manifest a browser reads when someone installs the site — both of which restate the same claims in the same words, and neither of which anybody had thought of as copy. The claims in them happened to be true. Nothing was holding them true, and the reason is the one above: they were populated once, from the pages, and nothing connected an edit to its duplicates.

The general shape, for anybody auditing their own shop: the question is not whether a claim is correct. It is how many places that claim is stored, and which of them you have ever read.