What a redirect chain is
A redirect chain happens when one URL redirects to a second URL, which redirects to a third, and so on, before the final page loads. A single redirect is normal. A chain means the visitor, and search engine crawlers, make extra round trips for no benefit.
http://example.com/old 301
https://example.com/old 301
https://www.example.com/old 301
https://www.example.com/new 200
Three redirects here, where one would do.
Why chains cause problems
- Speed. Every hop is another request, DNS lookup, and often a new TLS handshake. On mobile networks the delay is noticeable.
- Crawling. Search engines follow only a limited number of hops (Google documents up to 10) and may give up on long chains.
- Maintenance. Each hop is another rule that can break or contradict the others.
- Loops. Two rules that send visitors back and forth give an endless redirect, shown by browsers as “too many redirects”.
How chains appear
Chains usually build up from rules added at different times: http to https, non-www to www, adding or removing a trailing slash, a CMS redirect, a plugin redirect, and an old migration that was never cleaned up.
How to find them
Enter the original URL in the HTTP Status & Redirect Checker. It lists every hop with its status code, address, and time. Test the variants visitors actually use: with and without www, http and https, with and without a trailing slash.
How to fix them
- Decide the one canonical address, for example
https://www.example.com/. - Make every old variant redirect directly to that address in a single hop.
- Use 301 or 308 for permanent moves and 302 or 307 only for temporary ones.
- Update internal links, sitemaps, and canonical tags to point to the final URL so most visitors never meet a redirect.
- Retest each variant, and the rules after any plugin or server change.
For http to https and www redirects, one server-level rule is cleaner than several plugin rules.
Redirect loops
If the checker reports a loop, two rules conflict, such as a plugin forcing the trailing slash while the server removes it, or a CDN set to HTTP while the origin forces HTTPS. Disable one of the two and retest.
FAQ
How many redirects are acceptable?
One hop to the final address is a good target. Two is tolerable for old URLs. More than that deserves a fix.
Do redirects lose SEO value?
Properly used permanent redirects pass signals to the new address, but long chains and loops waste crawl budget and risk errors.
Should I remove old redirects eventually?
Keep them as long as old links or search results still point to them.