Redirects are one of the most useful tools in SEO. They keep visitors and link value flowing when URLs change. But every redirect you add sits on top of the ones that came before, and after a few years of redesigns, HTTPS switches and URL clean-ups, a single old link can bounce through three, four or five URLs before it reaches a real page. That is a redirect chain. When the bouncing never ends because two URLs point back at each other, it is a redirect loop.
Chains slow down users, waste crawl activity and make your site harder to maintain. Loops are worse: the page simply fails to load, and search engines cannot reach it at all.
This guide explains what redirect chains and loops are, what Google says about them, how to find them on your site and a step-by-step process for fixing them for good.
Key Takeaways
- A redirect chain is any path with more than one redirect between the requested URL and the final page; a loop is a chain that never reaches a final page.
- Google says Googlebot can follow up to 10 hops but recommends redirecting straight to the final destination, or keeping chains to ideally no more than 3 hops.
- Most chains come from layered changes: HTTP to HTTPS, www to non-www, trailing slashes and old migrations.
- The fix is to update every redirect rule so it points directly to the final URL, then update internal links so they do not hit redirects at all.
- Loops usually come from conflicting rules in different layers: server config, CMS plugins, CDN and SSL settings.
What Is a Redirect Chain?
A redirect chain happens when URL A redirects to URL B, which redirects to URL C, and so on until a page finally returns a 200 status. A typical real-world example looks like this:
http://example.com/services 301 →
https://example.com/services 301 →
https://www.example.com/services 301 →
https://www.example.com/services/ 200 OKEach step is a separate HTTP request. The visitor's browser, or Googlebot, has to wait for each response before moving on. None of these redirects is wrong on its own; together they form a three-hop chain where a single redirect would do.
What Is a Redirect Loop?
A redirect loop happens when the chain circles back on itself: A redirects to B and B redirects back to A, or a longer cycle repeats. Browsers give up and show an error such as "This page isn't working – redirected you too many times". Search engines cannot index the page, and any links pointing to it lead nowhere.
| Redirect chain | Redirect loop | |
|---|---|---|
| Does the page load? | Yes, eventually | No |
| User impact | Slower load, especially on mobile | Error page, lost visitor |
| Search impact | Extra crawl requests; long chains may not be followed to the end | Page cannot be crawled or indexed |
| Urgency | Medium; fix in your next technical sprint | High; fix immediately |
| Common cause | Redirects layered over years of changes | Conflicting rules between server, CMS, CDN or SSL settings |
What Google Says About Redirect Chains
Google covers chains in its documentation on site moves. The advice is to redirect directly to the final destination, and if that is not possible, to keep chains short:
“If this is not possible, keep the number of redirects in the chain low, ideally no more than 3 and fewer than 5.”
— Google Search Central, Site moves with URL changes
The same page notes that Googlebot can follow up to 10 hops in a chain, and that chaining redirects adds latency for users while not all user agents and browsers support long chains. In practice that means a two-hop chain is not a disaster, but there is no benefit to keeping it, and long chains risk Google stopping before the final page.
Google also recommends server-side permanent redirects wherever possible, with meta refresh and JavaScript redirects as fallbacks. JavaScript redirects inside a chain are particularly fragile, because Google only sees them if rendering succeeds. Our guide to 301 vs 302 redirects explains which status codes to use, and our HTTP status codes guide covers the full set.
Why Redirect Chains Hurt SEO and UX
- Slower pages. Each hop adds a round trip before the page even starts loading, which can affect real-user metrics like those described in our Core Web Vitals guide.
- Wasted crawling. Every hop is a separate request. On large sites this adds up and matters for crawl budget.
- Risk of breakage. The more links in a chain, the more chances one of them breaks during a future change, turning a chain into a 404 or a loop.
- Messy signals. Chains often mix 301s and 302s, sending inconsistent signals about which URL is canonical.
- Harder maintenance. Nobody can tell where a URL really ends up without testing it, and redirected URLs that lose their internal links can quietly become orphan pages.
Common Causes of Chains and Loops
- Separate rules for HTTP to HTTPS, non-www to www and trailing slash that fire one after another instead of together.
- Multiple site migrations, where old redirects point to URLs that were themselves later redirected.
- Changing URL slugs in a CMS that automatically adds a redirect each time.
- Redirect plugins and server rules (.htaccess, Nginx) that both act on the same URL.
- CDN or hosting settings that force HTTPS while the origin server forces HTTP, a classic loop.
- Localisation or geo-redirects that bounce users between country versions. See our hreflang guide for better alternatives.
How to Find Redirect Chains and Loops
| Method | Best for | What to look for |
|---|---|---|
| Site crawler (Screaming Frog, Sitebulb, Semrush Site Audit) | Whole-site discovery | Redirect chain and loop reports, internal links pointing to 3xx URLs |
| List-mode crawl of old URLs | Migrations and legacy URLs | Chains starting from URLs that are no longer linked internally |
| Browser developer tools (Network tab) | Checking a single URL | Each 301/302 response and its Location header |
Command line: curl -sIL URL | Quick checks and scripts | Every hop's status code and location |
| Search Console Page Indexing report | Seeing Google's view | "Page with redirect" and "Redirect error" statuses |
Do not just crawl your live site. Many chains start from URLs that are no longer linked anywhere internally but still have backlinks or bookmarks. Export old URLs from previous sitemaps, analytics, your backlink tool and your redirect map, then crawl that list. In Search Console, the "Redirect error" status flags URLs where Google hit a loop, an overly long chain, an empty or bad redirect URL, or a chain that exceeded the maximum URL length. Our Page Indexing report guide covers this status.
How to Fix Redirect Chains: Step by Step
- Export every chain. From your crawler, export each chain with its source URL, every hop and the final destination with its status code.
- Confirm the final destination is correct. It must return 200, be indexable and be the right page. If it is a 404, choose the best live replacement first.
- Rewrite each redirect rule to point straight to the final URL. A to D, B to D and C to D, rather than A to B to C to D.
- Combine protocol and hostname rules. Make HTTP to HTTPS and www normalisation happen in one rule that sends users to the canonical version in a single hop.
- Use permanent server-side redirects. Use 301 or 308 for permanent moves rather than JavaScript or meta refresh.
- Update internal links. Change links in navigation, content, canonicals, hreflang and sitemaps so they point to the final URL and never trigger a redirect. Our internal linking guide explains why this matters.
- Update your XML sitemap. It should list only final, 200-status canonical URLs.
- Re-crawl and test. Crawl the original source list again and confirm every URL now reaches its destination in one hop.
- Keep redirects in place. Google advises keeping redirects for as long as possible, generally at least a year; for users, consider keeping them indefinitely.
How to Fix a Redirect Loop
- Clear your browser cache and cookies, and test in a private window, to confirm the loop is real.
- Trace the loop with
curl -sILor browser developer tools to see which URLs repeat. - Check each layer that can issue redirects: server config, CMS site URL settings, redirect plugins, CDN rules and SSL mode.
- Remove or correct the conflicting rule so only one layer decides the canonical protocol and hostname.
- Purge server, plugin and CDN caches, then test again.
Common Mistakes
- Fixing the chain but not the links. Internal links that still point to old URLs keep generating unnecessary redirects.
- Redirecting everything to the homepage. Irrelevant redirects frustrate users and do not pass along topical relevance. Map old pages to their closest equivalent, and use a 404 or 410 where none exists. See how to fix 404 errors.
- Removing old redirects too soon. Deleting historical rules to "clean up" can break backlinks that still point at those URLs.
- Using 302s for permanent moves. Temporary redirects in a chain send mixed signals about the canonical URL.
- Ignoring chains during migrations. Every website migration should include a step that flattens old redirects to the new final URLs.
Related Guides
- Search Console Page Indexing Report: Every Status Explained
- IndexNow: What It Is and How to Use It
- Faceted Navigation SEO: How to Handle Filters
Frequently Asked Questions
How many redirects is too many?
Ideally one. Google recommends redirecting directly to the final destination and, where that is not possible, keeping chains to ideally no more than 3 and fewer than 5 hops. Googlebot follows up to 10 hops.
Do redirect chains lose link equity?
A single permanent redirect is the standard way to consolidate signals to a new URL. Long chains add risk: they may not be followed to the end, they slow users down and they break more easily. Flattening them removes that risk.
What causes the "too many redirects" error?
It is a redirect loop, usually caused by conflicting rules between your server, CMS, plugins, CDN or SSL settings, or by stale cached redirects.
Is a single redirect bad for SEO?
No. A single permanent redirect is the correct way to move a page. The problem is stacking several redirects in a row or linking internally to redirecting URLs.
How do I check a redirect chain for one URL?
Use a redirect checker, your browser's developer tools Network tab, or run curl -sIL followed by the URL to see each hop and status code.
Conclusion
Redirect chains and loops are a classic case of technical debt. Each one was added for a good reason, but together they slow pages, waste crawling and risk breaking. Audit your old and current URLs, point every redirect straight to its final destination, update internal links and keep the rules in place. If you are planning a redesign or migration in 2026 and want it done without losing traffic, our technical SEO team can help, or you can get a free quote.
