What is a redirect chain?
A redirect chain is a redirect that lands on another redirect. The browser asks for page A, is sent to page B, is sent from B to page C, and only then gets content. Each step is a separate round trip to the server. Chains build up quietly over years: the site moved from http to https, then dropped the www, then rebuilt its URL structure, then retired a product, and every one of those changes added a redirect on top of the last without anyone collapsing the stack.
Two hops is a chain. Five is common on old sites. Google's documentation says its crawler follows up to ten hops before giving up, and that the signals passed through each one are not guaranteed to survive intact.
Why it matters
Why a redirect chain matters
Speed first. Every hop adds a server round trip, often a few hundred milliseconds on a phone, before the page even begins to load. A chain of three can add a full second to a page that was otherwise fast, and that second counts against Core Web Vitals.
Then crawling and authority. A crawler that spends its budget following chains has less left for the pages that matter, and pages buried behind long chains get crawled less and indexed later. Ranking signals passing through a chain can also leak, so a page with good links pointing at an old URL may be getting less from them than it should. After a migration, chains are one of the most common reasons the new site underperforms the old one.
In practice
How redirect chains work in practice
- 01
Finding them takes a crawl. A site crawler such as Screaming Frog or Sitebulb follows every link and every redirect and reports the chains, with each hop and its status code. Search Console's page indexing report flags URLs with redirect errors. Check the usual culprits by hand too: the http version of the homepage, the www and non-www versions, and a URL with a trailing slash and without.
- 02
Fixing means collapsing. Every redirect that points at another redirect is updated to point straight at the final destination, so A goes to C directly and B goes to C directly. Then internal links are updated to point at C in the first place, because a link that resolves through a redirect is a redirect you did not need. After a migration this is a scheduled task: crawl, collapse, recrawl, until the report is clean.
Watch out
What people get wrong about redirect chains
Assuming a redirect to a redirect is harmless because the visitor gets there in the end. The visitor waits, the crawler counts the cost, and the signal weakens on the way. The destination being right does not make the route fine.
The other mistake is fixing the chain without fixing the links. If the navigation still points at the old URL, every click still goes through at least one redirect. Update the link and the redirect becomes a safety net instead of the main road.
