ChecklistUpdated 2026-09-21
What to publish when a product changes
Use it the week a product changes — a new revision, a changed specification, a renamed variant, a discontinuation. Models keep repeating the version they found first; the list makes the change explicit where they look, and keeps the old version on record instead of erasing it.
On the product page
- The new value is stated in the text, with the date it applies from.
- The old value is not silently removed: say what changed ("45 litres from 2026; the 2025 version was 48 litres").
- Identifiers are updated: a new revision with a new GTIN gets the new GTIN, and the old one is not reused.
- The structured data changes in the same release as the visible text.
Around the page
- Pages you control that repeat the old value — comparisons, guides, the blog — are updated or marked as describing the old version.
- Retailers and marketplaces that list the product get the new data feed or specification sheet.
- If the old product is discontinued, its page stays online and says so, pointing to the successor — a 404 leaves only third-party pages describing it.
Afterwards
- Ask the same buyer questions in several models two and four weeks later, and record which version each answer describes, with the exact model name and date.
- Keep that record next to the date of the change: it is the only way to tell later whether the change reached the answers.
Why each item is on the list
Related
← All checklists