A redirect chain occurs when a URL redirects to another URL, which then redirects to yet another URL, creating multiple hops before reaching the final destination. For SEO, redirect chains are problematic because: (1) Each hop dilutes PageRank — Google confirmed that 301 redirects pass most but not all link equity, and each additional hop compounds the loss; (2) They slow down page load times, harming Core Web Vitals and user experience; (3) Googlebot may stop following redirects after approximately 5 hops, risking incomplete indexing. Best practice: keep redirects to a single hop whenever possible.

301 (Permanent Redirect): Use this for permanent URL changes — site migrations, URL restructuring, or consolidating duplicate pages. Google eventually transfers link equity to the new URL and replaces the old URL in its index. 302 (Temporary Redirect): Use for short-term changes like A/B testing, seasonal promotions, or temporary maintenance pages. Google typically keeps the original URL indexed and does not transfer full link equity. Using a 302 when a 301 is needed (or vice versa) can confuse search engines and harm rankings. When in doubt for permanent changes, always use 301.

Google's official stance from John Mueller is that Googlebot follows up to 5 redirect hops per crawl before stopping. However, for optimal SEO performance, the recommendation is much stricter: aim for zero or one redirect hop. Each additional hop increases page load time, wastes crawl budget, and incrementally reduces the link equity passed to the final destination. If you have chains of 3+ redirects, prioritize fixing them. Common sources of long chains include: HTTP→HTTPS→WWW→trailing slash→new URL (4 hops that should be consolidated into 1).

A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (or through a longer cycle like A→B→C→A). This creates an infinite loop that browsers eventually break with a "too many redirects" error. Redirect loops are devastating for SEO — search engines cannot index the content, and users cannot access the page. Use this Redirect Path Tracer tool to detect loops: if you see the same URL appear twice in the chain, you've identified a loop. Common causes include misconfigured .htaccess rules, conflicting CMS plugins, or CDN/SSL misconfigurations.

To fix a redirect chain, map out all hops using a tool like this one, then update each intermediate redirect to point directly to the final destination URL. For example, if you have: oldsite.com/page → newsite.com/page → newsite.com/new-page → newsite.com/final-page, update the first redirect to go straight to newsite.com/final-page. Also audit your .htaccess, nginx config, CMS redirect plugins, and CDN settings to eliminate unnecessary intermediate redirects. After fixing, always re-test with this tool to confirm the chain is resolved.

Google has confirmed that 301 redirects pass most of the link equity to the destination URL, but not necessarily all of it. While the exact amount is not publicly disclosed, SEO experts estimate a small loss (roughly 1-10%) per redirect hop based on observed ranking changes. For a chain of multiple 301s, this loss compounds, meaning a 3-hop chain could lose noticeably more equity than a single redirect. Google's Gary Illyes stated in 2016 that 301s pass full PageRank, but more recent guidance suggests some dilution occurs. To be safe, always minimize redirect hops.