WebCare.

WordPress problem fix

WORDPRESS REDIRECT LOOP OR TOO MANY REDIRECTS?

The cause is usually small and the fix is quick once you trace the chain. We find the loop and stop it.

4 hour emergency response You only pay when it is fixed 150+ WordPress sites managed

The short answer

"ERR_TOO_MANY_REDIRECTS" or an endless WordPress redirect loop usually comes from one of a few narrow causes: a Cloudflare SSL setting fighting your site, a wrong site address in the database, or a redirect plugin with rules that point back at each other. It looks alarming but the cause is small and the fix is quick once you trace the chain.

Is this your situation?

If any of these match, you are on the right page.

Browser says too many redirects

Page reloads forever and never lands

Started after adding Cloudflare

Started after a bulk redirect import

What usually causes it

Is this a Cloudflare SSL problem?

Often. Cloudflare set to Flexible while your origin already serves HTTPS makes Cloudflare and WordPress argue about which version of the URL to load, and the browser loops. Full or Full strict matches the origin and stops it.

How does a wrong site address cause a loop?

If the WordPress site URL and home URL do not agree on https plus www or non-www, every request gets bounced to a different version of itself. The browser eventually gives up and shows too many redirects.

How do bad redirect rules create a loop?

Redirect plugins let you stack rules. If one rule sends A to B while another sends B back to A, or chains of 302s point at each other, the browser bounces between URLs forever.

How we fix it

The real method, in the order it works.

  1. 1

    Trace the chain with a redirect checker to see where it loops.

  2. 2

    Check Cloudflare SSL mode, switch Flexible to Full or Full strict when the origin has a valid certificate.

  3. 3

    Make the site address and home values match one version, https with your chosen www or non-www.

  4. 4

    Remove circular rules in the redirect plugin.

  5. 5

    Clear Cloudflare and site cache and retest.

Real fix, from our work

How this one actually went down

On one content heavy site I managed, a page got stuck in an endless redirect loop. When I dug in, the SEO team had been redirecting old content to new content, but they had stacked multiple 302 redirects inside the redirect plugin, and several pointed back at each other. So the page kept bouncing between URLs forever and never landed. I mapped each old URL straight to its final destination with a single permanent 301, stripped out the circular rules, and the loop was gone. The lesson: use one clean 301 per move, never chains of temporary 302s.

Screenshot illustrating Redirect loop
AJ

Written by Ali Yasin Jatoi

Founder of WebCare Studios. Ali has worked with WordPress for more than 10 years, including managing a fleet of 150+ sites with WP-CLI automation for updates, security cleanup, and malware removal. He has hands on experience across major hosts including Cloudways, A2 Hosting, Hostinger, and Bluehost.

Why owners pick WebCare

4 hour emergency response

Site down, hacked, or broken checkout gets a senior engineer within 4 hours. No ticket queues, no bots.

You only pay when it is fixed

Flat quote up front. If we cannot get you back online, you do not pay. Risk sits with us, not you.

Data safe approach

We work on a snapshot first and never touch your live database until the fix is verified safe.

150+ sites managed

We run a fleet of WordPress sites every day. The errors you are seeing are ones we have closed hundreds of times.

Common questions

What Cloudflare SSL mode should I use?+

Use Full or Full strict when your origin has a valid SSL certificate, which most modern hosts give you for free. Flexible is the usual cause of the loop.

Why did Cloudflare cause this?+

On Flexible, Cloudflare talks to your origin over HTTP while serving the visitor over HTTPS. WordPress then redirects to HTTPS, Cloudflare strips it, and the loop begins.

Can a redirect plugin loop my whole site?+

Yes. A single circular rule can take down every URL if it sits on a wildcard or a core path like the home page.

How do I prevent it after a migration?+

Map old URLs straight to their final destination with a single permanent 301. Avoid chains of 302s, and check SSL mode and site address right after the cutover.

Send my site for triage in 15 minutes

Two fields. Email and your URL. A senior WordPress engineer reads it within minutes and replies on email and WhatsApp with what is wrong and what we will do next.

Two fields. Senior engineer replies within 15 minutes during business hours.

Related fixes

WhatsApp Get my site fixed