← Back to blog

When to Merge Two Old Blog Posts Into One Instead of Writing a New One

13 October 2026·5 min read
Quick answer: Merge two old blog posts when they're targeting overlapping search intent and cannibalising each other — both sitting around position 8–20 for the same query, neither one breaking through. Combine the useful content from both into the stronger-performing URL, then 301 redirect the weaker one across so you consolidate the backlinks and ranking signals instead of splitting them between two mediocre pages. ✨

Most businesses treat "more blog posts" as an unambiguous SEO win, so they keep publishing near-duplicate articles for years without ever auditing what's already there. 💖 The honest truth is that two thin, overlapping posts competing for the same search almost always underperform one genuinely good one — and the fix isn't writing a third post, it's merging the two you've already got.

What most businesses get wrong

The biggest mistake is never checking Search Console for cannibalisation in the first place, so two posts quietly compete against each other for months or years with nobody noticing. The second is, once spotted, deleting the weaker post outright instead of redirecting it — which throws away any backlinks or authority it had built up and can leave a dangling 404. The third is merging into a brand-new URL rather than keeping whichever existing page already has the most authority, which wastes the head start that page had.

The Merge-or-Keep Workflow
  1. Find the candidates: in Search Console, export Performance data filtered by Pages, then sort by query to spot two different URLs ranking for the same core terms, both underperforming.
  2. Pick the surviving URL: whichever page has more backlinks, more historic traffic, or stronger domain-relevant authority wins — not whichever post is newer or better written.
  3. Combine the content properly: don't just paste one post under the other. Read both, keep the genuinely useful sections from each, cut the repeated bits, and write it as one coherent, better article — not a stitched-together Frankenpost.
  4. 301 redirect the losing URL to the surviving page, pointing specifically to the relevant content, not the homepage.
  5. Update internal links across your own site that still point to the old URL, so you're not redirecting your own visitors unnecessarily.
  6. Resubmit the surviving URL in Search Console and expect a few weeks for Google to fully reprocess the change.
A local service business with a seasonal dip: publishes a seasonal explainer post, then three years later writes an almost identical one with a slightly different title — both now sit on page two for the same search, each quietly undermining the other.
A B2B firm with a long sales cycle: has two posts explaining essentially the same part of their process from different angles, written a year apart — merging them into one authoritative version outperforms either original within a few months.
A booking-based business: has an old FAQ-style post and a newer "how it works" post answering the same customer question in different words — a classic merge candidate once you line them up side by side.

The mechanics of doing this properly

A 301 redirect is a permanent redirect — it tells both browsers and search engines that the old URL has moved for good, and it passes the vast majority of that page's accumulated authority to the new destination. Depending on your platform, this is set either in your site's redirect settings (Shopify has a built-in URL redirect tool under Online Store) or via server configuration if you're self-hosted. The redirect needs to point to the specific surviving post, not a category page or the homepage — a mismatched redirect destination reads to Google as a soft 404 and won't pass the value you're hoping for.

Once the redirect is live, go through your own site's internal links, your sitemap, and any navigation menus or related-post modules still pointing at the old URL, and update them to point directly at the surviving page. Leaving internal links passing through a redirect isn't fatal, but it's an easy, free fix while you're already in there. Expect Google to take anywhere from a few days to a few weeks to fully recrawl and reconsolidate the signals — this isn't instant.

💡 Redirect to the specific page, never the homepage. A lazy blanket redirect to your homepage tells Google the old content simply disappeared rather than moved — you lose the SEO benefit you merged for in the first place.

Mistakes to avoid

  • Merging two posts without checking which URL actually has the stronger backlink profile first.
  • Deleting the old post with no redirect at all, leaving a 404 that visitors and crawlers both hit.
  • Forgetting to update your own internal links and navigation after the redirect goes live.
  • Merging topics that only loosely overlap just because the keywords look similar on the surface.
  • Walking away immediately after the merge instead of checking back in Search Console a month later to confirm it worked.

Frequently asked questions

How do I know two posts are actually cannibalising each other, rather than just covering a similar topic?

Check Search Console's Performance report, filter by page, and look for two different URLs ranking for the exact same core queries, both sitting outside the top few positions. If only one of them ranks well and the other barely gets impressions, it's less urgent — the overlap is only a real problem when both are stuck competing.

Will merging two posts guarantee a ranking improvement?

No — there's no guarantee. Consolidating signals onto one stronger page often helps, but content quality, overall site authority, and competition for that term still matter, and it can take time to show up. Treat it as removing self-inflicted competition, not a guaranteed jump to page one.

Should I always keep the older URL when merging?

Not automatically — keep whichever URL has more accumulated authority (backlinks, historic traffic), which is sometimes the newer post if it's picked up more links. Check the data rather than assuming age wins.

What if the two posts genuinely serve different audiences, even though the keywords overlap?

Then don't merge them — differentiate them instead, with clearer titles and internal linking that signals to both readers and Google which post answers which specific question. Merging should solve genuine duplication, not force together two posts that are actually doing different jobs.


Keep reading 🤍

Share
Written by
Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦