How to Update Old Blog Posts Without Losing Rankings
To update an old blog post, keep its URL and check that it still answers the query it targets. Then fix what has gone stale: outdated facts, broken links, a weak opening and missing questions readers now ask. Change the date only when the content changed in a way a reader would notice. A post that answers its query better than it did before is the goal; a new date on old text isn’t.
Here’s how to choose which posts to update first, what to change, when to merge or delete instead, and how to check the result before you republish.
Why update old posts at all?
Because an old post starts with things a new one doesn’t have: a URL, links pointing at it and a history with search engines. What it may lack is an answer that matches what people search for today. Fixing that is a smaller job than starting over, though neither comes with a guarantee.
Posts go stale in predictable ways. A tool changes its interface and your screenshots no longer match. A statistic you quoted gets replaced by a newer study. The question behind the query shifts, so a post written for “what is X” now gets searched by people who want “how to choose X”. And links break as other sites move pages.
Leaving them has a cost you can see in your own reading habits. A post with a broken link and a dead screenshot gives a visitor a reason to doubt the rest of your site.
Which old posts should you update first?
Start with posts that already get some traffic or impressions but have dropped, then posts that target a query you care about and never ranked well. Posts nobody searches for and that don’t support a product page come last, or go on the delete list.
| Post type | Signal | What to do |
|---|---|---|
| Was ranking, has slipped | Clicks or average position falling | Update first: refresh facts, improve the opening and title |
| Ranks on page two | Impressions with few clicks | Rework the answer and the structure to fit the query |
| Never ranked, good query | Few impressions, the topic matters to you | Rewrite around one query, or merge into a stronger post |
| Two posts on one query | Both rank poorly and swap places | Merge them into one and redirect the other |
| Outdated, no traffic, off topic | Nothing in your search data | Delete it, or redirect it if anything links to it |
Your search console data is the source for these signals. Don’t guess from memory which posts “feel” old.
What should you change in an old post?
Read the post as a new visitor who typed the target query. Then work through it in this order:
- The opening. The first paragraph should answer the query directly. Older posts often open with background; move the answer up. Our blog post structure guide shows the full template.
- Facts and numbers. Check every statistic against its source. Replace or remove the ones you can’t verify.
- Steps and screenshots. Redo anything that describes an interface or a process that has changed.
- Links. Fix broken outbound links and add internal links to posts you’ve published since.
- Missing questions. Look at what people now ask around the topic and answer the ones your post skips, in a section or in the FAQ. The FAQ guide covers how to pick them.
- Title and description. Rewrite them if the query has shifted or the click rate is low. Keep the keyword at the start of the title.
Leave the parts that work. If a section is accurate and readers stay on it, rewriting it for the sake of change only adds risk.
What should you never change when updating a post?
The URL. Changing the slug turns an old page with history into a new page without it, and every link pointing at the old address breaks unless you add a redirect. Even with a redirect, you’ve added a step for nothing.
Two other habits do more harm than good:
- Changing the date without changing the content. Google’s guidance on helpful content asks directly whether you change dates to make pages seem fresh when the content hasn’t substantially changed.
- Rewriting the post around a different query. If the new query deserves a page, write a new post. Turning an old post into something else throws away what it ranked for.
When should you merge or delete instead?
Merge when two of your posts answer the same question. They compete with each other, and neither gets the full weight of your links. Pick the stronger URL, move the best parts of the weaker post into it and redirect the weaker URL to the stronger one with a 301. Our post on choosing target keywords covers how to avoid creating the overlap in the first place.
Delete when a post is off topic and gets no traffic. If other pages link to it, redirect it to the closest relevant post. If nothing links to it and nothing relates to it, let it return a 404 or 410.
A thin post isn’t always a delete. Sometimes it’s the start of a good answer. Ask whether you’d write a post on that query today. If yes, rewrite it. If no, remove it.
Should you use AI to update old posts?
It can speed up the mechanical parts: spotting outdated claims, suggesting missing questions, rewriting an opening to answer first. It’s risky for facts. A model asked to “refresh this post” may replace an old statistic with a new one it invented, and the result looks more current while being less true. Check every changed number against a source.
AI rewrites also tend to flatten the voice of the original. Run the revised sections through the same edit you’d give any AI draft; our six-pass editing method covers it. For whether AI-assisted updates hurt rankings, see is AI content bad for SEO.
How do you check an updated post before republishing?
Run it through the same checklist as a new post. The first paragraph answers the query, headings are questions, and there’s a table where a comparison helps. It ends with an FAQ, and every internal link works. The title has 60 characters or fewer with the keyword first, and the description runs 110 to 160 characters. Then read it once on a phone.
You don’t need a paid tool for this. If you update a few posts a month, the checklist above and your search console data are enough, and Copix would be the wrong purchase. A tool starts to pay off when you update in batches. On Copix Complete, the seo tool’s page action audits the live post for its query, including on-page findings and how ready it is to be cited by AI answers. After you revise, check_draft runs the house rules on the new draft, scores it for honesty and hype, and audits it on the page level. To find posts that compete with each other, queries checks candidates against the titles you’ve already published. See what the SEO engine checks, compare the plans, or read about getting cited by AI answers.
FAQ
How often should you update old blog posts?
When something in them changes, or when their search performance drops. A fixed schedule leads to cosmetic edits. A quarterly look at your search data to find slipping posts is a reasonable rhythm for most blogs.
Should you change the published date after an update?
Only after a substantial update a reader would notice, like corrected facts or a new section. Fixing a typo or a link doesn’t justify a new date.
Will updating a post hurt its rankings?
Keeping the URL and the query lowers the risk, but nobody can promise where rankings settle. They can move for a while after any change. Rewriting the post for a different query is the change most likely to lose what it ranked for.
Is it better to update an old post or write a new one?
Update when the post targets a query you still want and the URL has some history. Write a new post when the query is different enough that one page can’t answer both well.
What should I do with old posts that get no traffic?
Check whether the query matters to you. If it does, rewrite the post around it. If it doesn’t, remove it. When other pages link to it, redirect it to a related post instead.