Redirect loop
redirect_loopShort answer
The URL redirects to a URL that eventually redirects back to it. Browsers show "too many redirects"; Googlebot records a redirect error and the page cannot be indexed. Almost always two rules fight — http↔https, www↔non-www, trailing slash on↔off. Make each URL lead straight to one final 200 page.
Why it matters
Nobody reaches the content: visitors see an error page, crawlers give up. If the looping URL had rankings, they fall within days. Loops usually appear right after a change in hosting, CDN or SSL settings, when the new layer adds a redirect that contradicts one already in the application.
How Glimana detects it
The crawler follows redirects and stops when a URL repeats in the chain; the rule fires with the final URL seen before the loop was detected.
How to fix it
Find which layer adds each redirect: CDN (Cloudflare "Always use HTTPS", "Automatic HTTPS rewrites"), web server (.htaccess, nginx), the application (WordPress site address, framework middleware). Keep the redirect in one layer and remove it from the others.
- The classic loop: Site Address is
http://while the host forces HTTPS, or the reverse. Set both addresses in Settings → General to the finalhttps://form. - Behind Cloudflare with SSL mode Flexible, WordPress sees HTTP and redirects to HTTPS forever. Set the SSL mode to Full (strict).
- Remove duplicate rules from
.htaccessleft by security plugins.
Loops come from URL redirects where A→B and B→A exist, or from a custom domain whose DNS still points at an old host that redirects back. Remove the circular entry or fix the DNS.
Log the full redirect chain in staging; curl -IL https://… shows every hop. Normalise scheme, host and slash in one rule.
How the fix is verified
Affected URLs are re-fetched; the task closes when each one ends at a 200 page.