Web & DNS

How to Trace a URL Redirect Chain and Fix Redirect Loops

Redirect chains and loops silently hurt SEO and page load speed. Here is how to trace every hop in a redirect path, identify the problem, and fix it.

How to Trace a URL Redirect Chain and Fix Redirect Loops

Every redirect adds latency. A chain of three redirects before a page loads wastes hundreds of milliseconds enough to measurably reduce conversion rates. More critically, each redirect hop in a chain passes less PageRank to the destination, eroding SEO value you have built over time. Trace any URL's full redirect path with the Redirect Checker.

Types of HTTP Redirects and Their SEO Impact

  • 301 Moved Permanently passes approximately 90–99% of link equity to the destination. Use this for permanent moves (HTTP to HTTPS, domain migrations, URL restructuring).
  • 302 Found (Temporary) passes significantly less link equity. Use only for genuinely temporary redirects such as maintenance pages.
  • 307 Temporary Redirect strict HTTP/1.1 equivalent of 302; preserves the request method.
  • 308 Permanent Redirect strict equivalent of 301 that preserves request method; rare in practice.
  • Meta Refresh / JavaScript Redirect not HTTP-level redirects; pass little to no link equity and are slower.

What Is a Redirect Chain?

A redirect chain occurs when URL A redirects to URL B, which redirects to URL C, and so on. Chains dilute link equity at each step and add cumulative latency. Google recommends a maximum of 5 hops in a chain, but best practice is to eliminate all multi-hop chains and go directly from A to C.

Common causes: domain migrations layered on top of HTTPS migrations, CMS URL changes without cleaning up old redirects, or third-party link shorteners in a chain with your existing redirects.

What Is a Redirect Loop?

A redirect loop occurs when A redirects to B and B redirects back to A (or via a longer cycle). Browsers detect this and display "ERR_TOO_MANY_REDIRECTS". Servers running the loop may do so indefinitely without browser intervention. The Redirect Checker detects loops and shows exactly where the cycle occurs.

Common Redirect Loop Causes and Fixes

  • HTTPS force redirect conflicting with CDN if your CDN handles HTTPS but your server also redirects HTTP to HTTPS, configure only one layer
  • www vs non-www conflict ensure your redirect and your canonical URL point in the same direction
  • WordPress home URL misconfiguration siteurl and home options in wp_options must both match the intended URL

Check your HTTP response headers with the HTTP Headers Checker to see exactly what your server is returning at each step.

Frequently Asked Questions

Do redirect chains hurt SEO?

Yes. Google's documentation confirms that redirect chains slow crawling, dilute PageRank, and can cause Googlebot to stop following the chain after a certain number of hops. Keeping all redirects as direct single-hop 301s is best practice.

How many redirects is too many?

Any chain longer than one hop is worth reviewing. More than three consecutive redirects will cause Googlebot to stop following and the destination page may not be indexed. The Moz guide on redirection and SEO covers the technical details.

Does a 301 redirect pass 100% of link equity?

No. Historically, Google passed roughly 85–99% of PageRank through a 301. In 2016, Google's Gary Illyes stated that 301 and 302 redirects now pass the same amount of PageRank, but consolidating redirects to direct 301s remains best practice to avoid compounding losses in chains.