A redirect chain occurs when a URL redirects to another URL, which in turn redirects to yet another URL, creating a sequence of multiple hops before reaching the final destination. For example, URL A redirects to URL B, which redirects to URL C, which finally serves the content. Each hop in the chain adds latency and can dilute SEO value.
Redirect chains commonly arise during site migrations, URL restructuring, or when multiple URL shortening services are layered. Over time, as URLs are updated without cleaning up old redirects, chains can grow to three, four, or more hops. Each additional hop adds network round-trip time and increases the risk of the chain breaking if any intermediate URL becomes unavailable. Site migration books on Amazon discuss prevention strategies.
Google recommends keeping redirect chains as short as possible, ideally a single hop from source to destination. While Googlebot can follow chains of up to five redirects, each hop reduces crawl efficiency and may result in incomplete link equity transfer.
To identify and fix redirect chains, use tools like Screaming Frog, Ahrefs, or browser developer tools to trace the full redirect path. The fix is straightforward: update each redirect in the chain to point directly to the final destination, eliminating intermediate hops. SEO audit tools books on Amazon cover diagnostic approaches.