Redirect chain too long: why it hurts crawling and UX
Every redirect hop is a small cost. Stack three or four of them on a key URL and you're losing time, signals, and sometimes rankings.
A URL goes through multiple redirects before reaching its final destination, http to https, then non-www to www, then trailing slash, then a legacy path mapping. Each hop adds a round-trip and a chance for signal loss. Loops are worse: the chain never resolves and the URL effectively disappears.
Long redirect chains slow first-byte time for users, eat into crawl budget on large sites, and can dilute or drop link signals between hops. Mixed 301/302 chains confuse search engines about which URL is permanent. Loops break crawl entirely.
- Stacked migrations: each redesign added a new redirect layer instead of replacing the old ones.
- Protocol + host + slash redirects all happening separately (http → https → www → trailing slash).
- A 302 sits in front of a 301, mixing temporary and permanent intent.
- A meta refresh fires after an HTTP redirect, adding an invisible client-side hop.
- An auth or geo middleware bounces requests through an interim URL.
- A loop: A redirects to B redirects to A.
- Open Redirect Chain Checker and paste the original URL.
- Look at the hop list: status code, location, duration, and content type for each step.
- Check the total number of hops, whether the chain crosses domains, and whether it mixes 301/302.
- Confirm there is no loop. Loops are a critical-severity issue.
- Look out for meta refresh tags reported on the final page, those are invisible to a quick HTTP check.
- 1
Redirect old URLs straight to the final destination
Replace any A → B → C chain with A → C. The intermediate hops are dead weight unless you have a specific reason to keep them.
- 2
Pick a single canonical host, scheme, and slash style
Decide whether you want https://www.example.com/ or https://example.com/, with or without trailing slashes, then redirect everything else there in one hop.
- 3
Stop mixing 301 and 302
If the move is permanent, use 301. Mixing temporary and permanent codes in one chain confuses search engines about which URL to consolidate signals onto.
- 4
Remove leftover meta refresh tags
If the final page also issues a <meta http-equiv="refresh">, that's a hidden extra hop and a UX issue. Use a real HTTP redirect instead.
- 5
Break loops immediately
A redirect loop is a critical bug. Identify the two URLs flipping between each other and pick the canonical destination. Loops effectively delist the URL until fixed.
How many redirects are too many?
More than 3 hops is generally too many. Google says it follows up to about 10 redirects but stops trusting the chain well before that. Aim for 0–1 hops on any URL that matters.
Are 301 redirects better than 302?
For permanent moves, yes. 301 tells search engines to consolidate signals onto the new URL. 302 (and 307) are temporary and may cause search engines to keep the old URL indexed.
Can redirect chains affect SEO?
Yes. They slow down crawl, can dilute link equity at each hop, and create ambiguity about the canonical destination. On large sites they also waste crawl budget that could be spent on new content.
Ready to diagnose your URL?
Redirect Chain Checker runs the exact checks discussed above.