Fix “too many redirects”
Paste the URL that fails. We follow every hop, find where it loops and tell you which setting causes it.
- Follows up to 10 hops
- Meta refresh, canonical and noindex
- See it as Googlebot
Why browsers say “too many redirects”
SSL mode loop
The proxy in front of the site (often Cloudflare's Flexible SSL mode) requests http while the server sends everyone to https. Set the proxy's SSL mode to Full (strict).
www and non-www loop
One rule sends visitors to www and another sends them back. Keep a single redirect to the host you want as canonical.
Redirect loop
The URL ends up back where it started, so browsers stop with “too many redirects”. Point it straight at the final page.
Too many redirects
The chain is longer than browsers and crawlers follow. Replace it with one redirect to the final page.
Find the loop first#
Run the failing URL through the checker above. It follows each hop the way a browser does and stops when a URL comes back, so you see exactly which two addresses send visitors to each other.
Fix it by cause#
Most loops come from two settings that each look right on their own:
- http ⇄ https: a proxy or CDN in front of the site talks http while the server insists on https. Change the proxy's SSL mode, not the server.
- www ⇄ non-www: one rule adds www and another removes it. Keep one redirect to the host you want.
- Two layers forcing the same thing: a hosting panel, .htaccess and a CMS plugin all redirecting. Keep one and remove the others.
- A CMS address setting that disagrees with the domain, such as WordPress set to http while the site serves https.
If no loop shows up here#
The checker sees what every visitor sees. When it reports no loop but your browser still fails, the loop depends on something only your browser sends, usually a cookie. Clear the site's cookies or open a private window.
FAQ