Redirect loop detected: what it is, why it matters, and how to fix it
This URL is part of a circular redirect chain where the final redirect points back to a URL already in the chain. The page is completely inaccessible to both users and search engines.
Where this fits: indexability in SEO
Why redirect loop detected hurts your rankings
A redirect loop results in a browser error (ERR_TOO_MANY_REDIRECTS) and makes the page completely unreachable. Search engines will drop the URL from their index after encountering the loop. Any link equity flowing to URLs in the loop is effectively lost.
This is a critical issue: it can remove pages from search results entirely or block them from being crawled at all. Treat it as an outage, not a backlog item — every day it persists is compounding lost visibility.
How to fix it
Trace the full redirect chain to identify where the loop occurs. Common causes include conflicting redirect rules (e.g., www-to-non-www and non-www-to-www simultaneously), CMS-level redirects conflicting with server-level redirects, or HTTP-to-HTTPS rules interacting with other redirects. Fix the conflicting rules so the chain terminates at a 200-status page.
# Common cause: conflicting .htaccess rules
# Rule 1 sends non-www to www
# Rule 2 sends www to non-www
# Fix: remove one of the conflicting rulesFrequently asked questions
What does "Redirect loop detected" mean?
This URL is part of a circular redirect chain where the final redirect points back to a URL already in the chain. The page is completely inaccessible to both users and search engines.
Why does redirect loop detected matter for SEO?
A redirect loop results in a browser error (ERR_TOO_MANY_REDIRECTS) and makes the page completely unreachable. Search engines will drop the URL from their index after encountering the loop. Any link equity flowing to URLs in the loop is effectively lost.
How do I fix redirect loop detected?
Trace the full redirect chain to identify where the loop occurs. Common causes include conflicting redirect rules (e.g., www-to-non-www and non-www-to-www simultaneously), CMS-level redirects conflicting with server-level redirects, or HTTP-to-HTTPS rules interacting with other redirects. Fix the conflicting rules so the chain terminates at a 200-status page.
How serious is this issue?
This is a critical issue: it can remove pages from search results entirely or block them from being crawled at all. Treat it as an outage, not a backlog item — every day it persists is compounding lost visibility. It belongs to the indexability family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects redirect loop detected on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by redirect loop detected, and hands you a ready-made fix task.
Check my site free