You click your own site and Chrome answers with “This page isn’t working” and ERR_TOO_MANY_REDIRECTS. A wordpress redirect loop means your site never loads — and every minute costs you traffic and rankings.
The good news: it is almost always a settings disagreement, not a hacked site — two rules disagree about the “correct” address of a page, so the browser bounces between them. Fix the disagreement and the loop disappears, usually in under half an hour. Below are the diagnosis and seven proven fixes, in order, checked against official WordPress and Cloudflare documentation on 20 November 2026.
In This Guide
- What Is a WordPress Redirect Loop?
- Causes of a WordPress Redirect Loop
- Diagnose the Loop First
- Method 1: Cookies and Cache
- Method 2: Match the Site Addresses
- Method 3: Cloudflare SSL Mode
- Method 4: Reset .htaccess
- Method 5: Plugins and Theme
- Method 6: wp-admin-Only Loops
- Method 7: www and Trailing Slashes
- Preventing Future Loops
- Frequently Asked Questions
- Conclusion
What Is a WordPress Redirect Loop?
A wordpress redirect loop is page A sending the browser to page B, and page B sending it straight back. After about 20 hops, the browser gives up.
Redirects are normal — WordPress uses them for permalinks, login pages, and 301 redirects. A loop only starts when two rules point at each other.
The loop can hit your whole site, only your homepage, or only wp-admin — where it hits is your best clue to the cause. Googlebot hits the same wall, so pages can drop from search results.
What Causes a WordPress Redirect Loop?
Almost every wordpress redirect loop traces to one of six causes — the table matches each to its symptom and fix.
| Cause | Typical symptom | Fix |
|---|---|---|
| Site Address mismatch | After a URL edit or migration | Method 2: match both URLs |
| Cloudflare Flexible SSL | Behind Cloudflare; same HTTPS URL repeats | Method 3: switch to Full (strict) |
| Conflicting .htaccess rules | After a .htaccess edit | Method 4: reset .htaccess |
| Plugin conflict | After a plugin install or update | Method 5: deactivate plugins |
| HTTPS unseen behind a proxy | Only wp-admin loops | Method 6: X-Forwarded-Proto check |
| www vs non-www fight | www and non-www take turns | Method 7: one canonical rule |
| Stale cookies or cache | Only for you, or only logged in | Method 1: clear cookies, purge caches |
In every row, two layers disagree — HTTP or HTTPS, www or no www — usually right after a change: an SSL certificate, a Cloudflare setup, a migration, a new plugin, or a URL edit.
Diagnose the Loop Before You Change Anything
Spend five minutes finding which addresses take turns, so you fix the right layer.
First, test the scope: open the failing page in a private window. If it loads, the problem is your browser’s cookies or cache — go to Method 1. Then try /wp-login.php and /wp-admin/; if only the admin area loops, skip to Method 6.
Next, trace the chain — in a terminal, run this with your own domain:
curl -sIL --max-redirs 10 https://example.com/ | grep -iE '^(HTTP|location)'
Same HTTPS address repeating? The server keeps redirecting a request already on HTTPS — a classic Flexible or proxy problem. www and non-www taking turns? The fight is over the hostname. An X-Redirect-By header naming a plugin? That plugin is sending the redirect. No terminal? A free checker such as httpstatus.io shows the chain.
Finally, back up first: Methods 2, 3, and 4 edit live settings and server files. Our WordPress backup guide shows how.

Method 1: Clear Your Browser Cookies and Cache
Start here — it costs nothing. Stale login cookies can trigger a wordpress redirect loop on wp-admin and wp-login.php, even when the site is fine for everyone else.
Clear cookies for your domain only — in Chrome: Settings > Privacy and security > Cookies > “See all site data”, then search for your domain and delete its entries; in Firefox: Settings > Privacy and Security > “Manage Data”. Then hard-refresh: Ctrl + F5 on Windows, or Cmd + Shift + R on Mac.
If the loop is gone, you are done. If it persists in a private window and on another device, it is server-side — move on. Also purge your caching layers, since a cached redirect can outlive its fix: clear your caching plugin, purge your CDN cache, and clear server-side cache.
Method 2: Make Your WordPress Address and Site Address Match
This is the most common cause of a wordpress redirect loop. WordPress stores two URLs: the WordPress Address, where core files live (siteurl), and the Site Address, the address visitors type (home). WordPress redirects visitors toward the Site Address, so if they disagree — HTTP vs HTTPS, or www vs no www — the browser bounces.
If you can log in, go to Settings > General: both fields must match exactly — same protocol (https://), same www choice, no trailing slash.
If the loop locks you out of wp-admin, set both values in wp-config.php: connect over FTP or your host’s file manager, download a copy first, and add these two lines above the comment “That’s all, stop editing!”:
define( 'WP_HOME', 'https://example.com' ); define( 'WP_SITEURL', 'https://example.com' );
Use your real domain and the exact www/HTTPS version visitors should use. These lines override the database without changing it — the site comes back, and you can fix the database later.
Warning: while these lines exist, the Settings > General fields turn grey. Once back in, update home and siteurl in the database (WP-CLI or phpMyAdmin), then remove the lines.
Method 3: Fix Cloudflare SSL Mode (Flexible vs Full Strict)
If your site sits behind Cloudflare, this fixes the single most common wordpress redirect loop on proxied sites. In Flexible mode, visitors connect to Cloudflare over HTTPS, but Cloudflare connects to your origin over plain HTTP — so your server redirects to HTTPS, Cloudflare passes it on, and the loop spins forever.
The fix: in the Cloudflare dashboard, go to SSL/TLS > Overview and set the mode to Full (strict) — Cloudflare then talks to your origin over HTTPS and verifies its certificate.
Full (strict) needs a valid certificate on your origin — most hosts provide a free Let’s Encrypt certificate, or you can generate a free Cloudflare Origin CA certificate. Cloudflare recommends Full or Full (strict) wherever possible.
While there, check for duplicate redirects in Redirect Rules or old Page Rules — if Cloudflare and your server both redirect HTTP to HTTPS, keep one. Check Always Use HTTPS is on, purge the cache, wait a minute, and test in a private window. Use Full (without strict) only as a temporary fallback.

Method 4: Reset Your .htaccess File to WordPress Defaults
If the URLs are correct and Cloudflare is set right, the next suspect is .htaccess, the hidden file in your site root controlling rewrites and redirects on Apache and LiteSpeed. A corrupted file, or two contradicting rules, can create a wordpress redirect loop.
Follow this order: back up, rename, test, regenerate. Find .htaccess in your site root over FTP or your host’s file manager — it is hidden, so enable “show hidden files” if needed. Download a copy, then rename the live file to .htaccess.bak.
Test your site: loop gone, .htaccess was the culprit; loop stays, rename it back and move to Method 5. If renaming fixed it, regenerate a clean file under Settings > Permalinks — just click Save Changes.
If you cannot log in, create a new .htaccess and paste in the default WordPress rules, verified against official documentation:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Re-add custom rules one at a time, testing after each, outside the # BEGIN WordPress and # END WordPress markers (WordPress overwrites them on regeneration). Note: Nginx does not use .htaccess — its rules live in the server block, for your host to review.
Method 5: Deactivate Plugins and Test Your Theme
A plugin can inject its own redirect — caching, SSL, redirect-manager, security, and multilingual plugins are the usual suspects. When one disagrees with WordPress or the server, you get a wordpress redirect loop.
Deactivate all plugins at once, then reactivate one by one. In wp-admin: Plugins, select all, Deactivate. If locked out, rename plugins to plugins-disabled inside wp-content over FTP, and test.
If the loop disappears with plugins off, rename the folder back and reactivate one at a time, testing after each. When the loop returns, the last plugin activated is the culprit — leave it off and check its redirect or SSL settings.
If plugins are innocent, test the theme the same way: rename your active theme’s folder inside wp-content/themes/ over FTP, and WordPress falls back to a default theme. If the loop clears, your theme — or a redirect rule inside it — is the cause. Also review security: a redirect to a strange domain is not a loop at all — our WordPress security checklist covers how to tell.
Method 6: Fix a WordPress Redirect Loop That Only Hits wp-admin
A loop hitting only wp-admin and wp-login.php has its own short list of causes.
First, clear your login cookies (Method 1): they are set for one exact address, so a mismatch can bounce you back to the login page forever.
Second, check FORCE_SSL_ADMIN, which forces the admin area onto HTTPS. If your server or proxy does not tell WordPress the request is already secure, WordPress keeps redirecting to HTTPS. Behind a proxy or CDN, add this block to wp-config.php above the “stop editing” line:
if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' === $_SERVER['HTTP_X_FORWARDED_PROTO'] ) {
$_SERVER['HTTPS'] = 'on';
}
This tells WordPress to trust the X-Forwarded-Proto header your proxy sends. Cloudflare sends it, as do most reverse proxies and load balancers.
Third, check for a security or login plugin redirecting after login — a “force login” plugin, login-page customizer, or brute-force protector can redirect the admin area in a circle. Deactivate them (Method 5) and test again.
Method 7: Fix www vs Non-www and Trailing-Slash Redirects
The last common cause of a wordpress redirect loop is a fight over the canonical address, showing www and non-www taking turns in the chain you traced.
Pick one canonical version and make every layer agree on it — most sites use non-www HTTPS (https://example.com), but either choice works.
Check each layer once: Settings > General must show your chosen version in both URL fields (Method 2); in Cloudflare or your host’s panel, keep only one www rule; in .htaccess, keep only one force-HTTPS and one www rule. If a plugin also manages redirects, use either the plugin or the server rules — never both.
Trailing slashes cause the same fight in miniature: WordPress expects a trailing slash on archive and category URLs, so a rule stripping them loops against its own redirect — remove it.
After a migration, check for the old domain left in the database — our guide to migrate a WordPress site to a new host covers the search-and-replace step. When every layer agrees, the chain ends after one redirect, then a 200 response.
How to Prevent a WordPress Redirect Loop in the Future
Fixing a wordpress redirect loop is half the job: change one layer at a time and test after each change.
Test big changes on a staging site first — SSL changes, Cloudflare setup, migrations, and new redirect plugins are exactly the changes that cause loops. Our staging site guide shows how.
Keep a short change log (date, change, location) — when a wordpress redirect loop appears, it tells you in seconds which change to undo.
Audit your redirect rules twice a year and delete duplicates — one canonical redirect per job prevents loops. Keep your origin certificate valid and Cloudflare on Full (strict): an expired certificate can push an admin back to Flexible mode.
A loop is not a 404 or a 500 error — see our fix WordPress 404 errors and fix WordPress 500 internal server error guides.
Frequently Asked Questions
What does ERR_TOO_MANY_REDIRECTS mean in WordPress?
The browser followed redirects that never reached a finished page: page A sent it to page B, page B sent it back, and after about 20 hops it gave up — almost always because two settings disagree about the site’s real address.
How do I fix a wordpress redirect loop if I cannot log in to wp-admin?
You do not need wp-admin: set the site URLs in wp-config.php (Method 2), reset .htaccess over FTP (Method 4), and deactivate plugins by renaming wp-content/plugins (Method 5).
Is Cloudflare Flexible SSL the cause of my redirect loop?
Very often, yes. In Flexible mode Cloudflare talks to your origin over plain HTTP, so your origin redirects to HTTPS and the loop spins. Switch to Full (strict), confirm the certificate, and purge the cache.
How long does it take to fix a WordPress redirect loop?
Most take 10 to 30 minutes once you know the cause — diagnosis is the slow part, so trace the chain first. If all seven methods fail, ask your host to check the server-level redirects.
Can a plugin cause a redirect loop?
Yes. Caching, SSL, redirect-manager, security, and multilingual plugins can add rules that clash with WordPress or the server. Deactivate them all, then reactivate one by one — the last one that brings the loop back is the culprit.
Will a redirect loop hurt my SEO?
Yes, if it stays up: Googlebot cannot crawl a site that never returns a page, so rankings can drop. It is reversible — fix it the same day and rankings normally recover after recrawling.
Conclusion
A wordpress redirect loop looks alarming — your whole site replaced by a browser error — but it is one of the most fixable problems in WordPress. Resolve it in order: clear cookies, match the site URLs, set Cloudflare to Full (strict), reset .htaccess, test plugins and theme, fix the wp-admin case, and settle www versus non-www.
Test after each method, and stop at the first fix that clears the loop — most sites are back within half an hour. Then lock it in: one canonical address everywhere, one redirect rule per job, and a staging site for the next big change.
BadilHost Verdict
A wordpress redirect loop is a settings disagreement, not a broken site. Usually the fix is one of three things: matching site URLs in wp-config.php, switching Cloudflare from Flexible to Full (strict), or a clean default .htaccess file. Diagnose first, change one layer at a time — your site will be back within the hour.
No prices appear in this guide — every fix uses free WordPress settings, free Cloudflare SSL modes, and free Let’s Encrypt certificates. Verified 20 November 2026. Sources: WordPress: Changing the Site URL and Cloudflare: SSL/TLS encryption modes.