Redirect Chains: How to Find Them and Fix Them for Good
Every extra redirect costs a round trip before your page starts loading. Here is how chains build up, why they matter, and how to cut them to a single hop.
A redirect sends a visitor, or a search engine, from one address to another. One redirect is fine. A redirect chain is when one redirect leads to another, and then another, before the visitor finally reaches the page.
How chains build up
Nobody plans a redirect chain. They grow over the years:
- The site moves from
http://tohttps://. That is one redirect. - Later, the team decides on
wwwaddresses. That is a second one. - Then a page is renamed, and the old address is redirected to the new one. That makes three.
Now a visitor who clicks an old link goes http://example.com/old-page → https://example.com/old-page → https://www.example.com/old-page → https://www.example.com/new-page. That is three hops before the first byte of the real page arrives.
Why chains matter
- Speed. Each hop is a full request and response. On a slow mobile connection, every hop can add a noticeable delay before the page starts loading.
- Crawling. Search engines follow redirects, but not forever. Googlebot follows up to about ten hops, then gives up. Long chains also use up crawl time that could go to your real pages.
- Lost signals. A clean, permanent (301) redirect passes ranking signals to the new page. Chains add more places where something can break, for example one hop that is a temporary (302) redirect, or one that returns an error.
Redirect loops
A loop is a chain that never ends: page A redirects to B, and B redirects back to A. Browsers stop and show an error such as "too many redirects". Loops usually come from two rules that disagree, for example a server rule that adds www and a plugin setting that removes it.
How to find chains
- Test your main addresses. Check all four versions of your home page:
http://andhttps://, with and withoutwww. Each should reach the final address in one hop. - Test old links. Addresses from old sitemaps, old blog posts and backlinks are where chains hide.
- Check internal links. If your own menu links to an address that redirects, change the link to the final address. That removes the redirect completely.
Our Redirect Checker follows every hop and shows the status code and address of each step, so a chain is easy to spot.
How to fix them
- Point every old address straight at the final one. Instead of A → B → C, make it A → C and B → C.
- Use 301 for permanent moves. Keep 302 for truly temporary changes.
- Handle HTTPS and www in one rule. On Apache, a single rule can send every variation directly to
https://www.(or to the non-www version) in one hop. - Update internal links, the sitemap and canonical tags to use final addresses, so the redirects are only needed for outside links.
Quick checklist
- Every version of your home page reaches the final address in one hop.
- No redirect in your site is a 302 when it should be a 301.
- Your sitemap lists only final addresses that answer with 200.
- Your menus and internal links never point at a redirect.
Fix these four and redirects stop being a problem you have to think about.
Free tools for this topic
Check your own site in under a minute
Run a free SEO audit and see exactly where your pages stand on the issues covered in this article.
Run Free SEO Audit