Redirect Chain

What Is a Redirect Chain?

Redirect chains often develop unnoticed after multiple website migrations and are a frequently overlooked technical SEO problem. With each additional redirect, some link equity is lost and load time increases. Tools like Screaming Frog automatically identify redirect chains — resolve them by making every old URL point directly to the final destination URL. Particularly on large websites, this can bring noticeable performance improvements.

A redirect chain is a sequence of multiple consecutive redirects, where one URL is forwarded to a second URL, which is forwarded to a third URL, and so on. For example: old-site.com → intermediate-site.com → new-site.com. This often happens unintentionally during website migrations or when multiple restructurings have been carried out in sequence. Redirect chains are a problem for SEO because each additional redirect increases load time, slows the crawl process, and leads to additional waste of crawl budget. Google recommends avoiding redirect chains and redirecting more directly.

Technically, each redirect costs an additional HTTP request: the browser requests URL 1, receives status 301 and is forwarded to URL 2, requests URL 2, receives another 301 and is forwarded to URL 3, and so on. This noticeably slows page load time. With a redirect chain of 3 or more steps, the original URL also loses more ranking power — not all 90–99% of link equity is passed on; a little less at each step. It is also inefficient for the crawler: with a limited budget, Google would rather crawl your actual pages than follow redirects.

In management, you should regularly check whether redirect chains have formed. Tools like Screaming Frog or Ryte detect these automatically. The fix is simple: the entire redirect chain should be replaced by a direct 301 redirect. From old-site.com → new-site.com, not via multiple stops. For large migrations, a clean mapping table should be created before implementing redirects. For websites with historically many redirects, a “redirect cleanup” is recommended, where unnecessary chains are resolved and new direct connections are created.