Redirect chains: how many hops is too many?

A redirect chain is a series of redirects where each one sends the visitor to the next instead of the final page; every extra hop costs time, crawl budget, and consolidation signal. A chain of more than two or three hops is usually worth flattening to one. One redirect is common, two can be reasonable when scheme and host both change, and past that the cost is mostly waste.

What is a redirect chain?

A redirect chain is a series of redirects in which each one sends the request to another URL instead of directly to the final page. The visitor lands on page one, gets sent to page two, then page three, and so on until a page answers with 200. Each intermediate step is a hop.

What does each hop cost?

Each hop adds a round trip, which delays the final response and costs the crawler budget it could spend on pages instead of hops. Each hop also dilutes the transfer: the consolidation signal is meant for the final URL, and every redirect in between is another place the link equity can stop.

Long chains can also break partway. A visitor or a crawler that gives up before the final URL never reaches the destination, so the page is effectively unreachable even though the chain technically still works.

Where does Google give up?

Google does not follow redirects forever. Past a point, hops stop being followed and the final URL can be treated as unreachable. There is no fixed published number, but a chain that runs on past several hops is a real risk. Do not build the chain and hope it holds; flatten it so the risk does not exist.

What is the difference between 301, 302, and meta refresh?

A 301 signals a permanent move and consolidates the old URL onto the target. A 302 is temporary: the original URL keeps the signals, until a long-lived 302 is effectively permanent in practice. A meta refresh is a page-level redirect written in the HTML, slower than a server redirect and not always followed. Prefer a 301 that points straight at the final URL.

What creates chains without you noticing?

The classic cause is stacking. One page ends up reachable through a series of normal-looking additions: http://example.com/page goes to the trailing slash, then to HTTPS, then to the www host. Four responses for one page. Every platform addition, a CDN, the www rule, a trailing-slash rule, adds another hop, and each one is invisible on its own until you follow the whole chain.

How do I flatten a chain?

Choose the final URL, then point every intermediate URL at it with one direct 301. Remove the middle hops, and update your internal links to skip the chain. Use the redirect checker: it shows every status and URL at each position, whether the final response is HTTP 200, hostname and scheme changes, and it flags chains with more than two redirects.

A silent chain can be loading slow and costing conversions for weeks before anyone notices. stillindexed.com checks your pages’ redirects and alerts you when something changes. Starter checks every 30 minutes, Agency every 15: https://app.stillindexed.com/auth/request