Key takeaways
- A practical guide to redirect loops: common causes (www/apex, http/https, trailing slash), how to diagnose quickly, and how to fix without creating chains
Table of Contents
Start with the map:
Related (cluster):
- Crawled - currently not indexed: what actually fixes it
- Discovered - currently not indexed: why it happens
- GSC redirect error: fastest fix checklist
- Browser-facing version: Too many redirects error (ERR_TOO_MANY_REDIRECTS)
What a redirect loop is
A redirect loop is when URL A redirects to URL B and URL B redirects back to URL A (or the chain cycles).
Common loop patterns:
- http ↔ https
- www ↔ apex
- trailing slash ↔ no slash
- locale redirects that depend on cookies
The 10-minute diagnosis
- Test the URL with a clean request (no cookies).
- Note every hop until it fails.
- Check whether the destination differs by host, slash, or protocol.
Fix checklist
- Pick one canonical pattern (host + protocol + slash).
- Make sure the canonical URL returns 200 and does not redirect.
- Collapse the loop into a single deterministic redirect.
- Avoid chains (one hop is the goal).
Validation
- GSC URL Inspection: final URL should be stable.
- The page should render and return 200 for Googlebot.
Next in GSC statuses
Browse the cluster: GSC indexing statuses.
- GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)
- Page with redirect (Google Search Console): What it means and how to fix it
- GSC redirect error: The fastest fix checklist (chains, loops, and canonical URLs)
- Submitted URL marked 'noindex': The fastest fix checklist (GSC)
- Submitted URL blocked by robots.txt: What it means and what to do (GSC)
- robots.txt unreachable: Why it happens and how to fix it
Next in SEO & Search
Up next:
Page with redirect (Google Search Console): What it means and how to fix itA practical guide to the indexing status "Page with redirect": why it happens, when it's normal, and how to fix redirect chains so Google indexes the right URL.