Redirect Chain

A redirect chain is a sequence of two or more redirects between the original URL a user requests and the final page that loads. Instead of pointing straight from URL A to URL C, the path passes through one or more middle stops: A redirects to B, and B redirects to C. Each extra hop slows the load and can weaken the SEO signals passed to the final URL.

A single redirect (A to B) is normal and healthy. A chain begins at the second hop and gets worse with each one added.

Chain: /old-page → /temp-page → /new-page (3 URLs, 2 hops)
Direct: /old-page → /new-page (2 URLs, 1 hop)

Why Redirect Chains Matter

Redirect chains cost speed and dilute ranking signals. Every hop is a separate round trip between the browser and the server, so a three-hop chain forces the browser to make three requests before showing any content. On mobile connections, this adds real delay and hurts Core Web Vitals scores.

Search engines feel it too. Googlebot follows redirect chains but has a limit. Google’s documentation states it follows up to 10 redirect hops in a single crawl attempt. Beyond that, Googlebot stops and reports a redirect error in Search Console, leaving the final page uncrawled.

Long chains also risk leaking ranking signals. While Google confirmed that individual 30x redirects pass full PageRank, mixed chains that combine permanent and temporary redirects can behave unpredictably and slow how fast signals consolidate on the destination.

How Redirect Chains Form

Chains usually build up over time, not all at once. Common causes:

• Repeated site migrations. A page moves once, then moves again, and the old redirect is never updated to point at the newest URL.
• HTTP to HTTPS switches. An old http:// URL redirects to http://www, which then redirects to https://www, creating two or three hops.
• Trailing slash and www rules. Server rules that add or drop a slash or the www prefix stack on top of an existing page redirect.
• Platform or plugin defaults. CMS plugins sometimes add their own redirect on top of a manual one.

The pattern to watch for is a redirect that points to another URL that also redirects. Point every old URL directly at the live final destination instead. For a broader overview of how redirects work, see the link redirect glossary entry.

Redirect Chain vs Redirect Loop

A redirect chain ends at a real page. A redirect loop never ends. In a loop, URL A redirects to B, and B redirects back to A, so the browser cycles forever and shows an ERR_TOO_MANY_REDIRECTS error. Browsers cut off loops after roughly 20 hops. A chain slows things down but still resolves; a loop breaks the page entirely.

How to Find and Fix Redirect Chains

Auditing takes two steps: find the chains, then flatten them.

1. Scan your URLs. Run key URLs through a redirect checker to see every hop and status code in the path. Site-wide crawlers like Screaming Frog flag chains across a whole site. linkutm’s redirect checker shows the full redirect path and the status code at each step for any single URL.
2. Update the first redirect. Change the original redirect so it points straight to the final destination, removing every middle hop. Keep the type consistent, ideally a 301 for permanent moves.
3. Recrawl and confirm. Test the URL again to verify it now resolves in one hop, then request reindexing in Search Console if the page matters for search.

Frequently Asked Questions

What is a redirect chain?

A redirect chain is a path of two or more redirects between the URL a user requests and the final page that loads. Rather than going directly from the old URL to the new one, the request passes through one or more intermediate URLs. Each hop adds load time and can slow how search engines process the move.

Are redirect chains bad for SEO?

Yes, long redirect chains can hurt SEO. They slow crawling, waste crawl budget, and may stop Googlebot before it reaches the final page if the chain exceeds about 10 hops. A single redirect is fine; the problem starts when redirects stack on top of each other.

How many redirects is too many?

Aim for one hop and treat anything beyond that as cleanup work. Google follows up to 10 hops per crawl, but performance and signal loss suffer well before that limit. Every chain should be flattened to a single direct redirect.

How do I fix a redirect chain?

Point the first redirect directly at the final destination and delete the intermediate hops. Use a redirect checker to map the full path, update the original rule to a single 301, then recrawl to confirm the URL resolves in one step.

To map every hop and status code in a redirect path, run the free redirect checker at linkutm.