Home >Blog

How to Set Up Redirect Chains for a Website Migration

Published 2026/09/30Updated 2026/09/30

A site migration without a redirect plan loses rankings, link equity, and users who hit dead ends. The fix is boring and mechanical: every old URL gets one single-hop 301 to its new home. Here's how to set it up without leaving chains behind.

Why chains happen

Redirect chains are almost always the result of sequential migrations. URL moves to a new path, then a year later the site restructures again, and the redirect gets stacked on top of the old one instead of being updated. Each hop is cheap alone; together they slow pages and dilute signals.

The process

Step 1. Inventory every old URL

Export your old site's URL list. Include the URLs that had links pointing at them — those are the ones that matter.

Step 2. Map each URL to its new home

Build a 1:1 mapping table: old URL → new URL. Every old URL gets exactly one destination.

Step 3. Flatten existing chains

If old URL A already redirects to B and B redirects to C, write A → C directly. Remove the middle hop.

Step 4. Implement single-hop 301s

Add one redirect rule per old URL, pointing straight at the final destination. No intermediate stops.

Step 5. Verify every rule

Run each old URL through a redirect checker. Expected result: exactly one hop, HTTP 301, ending on the new URL.

A chain of browser windows connected by arrows with a single-hop path highlighted

What to check after the migration

Re-submit the sitemap in Search Console for both old and new site properties.
Monitor 404s for a month — anything that 404s is a mapping you missed.
Recheck the chains weekly until the crawlers settle; then spot-check monthly.

Run your old URLs through the Redirect Chain Checker before and after the change — it reports every hop so you can confirm the chain is gone.

How long should a redirect chain be?
Aim for one hop. Every extra hop adds latency and can cost you link equity. Three or more is where you should clean it up.

301 or 302 for site migration?
301. It's permanent, and search engines transfer ranking signals through it. Use 302 only for temporary moves.

What's the most common cause of redirect chains?
Sequential migrations: every time a URL moves, someone adds a new redirect on top of the old ones instead of updating the target.

How do I find existing chains?
Run a redirect checker across your old URLs — it follows each path and reports every hop.

Do chains matter for users or just SEO?
Both. Users feel the extra hops as slower loads, and crawlers may give up on very long chains.

FAQ

How long should a redirect chain be?

Aim for one hop. Every extra hop adds latency and can cost you a slice of link equity. Three or more is where you should clean it up.

301 or 302 for site migration?

301. It's permanent, and search engines transfer ranking signals through it. Use 302 only for temporary moves.

What's the most common cause of redirect chains?

Sequential migrations: every time a URL moves, someone adds a new redirect on top of the old ones instead of updating the target.

How do I find existing chains?

Run a redirect checker across your old URLs — it follows each path and reports every hop. Then flatten each chain to a single 301.

Do chains matter for users or just SEO?

Both. Users feel the extra hops as slower loads, and crawlers may give up on very long chains.

How to Set Up Redirect Chains for a Website Migration

Why chains happen

The process

Step 1. Inventory every old URL

Step 2. Map each URL to its new home

Step 3. Flatten existing chains

Step 4. Implement single-hop 301s

Step 5. Verify every rule

What to check after the migration

FAQ

Table of Contents

Information

Tags

More Posts

301 vs 302 Redirects: When to Use 301, 302, 307, and 308

How to Find the Final URL Behind a Short Link

What Is a Redirect Chain? A Clear Guide With Real Examples

Too Many Redirects: Causes, Diagnosis, and Fixes

Do Redirect Chains Hurt SEO? What Google Recommends

Redirect Audit Checklist: How to Find Chains, Loops, and Broken Targets