Redirecting a Merged Post Without Losing Rankings

Redirecting a merged blog post without losing rankings means a single 301 redirect from the old URL straight to the surviving, topically-matched URL, updated internal links pointing to the same destination, and the merged content itself genuinely covering what both original posts covered. Get any one of those three wrong — a wrong redirect type, a mismatched target, or content that dropped what made the old post rank — and the merge loses traffic instead of consolidating it.

Merging posts is usually the right call when two articles compete for the same keyword or cover heavily overlapping ground. The redirect is where that good decision either pays off or gets undone. This is the sequence that keeps it from going wrong.

What redirect type actually preserves rankings after a merge?

A 301 redirect, every time, no exceptions for this use case. A 301 status code tells search engines the move is permanent, which is what triggers Google to consolidate the old URL’s ranking signals — links, relevance, historical performance — onto the new one. A 302, which signals a temporary redirect, doesn’t trigger the same consolidation; Google tends to keep evaluating the old URL as the “real” one and hold back full signal transfer, which is the opposite of what a permanent content merge needs.

Step 1: How do you decide which URL survives the merge?

Before touching the redirect, settle which of the two (or more) posts becomes the surviving URL. The general rule: the URL with more backlinks, more historical organic traffic, and a stronger current ranking wins, even if the other post has “better” or newer content — you can move better content onto the stronger URL, but you can’t easily move accumulated backlinks and ranking history onto a weaker one. Check both in Search Console (clicks and impressions over the last 12-16 months) and in a backlink tool before deciding, rather than guessing from memory.

Step 2: How do you merge the content itself?

The redirect only works if the destination page genuinely satisfies what both original URLs were ranking for. Read through both posts and note every subtopic, question, and keyword variant each one covered, then confirm the merged page addresses all of them — not just the topics from the surviving post. A merge that keeps 80% of one post and drops the unique 20% from the other typically loses the rankings tied to that missing 20%, because the redirect target no longer matches the intent that content used to satisfy.

Step 3: How do you set up the actual redirect?

Point the retired URL directly at the final destination URL — not at an intermediate page, and not into a redirect chain. A chain (URL A → URL B → URL C) adds latency, and while Google generally follows a handful of hops, each additional hop is a chance for a signal to degrade or for the chain to break entirely during a future site change. Implement it at the server or CMS redirect-manager level, confirm it with a direct HTTP request (checking for a single 301 response, not a 302 or a chain), and never rely on a client-side JavaScript redirect for this.

Step 4: How do you update everything else that still points to the old URL?

A redirect fixes what happens when someone lands on the old URL, but it doesn’t fix internal links across the site still pointing there — every hop through a redirect, even a correctly configured one, adds a small amount of friction and dilutes signal slightly compared to a direct link. Crawl the site, find every internal link to the retired URL, and update them to point straight at the surviving URL. Update the XML sitemap too; leaving the old URL listed there sends Google a mixed signal about which URL is actually canonical.

Five steps that keep rankings intact through a merge

• Choose the stronger URL to survive — more backlinks and traffic history, not just newer content.
• Cover both posts’ subtopics — the merged page has to satisfy both original search intents.
• Use a single, direct 301 — no chains, no 302s, no JavaScript redirects.
• Update internal links and the sitemap — point everything straight at the final URL.
• Keep the redirect live for at least a year — permanently is safer if there’s no pressing reason to remove it.

What common mistakes cause a merge to lose rankings?

• Merging into the newer post instead of the stronger one. Picking the URL with a nicer publish date over the one with the backlink and traffic history throws away the exact signals the merge was meant to consolidate.
• Redirecting to a page that doesn’t actually cover the old content. If the merged page reads as a different topic to a human, Google’s algorithms tend to reach the same conclusion and treat the redirect as unreliable.
• Leaving old internal links unrouted through the new redirect. Functional, but it compounds unnecessary hops across the site and makes the eventual redirect map harder to audit.
• Removing the redirect too soon. Deleting it after a few months, or reusing the old URL for new content, severs any external links still pointing at it and can strand residual referral and search traffic.

How do you verify the merge actually worked?

Check Search Console’s Performance report for both URLs four to eight weeks after the redirect goes live. The surviving URL’s clicks and impressions should show the old URL’s traffic folding into it, not just holding steady at its pre-merge level — if the surviving URL’s numbers don’t move but the old URL’s traffic simply vanishes, that’s the signature of a broken or mismatched redirect, not a successful consolidation, and it’s worth re-checking the redirect status and content overlap immediately rather than waiting longer.

Frequently asked questions

Should a merged post redirect with a 301 or a 302?

Always a 301. A 301 tells search engines the move is permanent and consolidates ranking signals onto the surviving URL; a 302 signals a temporary move, so Google keeps the old URL indexed and doesn’t pass signals the same way, which defeats the purpose of a merge.

How much ranking value does a 301 redirect actually pass?

Most SEO practitioners estimate roughly 90-99% of link equity passes through a 301, based on years of observed ranking behavior, though Google has never published an exact figure. Some loss is normal and expected; a merge that loses most of its combined traffic points to a mismatch problem, not the redirect mechanism itself.

What happens if the merged content isn’t topically close to the old post?

Google evaluates whether a redirect target is a reasonable match for the redirected URL’s content. A redirect to an unrelated or only tangentially related page can be treated as a soft 404, meaning the old URL’s signals aren’t fully consolidated onto the new one, and rankings for that content simply disappear instead of transferring.

How long should the redirect stay live after a merge?

Indefinitely, or at an absolute minimum one year. Removing a redirect early — reusing the old URL for something else, or letting it 404 — cuts off any residual traffic and signal transfer still in progress, and re-breaks links from external sites that haven’t been updated.

Sources

• 301 Redirects and Google Search — Google Search Central
• On-Page SEO: The Complete Working Checklist
• Deciding Which URL Survives a Merge
• Keyword Cannibalisation: Diagnosis and Repair
• Content Freshness: When Updating Helps and When It Doesn’t