Redirect Chains

A redirect chain happens when a URL redirects to another URL, which then redirects again, before finally reaching the destination: A to B to C to D. A redirect loop is a chain that never ends, such as A to B and B back to A, so the page never loads.

Written by Paul Hoda, SEO consultant since 2005. Last updated 8 November 2026.

How redirect chains build up

Chains are rarely created on purpose. They grow over years of small changes:

  • A page is moved, then moved again during a redesign.
  • The site switches from http to https, then from non-www to www, with separate rules for each.
  • Trailing-slash rules add another hop.
  • A Website Migration redirects old URLs to pages that are later renamed.
  • Plugins and server rules both add redirects for the same URL.

Why redirect chains are bad for SEO

  • Slower crawling: Googlebot follows up to around 10 hops, but each one costs time. On large sites, chains waste Crawl Budget.
  • Signals may not pass: if a chain is too long or breaks, ranking signals from Backlinks may not reach the final page.
  • Slower pages for users: every hop adds a round trip to the server, which hurts Page Speed, especially on mobile.
  • Higher risk of errors: the more hops, the more chances that one returns a 404 or loops.

Redirect loops are worse: the page cannot load at all, so it drops out of search and users see an error.

How to find redirect chains

  • Crawl your site with an SEO crawler and use its redirect chain report.
  • Check important old URLs, especially those with backlinks, using a header checker that shows every hop.
  • Review the Pages report in Google Search Console for “Redirect error”.
  • Export your redirect rules from plugins and server files and look for overlaps.

How to fix redirect chains

  1. Point every old URL directly to the final destination in a single 301 Redirect.
  2. Update internal links so they link straight to the final URL rather than relying on redirects (Internal Linking).
  3. Combine protocol and host rules so http://domain and non-www versions go to https://www. in one hop.
  4. Remove duplicate rules in plugins, .htaccess and CDN settings.
  5. Fix loops immediately by finding which rule sends traffic back.
  6. Update your XML Sitemap so it lists only final URLs returning 200.

Preventing chains in the future

Keep a single, documented redirect map for your site. Whenever you change a URL, check whether existing redirects point to it and update them too. Before any migration, audit existing redirects so new rules do not stack on top of old ones.

How many hops are acceptable?

One redirect is ideal. Two is usually harmless. Three or more should be fixed, especially for pages that receive links or traffic. For internal links, aim for zero redirects: link directly to the live URL.

Key Takeaways

  • A redirect chain passes through several URLs before reaching the final page.
  • Chains slow crawling and pages and risk losing signals.
  • Point each old URL straight to its final destination.
  • Combine protocol and host rules into one redirect.
  • Keep a single documented redirect map.

Related Terms

Wondering what to fix first on your site? Get a free check of your site’s SEO, or keep learning in the SEO Encyclopedia.