Blog

Redirect loop: How to find it and fix it (SEO + GSC)

0.97 min read/
/

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.

Subscribe
Get new essays via Substack or RSS. Start with the guided path if you are new.
Start with the main guide
GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)

A practical map of Google Search Console indexing statuses (Coverage): what each status means, the most common root causes (canonicals, duplicates, robots, redirects, soft 404s), and the fastest way to validate fixes.

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

Contents

Start with the map:

Related (cluster):

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

  1. Test the URL with a clean request (no cookies).
  2. Note every hop until it fails.
  3. Check whether the destination differs by host, slash, or protocol.

Fix checklist

  1. Pick one canonical pattern (host + protocol + slash).
  2. Make sure the canonical URL returns 200 and does not redirect.
  3. Collapse the loop into a single deterministic redirect.
  4. 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.

Tags

More reading