How to Fix Redirect Chains and Loops for Better SEO

This guide shows you how to find every redirect chain and loop on your site and collapse each one into a single hop. If you are searching for how to fix redirect chains, the short version is simple: point every old URL straight at its final destination and update the links that still use old URLs.

What is a redirect chain and how is it different from a loop?

A redirect chain is any path where a URL redirects to another URL that also redirects, so the browser or crawler needs two or more hops to reach a page that returns 200. A typical example is http://site.com/page to https://site.com/page to https://www.site.com/page to https://www.site.com/page/.

A redirect loop is a chain with no end. URL A points to URL B and URL B points back to A, so the page never loads and the browser shows an error such as “too many redirects”. A chain wastes time; a loop breaks the page completely.

Chains usually build up over years. A site moves to HTTPS, then switches to www, then changes its permalink structure, and each change adds a rule on top of the old ones instead of rewriting them.

How many redirects in a chain is too many?

Any chain longer than one hop is worth fixing, and Google’s own guidance is to redirect to the final destination directly. In its documentation on site moves with URL changes, Google says Googlebot can follow up to 10 redirect hops, but if you cannot avoid a chain, keep it short: ideally no more than 3 hops and fewer than 5.

Those numbers are a ceiling, not a target. Every extra hop adds a round trip for real visitors, and on a slow mobile connection that delay is easy to feel. In my audits I treat one hop as normal, two hops as a task for the next sprint and three or more as urgent.

Do redirect chains hurt SEO?

Redirect chains can hurt SEO indirectly because they slow pages down, waste crawl requests and make your canonical signals messier, even though a short chain will not get a page removed from Google. Google still follows them, so the damage is gradual rather than sudden.

The bigger risks are practical:

• Visitors wait longer before the first byte arrives, which pushes up Largest Contentful Paint.
• Large sites spend crawl activity on hops instead of new or updated pages.
• If any hop in the chain is a temporary redirect, you send a mixed signal about which URL should be canonical.
• A chain can turn into a loop the next time someone adds a rule, which takes the page offline.

Google explains in its guide to redirects and Google Search that permanent redirects (301 and 308) signal that the target should be canonical, while temporary ones (302, 303 and 307) do not. A chain that mixes the two is a common reason the wrong URL keeps showing in results. If Search Console lists many URLs under “Page with redirect”, my guide to the Page with redirect status explains when that report needs action and when it is expected.

How do I find redirect chains on my site?

You find redirect chains by crawling your site with a tool that follows redirects and reports the full path, then checking your server rules and backlinks for old URLs. One method is rarely enough, so I combine three.

1. Crawl the site. Run a crawler such as Screaming Frog, Sitebulb or the site audit in Semrush or Ahrefs with redirect following switched on. Export the redirect chains report.
2. Test the four homepage variants. Request http, https, www and non-www versions of your homepage. Each should reach the final version in exactly one hop.
3. Check links you do not control. Export your top linked pages from Search Console’s Links report or a backlink tool and run those URLs through the crawler in list mode. Old URLs with backlinks often sit behind two or three historic redirects.
4. Read the rules. Open your .htaccess, Nginx config, CDN rules and any WordPress redirect plugin. Look for rules that overlap, such as an HTTPS rule and a www rule that run one after the other.

A quick command line check also works for single URLs: curl -I -L shows each status code and Location header in order, so you can count the hops yourself.

How do you fix redirect chains and loops step by step?

You fix a chain by editing the first redirect so it goes straight to the final URL, and you fix a loop by deleting or correcting the rule that points the target back to the source. After that, you remove the reasons the old URLs are still being requested.

1. Map each chain. For every chain, write down the starting URL and the final URL that returns 200.
2. Rewrite the first rule. Change the source URL’s redirect to point directly at the final URL with a 301 or 308. Leave the middle URLs redirecting to the final URL too, since they may have links of their own.
3. Merge protocol and host rules. Replace separate HTTPS and www rules with one rule that sends any variant to https://www in a single step.
4. Break loops. Find the pair of rules that point at each other. Usually one is a leftover from an old migration or a plugin conflicts with a server rule. Keep one, delete the other.
5. Update internal links. Replace links in menus, footers, body content and image URLs with the final URL so visitors and crawlers never hit a redirect inside your own site.
6. Update canonicals, hreflang and sitemaps. These should list final URLs only. A sitemap full of redirecting URLs sends weak and confusing signals.
7. Re-crawl and confirm. Run the crawler again and check that every chain now has one hop and that no loop remains.

Google recommends keeping redirects from a move for as long as possible, generally at least one year, so do not delete old rules just because the chain is gone. On WordPress, a redirect plugin and a server rule fighting each other is the most common loop I find. If you are planning a bigger rebuild, my website redesign service includes a full redirect map so chains never form in the first place.

What does fixing a real redirect chain look like?

How can you stop redirect chains from coming back?

You stop chains from returning by keeping one central redirect map and checking it every time a URL changes. Most chains are created during routine edits, not migrations.

• Before adding a redirect, search the map for any rule that already points at the source URL and update that rule too.
• Keep protocol, host and trailing slash rules in one place, ideally at the server or CDN level.
• Add a redirect check to your monthly crawl. My free SEO audit checklist includes it alongside other crawl health checks.
• When you change a slug, update internal links the same day.

If you would rather hand this off, my technical SEO service covers redirect audits, chain fixes and the follow-up crawl to prove every path is clean.

Frequently asked questions