How many redirects in a chain is too many?

The ideal chain length is zero or one. Two redirects is tolerable in specific scenarios (HTTP to HTTPS plus path change). Three or more hops should always be investigated and resolved. Each redirect adds a full HTTP round-trip (typically 50-200ms depending on geography), wastes bandwidth, may drop cookies or tracking parameters, and confuses search engine crawlers. Browsers limit redirect chains to around 20 hops before showing ERR_TOO_MANY_REDIRECTS, but performance degradation is noticeable at just 3 hops.

What is the most common cause of redirect loops in production?

The most common cause is conflicting redirect rules between layers. A classic example: the application enforces HTTPS (redirects HTTP to HTTPS), but a load balancer terminates TLS and forwards requests as HTTP. The application sees HTTP, redirects to HTTPS, the load balancer strips TLS and forwards HTTP again, creating an infinite loop. Fix this by checking the X-Forwarded-Proto header instead of the request protocol, or configure the redirect at only one layer.

How do I detect redirect chains introduced by a deployment?

Run automated post-deployment checks that follow redirects for all critical URLs and report chain length. Use curl -sL -o /dev/null -w '%{num_redirects}' for each URL. Fail the deployment pipeline if any URL exceeds a maximum chain length (e.g., 2). Also maintain a redirect inventory file in version control and run a CI check that detects if any redirect target is also a redirect source, which indicates a chain.

Do redirect chains affect SEO rankings?

Yes. Google has stated that while it follows redirect chains, each hop may dilute some PageRank (link equity). A single 301 redirect passes nearly all link equity, but chains of 3+ redirects may result in noticeable ranking loss. Additionally, Googlebot has a crawl budget per site, and wasting it on redirect chains means fewer real pages get crawled. For SEO-critical pages, always ensure a direct single-hop redirect from the old URL to the final canonical URL.

When should I use 301 vs 302 redirects in a chain?

Use 301 (Moved Permanently) when the old URL will never be used again. Search engines transfer link equity to the new URL and eventually stop crawling the old one. Use 302 (Found / Temporary) when the redirect is temporary, such as during A/B tests or campaign landing pages. In a chain, mixing 301 and 302 causes confusion: if the first hop is 302 (temporary) but the second is 301 (permanent), search engines may not consolidate the URLs correctly. Audit chains to ensure all hops use the appropriate status code.

Tracking Redirect Chains for Configuration Issues