Skip to content
← Back to site down

Why do you get a redirect loop?

A redirect loop means the request is trapped between competing URL or SSL decisions — for example HTTP forcing HTTPS in multiple places, www vs non-www conflicts, or Cloudflare/WAF rules rewriting the request repeatedly. This often starts after an SSL change, Cloudflare setup, a migration, switching hosts, enabling a cache plugin, or updating rules in .htaccess/Nginx. This page is for urgent incidents where users can’t access the site (or wp-admin), and enquiries or revenue are at risk. We treat it as a controlled rescue: isolate the redirect chain, remove the conflict, and verify stable access across key journeys.

Process

How We Fix a Redirect Loop / Too Many Redirects

A controlled recovery process (no trial-and-error).


  • Diagnosis: We trace the full redirect chain (browser + server + Cloudflare) to see exactly where it loops (http/https, www/non-www, trailing slash, cookie rules, cache or WAF rules).

  • Stabilisation: We remove the conflicting rule(s) and keep one source of truth for URL + SSL (WordPress settings, server rules, Cloudflare settings). We apply the minimum safe change to stop the loop without breaking logins, admin, or checkout.

  • Verification: We confirm the site loads consistently across key routes (home, key landing pages, wp-admin, login, checkout where relevant) on fresh + cached sessions, and across HTTP headers where needed.

Isometric 3D illustration showing the process of diagnosing, fixing, and verifying a WordPress redirect loop to restore stable site access.

Common causes

Most Common Causes of Redirect Loops on WordPress

What triggers endless redirects (and what we check first).


  • HTTP → HTTPS forced in multiple places: WordPress settings, Cloudflare settings, and server rules all try to redirect, creating a loop.

  • www vs non-www mismatch: the site alternates between www and non-www due to inconsistent canonical rules across WordPress, DNS, and server config.

  • Cloudflare SSL mode mismatch: Flexible SSL or incorrect origin SSL settings can cause repeated redirects between Cloudflare and the server.

  • Cache plugin or edge cache behaviour: cached redirects, cookie-based redirect rules, or stale cache at Cloudflare/CDN level can keep the loop alive.

  • Security/WAF rules or plugins: firewall rules, geo rules, or security plugins may redirect repeatedly (login protection, country blocks, challenge pages).

  • Trailing slash / path rewrite conflicts: Nginx/.htaccess rewrites + WordPress permalink rules fight each other on specific routes.

Isometric 3D illustration showing multiple configuration conflicts causing a WordPress redirect loop, including SSL, domain, cache, and security rules.
With redirect loops, the priority is one source of truth for URLs and SSL — then careful verification across cached and non-cached sessions.

How WPAssistant Works: Rescue Principles

Isometric 3D illustration of a magnifying glass identifying a bug in a code document, with a log file beside it, representing root-cause diagnosis and technical troubleshooting

Root-cause diagnosis

We map the redirect chain and identify the exact rule or layer creating the loop.

isometric 3d illustration of a control panel with a single slider being adjusted by a wrench and gear, shield icon representing safety, and a small before and after comparison card, symbolising minimal safe changes and controlled website fixes

Minimum safe change

We remove only the conflicting redirect source and keep a single canonical rule-set.

Isometric 3D illustration showing end-to-end checkout verification with a checklist, shopping cart, and email confirmation connected in a single workflow, representing complete purchase journey testing and order validation

Business-critical testing

We confirm stable access to key routes (wp-admin, login, checkout) across sessions and caches.

Isometric 3D illustration of a report document with simple charts, a speech bubble, and a handshake symbol connected together, representing clear communication, reporting, and handoff verification in a digital workflow.

Clear handover

You get a short summary of what caused the loop, what changed, and what to avoid next time.

Redirect loop / Too many redirects: What We Fix

A redirect loop can block the whole site or only specific routes (login, wp-admin, checkout). Fixing it properly means identifying the exact redirect chain and removing the conflicting source — not stacking more rules on top.

Typical rescue outcomes

We stabilise the canonical URL (http/https and www/non-www), align WordPress URL settings with server rules, correct Cloudflare SSL/redirect behaviour, clear cached redirects where required, and confirm the site loads consistently. Where relevant, we verify login, wp-admin, and checkout/payment flows.

Related rescue pages (recommended)

Redirect issues often appear alongside wider outages or configuration changes:

Site Down (Incident Response) · HTTP 500 Internal Server Error · Rescue Packages & Pricing

No open-ended billing. Scope is agreed before work begins. If the issue is bigger than expected, you’ll know before any additional work is done.

 

  • Fast access restoration: stop the loop and make the site reachable again.
  • One source of truth: align WordPress, server and Cloudflare URL/SSL decisions.
  • Safe changes only: minimum fix required without collateral damage.
  • Cache verification: confirm behaviour on fresh + cached sessions.
  • Clear next steps: what caused it, what changed, and what to avoid next time.

Redirect loop FAQs: Quick Answers

Short answers to the most common questions when WordPress gets stuck in an endless redirect loop.
What does “Too Many Redirects” mean?

It means the browser is being redirected repeatedly and never reaches a final page. The loop is usually caused by conflicting http/https or www/non-www rules across WordPress, the server, and Cloudflare.

Can Cloudflare cause redirect loops?

Yes. SSL mode mismatches (e.g. Flexible), edge redirects, WAF rules, or cached redirects can create loops between Cloudflare and your origin server. We confirm the chain and correct the single conflicting source.

Why did this start after enabling SSL or changing settings?

Redirect loops commonly appear after enabling HTTPS, switching the WordPress Site URL, adding server redirects, or enabling cache/security rules. Multiple layers may be trying to enforce the same redirect.

Can you fix it if I can’t access wp-admin?

Yes. We can diagnose and correct the redirect chain from server/hosting access, and restore wp-admin access safely.

Will fixing redirects affect SEO or canonical URLs?

When done correctly, it improves consistency. We keep one canonical URL, avoid chains, and ensure the final destination is stable across caches and sessions.

For clear pricing and service options, visit our pricing page. All work is scoped in advance, with no open-ended billing. If you’re experiencing issues or need expert help, the contact form below is the fastest way to get started. Please include your website URL and a short description of the problem so we can advise on the best next step.

Need help now?

Start a WordPress Rescue

If your site is down, unstable, or something broke after an update, plugin change, or migration, tell us what’s happening. We’ll review the details and confirm the next steps before any work starts.

Include your website URL, what changed before the issue, and any error message or screenshot. That helps us move faster.

Start a WordPress rescue request