How to Update an Old Recommendation

Recommendations age. The blender you loved gets a new model with a worse lid. The app you praised changes its free plan. The bookshop on your city walking route closes. Nothing you wrote was wrong when you wrote it, but a reader arriving today does not know that. They only see a confident pick that no longer holds.

Updating old posts is not the most glamorous part of writing recommendations, but it might be the most valuable. A blog full of picks that are still accurate is rare, and readers notice. Here is a calm, repeatable way to keep yours in shape.

Signs a pick has gone stale

Some changes announce themselves. Others creep in quietly. A few signals worth watching for:

• The thing itself changed. A new version, a new edition, a redesign, a different recipe, a new owner.
• The price moved a lot. A “great value” pick that doubled in price may not be great value any more.
• It is hard to find. Discontinued, out of stock everywhere, or only available second-hand.
• Your own view changed. Six more months of use revealed a flaw, or the thing turned out sturdier than you expected.
• Readers are telling you. Comments asking “is this still the one you’d pick?” are a gentle nudge. On PepPick every comment is reviewed before it appears, so you will see these questions as they come in.
• Your links lead somewhere unexpected. A product page that now redirects to a different item, or a page that no longer exists.

That last one matters more than it seems. The PepPick community guidelines say a link must lead where its text says it does. A link that silently changed is still your link, so check yours from time to time.

Decide: refresh, rewrite or retire

Not every stale post needs the same treatment. We find it helps to sort them into three buckets.

Refresh

The core recommendation still stands, but details have drifted. Update the price range, fix links, note the new model name and add a sentence about anything you have learned since. This is the most common case and usually takes minutes.

Rewrite

The verdict has changed. Maybe your top pick slipped to second place, or a new option is clearly better. Rewrite the parts that changed, keep what still holds and say plainly what is different and why. Readers who saw the old version deserve to understand the shift, not just discover it.

Retire

The thing is gone, or the whole topic no longer makes sense. You can leave the post up with a clear note at the top explaining that it is kept for reference, and point readers to a newer pick if you have one. Or, if it no longer helps anyone, ask for it to be removed: the help pages and contact page explain how to reach the team.

Make the change visible

Quiet edits make readers uneasy once they notice them. Visible ones build trust. When you change something meaningful, tell people:

• Add a short update note near the top: what changed and roughly when. “Update: the 2026 model has a new lid. I’ve used it for a month and it’s an improvement, details below.”
• Keep a brief changelog at the end for posts you update often, such as a ranked list. A few dated lines are enough.
• Do not erase your old opinion if it was reasonable at the time. “I used to recommend X. Here’s why I don’t any more” is honest and genuinely useful to someone who bought X on your advice.

Small typo fixes and tidy-ups do not need a note. Use your judgement: if a reader who saw the old version would make a different decision with the new one, say so.

Keep the address, keep the reader

When a pick needs a big rewrite, it is tempting to start a fresh post. Sometimes that is right, for example when the new version is truly a different piece. More often, updating the existing post is kinder to readers. Anyone who bookmarked it, saved it in a feed reader or shared it with a friend lands on the current answer instead of an outdated one.

If you do publish a new post, link to it from the old one. A single line at the top like “There’s a newer version of this list” saves readers from following stale advice. And link back the other way if the old post still has useful background.

Titles deserve a look too. A year in a title (“best of 2025”) dates a post the moment the calendar turns. If you keep a list current, a title without a year may serve readers better, with the update note doing the job of saying how fresh it is.

Build a simple review rhythm

The hardest part of updating is remembering to do it. A light routine beats good intentions:

1. Keep a short list of your posts most likely to go stale: ranked lists, buyer’s guides, anything with prices or version numbers.
2. Pick a regular slot, monthly or seasonal, and check a few posts each time rather than all of them at once.
3. Click every link in the posts you check. It is dull, but it catches problems fast.
4. Re-read your verdict and ask: would I still give this advice to a friend today?
5. Note the date you checked, even if nothing changed, so you know where to start next time.

Categories make this easier. If you sort your picks into a category like “Lists” or “Guides”, you have a ready-made shelf of posts to review first.

When you plan a new piece, it also helps to write it so it is easy to update later. Clear sections, a separate “How I tested” note and a dated verdict all make future edits quicker. We cover the testing note in Show your work: disclosing how you tested, and the list structure in What makes a top 10 list worth reading.

A recommendation is a promise that something is worth a reader’s time and money. Keeping that promise current is one of the nicest things you can do for the people who trust you.