How Redirect Chains Affect SEO
A redirect chain is when one URL redirects to another, which redirects to another, before finally reaching the real page. Each hop costs time and, done wrong, leaks the SEO value the original link earned.
301 vs 302 — the key distinction
A 301 is a permanent redirect: search engines transfer ranking signals to the destination and update their index to the new URL. A 302 is temporary: engines keep the original URL as canonical and are slower to pass value. Using 302 for a permanent move is one of the most common — and costly — redirect mistakes.
How chains hurt
- Latency — every hop is another round trip before the page loads; users feel it, especially on mobile.
- Crawl budget — search bots waste requests following hops instead of indexing real pages.
- Signal dilution — long or mixed chains can weaken how much link equity reaches the final URL.
- Failure risk — the more hops, the more chances one breaks and produces a dead end or loop.
Redirect loops
A loop is a chain that never terminates — A → B → A. Browsers give up with "too many redirects" and the page never loads. Loops usually come from conflicting rules (e.g. HTTP→HTTPS and a www rule fighting each other) and block the page entirely.
How to fix chains
- Point every redirect straight at the final destination — collapse A → B → C into A → C.
- Use 301 for permanent moves so ranking value transfers.
- Audit HTTP→HTTPS and www/non-www rules so they don't stack or conflict.
- Re-check after changes — a redirect test shows the full chain, each status code, and the final URL, so you can confirm it's a single clean hop.
Frequently asked questions
How many redirects are too many?
Ideally zero to one. Each extra hop adds latency and risk; keep chains to a single 301 to the final URL wherever possible.
Do 301 redirects pass SEO value?
Yes — a 301 permanent redirect passes the large majority of ranking signals to the destination. A 302 temporary redirect does not reliably do so, which is why using the right type matters.