Redirect Loops

A redirect loop happens when a URL redirects to another URL that eventually redirects back to the first, so the browser goes round in circles and the page never loads. Browsers stop after a set number of hops and show an error such as too many redirects.

Written by Paul Hoda, SEO consultant since 2005. Last updated 8 November 2026.

How redirect loops happen

The simplest loop is page A redirecting to page B while page B redirects to page A. Longer loops pass through several URLs before returning to the start. Common causes include:

  • Conflicting HTTPS rules, for example the server forcing HTTPS while a CDN or proxy talks to the server over HTTP, which triggers the HTTPS redirect again and again.
  • Clashing www and non-www rules set in different places, such as the server config and the CMS settings.
  • Trailing slash rules that add a slash in one layer and remove it in another.
  • Redirect plugins with rules that undo each other after a website migration.
  • Login or cookie checks that keep sending users back to the same page.
  • A site address in the CMS that does not match the real domain.

Why redirect loops matter for SEO

A page stuck in a loop cannot be loaded by visitors or by Googlebot. Google reports these as redirect errors in Search Console, and the affected URLs cannot be indexed. If an important page or a whole site is caught in a loop, it can quickly lose visibility. Loops also waste crawling effort and any links pointing to the looping URLs deliver no value.

How to find redirect loops

  1. Check the Page indexing report in Google Search Console for the Redirect error reason.
  2. Crawl the site with a tool such as Screaming Frog, which flags redirect loops and chains.
  3. Test suspicious URLs with a redirect checker or browser developer tools to see every hop.
  4. Try each variation of your homepage: http and https, with and without www, with and without a trailing slash.

How to fix them

  1. Map out every hop in the loop and identify which rule creates each one.
  2. Decide on one preferred version of each URL: protocol, hostname and slash style.
  3. Keep redirect rules in as few places as possible, and remove duplicates between the server, CDN and CMS.
  4. If using a CDN, set its SSL mode so it connects to your origin over HTTPS when the origin forces HTTPS.
  5. Point each old URL straight to its final destination with a single 301 redirect.
  6. Clear caches, retest and request reindexing for key pages.

Loops versus chains

A loop never ends. Redirect chains do end, but only after several hops, which slows pages and crawling. Both come from untidy redirect rules, so audit them together.

Key Takeaways

  • A redirect loop sends a URL round in circles so the page never loads.
  • Conflicting HTTPS, www and trailing slash rules are the usual causes.
  • Looping URLs cannot be crawled or indexed by Google.
  • Search Console and site crawlers both flag redirect errors.
  • Keep redirect rules in one place and point each URL straight to its final destination.

Related Terms

Curious how this applies to your website? Request a free SEO check-up, or keep learning in the SEO Encyclopedia.