Redirect Loop Error on Your Site? Here’s How to Fix It

2. What a Redirect Loop Error Actually Is

Quick Answer: A redirect loop is when page A sends the browser to page B, and B sends it straight back to A — an endless circle. After about twenty hops the browser gives up and shows an error instead of your page. The two destinations point at each other.

Redirects are normal. A 301 or 302 tells the browser “that page has moved, go here instead,” and it usually works invisibly. A redirect loop is that mechanism gone wrong: the new address points back to the old one, so the browser bounces between them forever.

No browser follows redirects forever, so it stops after a set number of hops and shows an error. The wording changes by browser, which is why the same redirect loop error looks different on different devices:

• Chrome and Edge. “This page isn’t working — redirected you too many times,” with the code ERR_TOO_MANY_REDIRECTS.
• Firefox. “The page isn’t redirecting properly.”
• Safari. “Safari can’t open the page because too many redirects occurred.”
• Behind the scenes. The server keeps returning 301 or 302 responses that never resolve.

3. What Causes a Redirect Loop

Quick Answer: Most redirect loops come from an SSL or CDN setting fighting your server, or a WordPress URL that doesn’t match itself. Clashing .htaccess rules and circular plugin redirects make up the rest. Nearly all are a settings conflict, not a damaged site.

When ZenWeb traces a redirect loop, the cause is rarely a mystery. Here is how they broke down across the sites we fixed.

The top cause is worth a pause: a site behind Cloudflare’s “Flexible” SSL while the server already forces HTTPS sends the request back and forth forever — a pattern Cloudflare documents in its guide to the too-many-redirects error. A rushed redirect after moving a page can start a loop too, the same way it leaves broken links across your website.

4. When Redirect Loops Tend to Strike

Quick Answer: Redirect loops rarely appear out of nowhere. They usually follow a change — enabling Cloudflare, forcing HTTPS, migrating the site, or installing a plugin. Knowing what you changed last points straight at the cause.

A redirect loop almost always has a trigger. Match your error to your last change and you have your first suspect.

The first two triggers are both about HTTPS — no coincidence, since forcing secure connections in more than one place makes a loop easy to create. If the whole site went dark rather than one page, treat it like a website that is down and not loading and start with your last change.

5. How a Redirect Loop Hurts Your Business

Quick Answer: A redirect loop error takes the affected page fully offline, so it costs every visitor who lands on it. If it hits a home or landing page, you lose sales, search visibility, and ad spend on that URL — all at once.

A redirect loop is not a cosmetic glitch. While it stays live, the affected page is simply gone for visitors, and that leaks value several ways at once:

• Lost sales and enquiries. A shopper who hits the error can’t reach your product or form. Most won’t retry — they leave for a competitor.
• The page reads as down. If the loop hits key pages, visitors experience it exactly like a website that is down and not loading, and lost enquiries start piling up.
• Wasted ad spend. A paid click landing on a looping page converts nobody, and a broken destination can get campaigns flagged — the same trap covered in our guide on fixing disapproved Google Ads.
• Weaker search visibility. When Google’s crawler keeps hitting the loop, it can’t index the page, and a page it can’t reach can’t rank.

6. How to Fix a Redirect Loop Step by Step

Quick Answer: Work from the outside in: browser first, then WordPress URLs, then SSL and CDN settings, then .htaccess and plugins. Test in a private window after each change so you see the real result, not a cached loop.

Follow these in order and stop as soon as the page loads — most are solved in the first three steps.

1. Rule out your own browser. Open the site in incognito, or clear your cookies and cache. Stale cookies cause client-side loops; if it loads in incognito, the site was never the problem.
2. Check your WordPress URL settings. In Settings → General, confirm WordPress Address and Site Address match exactly — same www or non-www, both on https. A mismatch here is the classic loop.
3. Check your SSL and Cloudflare mode. If you use Cloudflare, set the SSL/TLS mode to Full (Strict), never Flexible, when your server already forces HTTPS. This clears the most common cause.
4. Reset your .htaccess file. In Settings → Permalinks, click Save Changes to regenerate a clean file, or remove any duplicate redirect rule you find.
5. Deactivate redirect and security plugins. Turn off plugins that handle redirects, SSL, or security, then switch them back on one by one until the loop reappears.
6. Trace the chain with a redirect checker. A free redirect-checker tool shows every hop, so you can see exactly where one page sends to another and back.
7. Clear every cache once more. Flush your site cache, CDN cache, and browser, so your fix isn’t hidden behind an old cached loop.

7. The Right Fix for Each Cause

Quick Answer: There is no single fix — it depends on which two rules are looping. An SSL mismatch needs Full (Strict) mode, a URL mismatch needs matching settings, and a clashing .htaccess or plugin rule needs the duplicate removed. Match the fix to the cause and each takes minutes.

Once you know the cause, this table gives you the matching fix.

Every fix shares one theme: each URL needs only one canonical rule. The moment two places both control a page’s destination, they can bounce the visitor between them.

8. How Long Fixing a Redirect Loop Takes

Quick Answer: A browser-only loop clears in minutes. A WordPress URL or SSL-mode fix takes 15 to 30 minutes. Server and post-migration loops take longer — but most SME sites are back within the hour.

Here is what the job looks like by scenario.

9. How to Stop Redirect Loops Coming Back

Quick Answer: Redirect loops come back through habits, not bad luck. Pick one canonical address, use Full (Strict) SSL, keep redirect rules in one place, and test in incognito after every change. Small routines keep loops from forming again.

Clearing the loop once is satisfying; the goal is not repeating the hunt. These habits do most of the work:

• Pick one canonical address. Choose www or non-www, plus https, and set it the same way in WordPress, your server, and your CDN. Mismatched versions are the root of most loops.
• Use Full (Strict) SSL. On Cloudflare, never leave the mode on Flexible when your server forces HTTPS — it is the single biggest cause of a redirect loop.
• Keep redirects in one place. Map them before you add, and don’t stack a plugin rule, an .htaccess rule, and a CDN rule for the same URL. Clean redirects also prevent broken links from building up across your site.
• Test in a private window after changes. Incognito ignores your cookies and cache, so you see the real result, not a stale one.

10. When to Get a Web Team to Fix It

Quick Answer: Handle it yourself when it’s a browser, URL, or SSL-mode fix. Call in a web team when the loop is server-level, when it appeared across many URLs after a migration, or when it keeps coming back — a sign of a deeper setup problem.

Clearing a simple redirect loop is a quick DIY job. Other times it points to something bigger. Bring in help when:

• The loop is server-level. Nginx rules, reverse proxies, and hosting-side redirects need someone comfortable at that layer, and often relate to a wider hosting problem that’s affecting your site.
• It appeared after a migration. Loops across many URLs need proper redirect mapping, not a page-by-page fix.
• It keeps coming back. A loop that returns after every change signals a fragile setup that needs fixing at the root.

ZenWeb diagnoses the loop, fixes it at the right layer, and hardens your redirect and SSL setup so it stays gone — part of our web design and care service, so your pages keep loading.

11. Conclusion

A redirect loop error feels like a wall, but it is one of the tidier website problems to solve. Every loop is two rules pointing at each other, and each has a clear fix: Full (Strict) SSL for a Cloudflare clash, matching addresses for a WordPress mismatch, one canonical rule for the rest. Rule out your browser first, then work in through your settings.

The lasting win is the habit, not the one-off fix. Keep one canonical address, one place for redirects, and an incognito test after every change, and the loop stops draining your leads and rankings. Do that, and visitors always land where you sent them.

12. Frequently Asked Questions

1. What does “ERR_TOO_MANY_REDIRECTS” mean?

It means your browser got stuck in a redirect loop. One page kept sending it to a second, and the second kept sending it back, so after about twenty hops the browser stopped and showed the error instead of a page. It is almost always a settings conflict — an SSL mode, a URL mismatch, or a clashing rule — not a damaged website.

2. How do I fix a redirect loop in WordPress?

Start with your browser: open the site in incognito or clear your cookies. If it still loops, check Settings → General and make sure WordPress Address and Site Address match, both on https. Then check your SSL or Cloudflare mode, reset your .htaccess from Settings → Permalinks, and deactivate redirect or security plugins one at a time until the loop clears.

3. Can Cloudflare cause a redirect loop?

Yes, and it is the most common cause we see. When Cloudflare’s SSL/TLS mode is set to Flexible but your server already forces HTTPS, the two keep redirecting the request back and forth. Changing the mode to Full (Strict), with a valid certificate on your server, ends the loop. Clear your cache afterwards so you don’t keep seeing the old error.

4. Why does my site loop only when I log in to wp-admin?

A login-only loop is usually a URL or cookie problem. If your WordPress Address and Site Address don’t match, or the site mixes http and https, the login cookie is set for one address and rejected on the other, bouncing you in a loop. Match both URLs on https and clear your cookies, and the admin login should hold.

5. How long does it take to fix a redirect loop error?

Most take under an hour. A browser cache or cookie cause clears in minutes, and the common WordPress URL or SSL-mode fixes take 15 to 30 minutes. Only server-level and post-migration loops take longer, because they need careful redirect mapping and often host access.