Content Writing
Should You Update, Merge, or Delete an Old Blog Post?
A decision guide for old blog posts: when to update, when to merge two posts into one, when to delete, and how to handle redirects and 404s without losing what the post earned.
Update an old post when its topic still matters to your readers and it has a sound foundation. Merge it when another post on your site serves the same search intent and the two are splitting attention. Delete it only when the content is obsolete, wrong or irrelevant and nothing on your site is a close replacement; if there is one, redirect to it instead. Most old posts belong in the first group.
Four Questions That Decide It
Run each post through these in order. The first "no" usually gives you the answer.
- Does the topic still matter to people you want as customers? If no, the post is a candidate for removal or for being left alone as an archive item.
- Is there another post on your site serving the same intent? If yes, you are looking at a merge (or at differentiating one of the two).
- Is it accurate and reasonably well made? If no, update it, or rewrite it if the foundation is poor.
- Is it performing or doing a job? Clicks, enquiries, links, use by your sales team. If yes, keep it and maintain it. If no, but the first three answers were positive, keep it and strengthen its internal links before deciding anything else.
The Decision Table
| Situation | Action | What happens to the URL |
|---|---|---|
| Relevant topic, outdated or thin content | Update | Stays the same |
| Two or more posts answer the same question | Merge into the strongest one | Weaker URLs 301 to the survivor |
| Topic no longer relevant, but a closely related post exists | Retire and redirect | 301 to the related post |
| Obsolete or wrong, no equivalent, no meaningful links | Delete | Returns 404 or 410 |
| Accurate, useful, distinct, but little traffic | Keep | Stays; add internal links |
| Needed by customers, not useful in search (e.g. an old announcement) | Keep, optionally noindex | Stays |
When to Update
Update when the post targets something people still search for and the URL has any history worth keeping: impressions, a few links, a place in your internal linking. Updating keeps all of that and is almost always cheaper than starting again. The method is in how to refresh outdated blog content.
One test: if the update would change what the post is about, it is not an update. A 2021 post on "best free email tools" that would now recommend entirely different tools can still be updated, because the intent is the same. A post on "email marketing tips" that you want to turn into "how to choose an email platform" is a new post.
When to Merge
Merge when two or more posts would satisfy the same searcher. You can spot this in Search Console: filter by an important query, open the Pages tab, and see whether several of your URLs collect impressions for it, often with positions swapping back and forth. Common examples on older blogs:
- "10 blogging tips for small businesses" and "Blogging tips for beginners"
- "What is content marketing?" and "Content marketing explained"
- A 2022 and a 2024 version of the same annual roundup
How to Merge Without Losing What Either Post Earned
- Pick the survivor. Usually the URL with more clicks, referring links and age. If it has a dated URL (with a year in it), the other one may make a better survivor.
- Export both posts' data first: queries, clicks, links. You will want it to check the result.
- Combine the content. Move every section from the retired post that adds something, then edit the whole piece so it reads as one argument rather than two posts stitched together.
- Set a permanent redirect from the retired URL to the survivor. Google recommends a permanent server-side redirect (a 301 or 308) wherever possible.
- Update internal links that pointed at the retired URL so they go straight to the survivor.
- Keep the redirect. Google's guidance on URL changes is to keep redirects for as long as possible, generally at least one year. There is rarely any reason to remove them.
When to Delete
Delete when the post is obsolete, inaccurate, off-brand or irrelevant, nobody uses it, and nothing on your site is a genuine replacement. Examples: a news item about a product you no longer sell, an event recap from years ago with no links, a post written for a market you have left.
Let the URL return a 404 or 410. Google says it currently treats 410s the same as 404s, and that 404s do not harm a site's indexing or ranking. A 404 for a page that genuinely no longer exists is the correct signal.
Do not redirect every deleted post to the homepage or a general category page. Google's help on 404 errors says that redirecting users to another page, such as the homepage, instead of returning a 404 can be problematic, and that such pages are called soft 404s. A redirect should take the reader somewhere that answers the same need; if nowhere does, let it 404.
Before deleting, check for external links. A post with links from good sites is worth redirecting to its closest relative, even if the match is imperfect, or worth updating instead of deleting.
When Noindex Is the Better Option
Some posts are useful to people who already know you but pointless in search: an announcement of a new office, a client-only how-to, a page your support team links to. Deleting them breaks those uses; leaving them indexed adds thin pages to search. A noindex tag keeps the page on the site and out of results. Use it sparingly, and never on a post you are merging, which should redirect so its links pass to the survivor.
Why Not Just Prune Everything Weak?
Bulk pruning is tempting after an audit that shows dozens of posts with no traffic. Google's guidance on helpful content addresses it directly: it asks whether you are adding or removing a lot of content mainly because you think it will help your rankings, and answers that it will not. Low traffic is a reason to look at a post, not a verdict. Some of your most useful posts for closing sales may never rank.
A Worked Example
A blog has four posts on related topics. The decisions might look like this:
| Post | Finding | Decision |
|---|---|---|
| How to write a newsletter (2020) | Still gets impressions; examples and tools outdated | Update |
| Newsletter writing tips | Same intent as the post above; fewer clicks, no links | Merge into the first, 301 |
| Our 2019 newsletter redesign | Internal announcement, no traffic, no links | Delete (404), or keep with noindex if customers refer to it |
| Newsletter open rates explained | Different intent, accurate, modest traffic | Keep; link from the updated post |
After the Changes
- Remove deleted and redirected URLs from your XML sitemap, and fix internal links so none point at a redirect or a 404 (how to use internal links in blog content covers the wider linking pattern).
- Check Search Console's Pages report a few weeks later for unexpected 404s or soft 404s.
- Compare the survivor's clicks and queries after four to eight weeks against both posts' combined baseline.
If you have not yet decided which posts need which treatment, start with a blog content audit, which produces exactly this list. And if the resulting updates and merges are more than your team can take on, our blog management service is written by an in-house team, with no lock-in on standard plans.
Questions
Questions about this article
Still unsure about something? Talk to a specialist — no script, no sales pitch.
Not by itself. Google's guidance on helpful content says that removing a lot of older content mainly to help rankings will not work. Deleting can still be right for a specific post that is wrong, off-topic or duplicated, and merging overlapping posts can produce one stronger page. Remove posts for reasons about the content, not to shrink the site.
Either is fine. Google says it currently treats a 410 (Gone) the same as a 404 (Not found), and that 404s do not harm a site's indexing or ranking. Use whichever your platform makes easy. What matters more is not redirecting the URL to an unrelated page such as the homepage, which Google may treat as a soft 404.
Choose the URL with more clicks, links and history as the survivor. Move the useful sections from the other post into it, edit so it reads as one piece, then set a permanent 301 redirect from the retired URL to the survivor. Update internal links to point straight at the survivor and keep the redirect in place for at least a year.
Noindex suits posts readers still need but searchers do not, such as internal announcements or event pages you want to keep on the site. For a post that is wrong or useless to everyone, noindex just hides a problem; update it or remove it. Do not noindex a post you are merging; redirect it instead so links pass to the survivor.
Google's guidance for URL changes is to keep redirects for as long as possible, generally at least one year. In practice there is little cost to leaving them in place indefinitely, and removing them risks breaking links from other sites and old bookmarks. Review redirect lists only to remove chains, not to delete working redirects.