What is a redirect chain?
Chain versus single redirect versus loop, why chains accumulate one migration at a time, the latency and crawl-budget cost of each hop, and how to flatten to one hop.
A redirect chain is a sequence of redirects a URL passes through before reaching its final destination — page A redirects to B, which redirects to C, which finally lands on D. Each individual redirect might be a perfectly correct 301, but strung together they become a tax on speed and crawling that is almost always avoidable.
Chain versus single redirect versus loop
A single redirect is one hop: A → B. That is normal and healthy — it is how you move a page properly. A chain is two or more hops in a row: A → B → C. A loop is a chain that never resolves — A → B → A — which the browser eventually gives up on with a “too many redirects” error, making the page completely inaccessible. Chains waste resources; loops break the page outright.
Why chains happen
They accumulate one migration at a time. A site moves from http to https (one redirect), later consolidates non-www to www (a second), then standardizes trailing slashes (a third) — and a single old URL now passes through all three before it arrives. Nobody adds a chain on purpose; they are the residue of changes made at different times without flattening the earlier rules.
Why they hurt
Latency. Each hop is another round trip to the server before the visitor sees anything, and the cost is worst on slow mobile connections. Crawl budget. Googlebot follows only a limited number of hops (around ten) before giving up, and every redirect it does follow is a fetch spent on plumbing instead of real pages — a real drain on large sites. Signal dilution. While 301s pass ranking signals, chaining several together is an unnecessary risk when a direct redirect passes them cleanly. Analytics loss. Referrer data can be dropped across multiple hops.
Redirect loops
A loop is the failure state of a chain. If A points to B and B points back to A — often through a misconfigured mix of HTTPS and www rules that contradict each other — the request bounces indefinitely and the browser aborts with “ERR_TOO_MANY_REDIRECTS.” Unlike a chain, which merely slows things, a loop takes the page down entirely, so it is always urgent.
How to fix them
Flatten every chain to a single hop: for each starting URL, redirect it directly to the final live destination rather than to another redirect. When you add a new redirect rule, check whether it now sits in front of an existing one and update the source accordingly. After any migration — protocol, domain, or URL structure — re-audit so today’s clean redirect does not become tomorrow’s second hop.
How to check yours
Our redirect checker traces the full hop path for a URL, so you can see every step between the address you entered and the page it finally reaches — and spot chains and loops at a glance. The HTTP header checker shows the status code and Location header at each step, which is how you confirm each hop is the 301 you intended.
Frequently asked questions
- What is a redirect chain?
- A redirect chain is a sequence of two or more redirects a URL passes through before reaching its final destination — for example, page A redirects to B, which redirects to C. Each hop may be a valid redirect on its own, but chained together they add latency and waste crawl budget.
- Why are redirect chains bad for SEO?
- Each hop adds a round trip that slows the page, especially on mobile. Googlebot follows only a limited number of hops (around ten) before giving up, and every redirect it follows spends crawl budget on plumbing instead of real pages. Chaining also risks diluting the ranking signals a single direct redirect would pass cleanly.
- How is a redirect chain different from a single redirect?
- A single redirect is one hop (A to B), which is the correct way to move a page. A chain is two or more hops in a row (A to B to C). A redirect loop is a chain that never resolves, such as A to B back to A, which the browser aborts with a 'too many redirects' error, breaking the page entirely.
- What causes redirect chains?
- They accumulate through successive site changes: moving from HTTP to HTTPS adds one redirect, consolidating non-www to www adds another, standardizing trailing slashes adds a third. An old URL then passes through all of them. Chains are the residue of changes made at different times without flattening the earlier rules.
- How do I fix a redirect chain?
- Flatten it to a single hop: update each starting URL to redirect directly to the final live destination rather than to another redirect. Whenever you add a new redirect rule, check whether it now sits in front of an existing one, and re-audit redirects after any protocol, domain, or URL-structure migration.
- What is a redirect loop?
- A redirect loop is a chain that never resolves — for example A redirects to B and B redirects back to A, often due to contradictory HTTPS or www rules. The request bounces indefinitely until the browser aborts with 'ERR_TOO_MANY_REDIRECTS'. Unlike a chain that only slows a page, a loop makes it completely inaccessible.