The too many redirects error is one of the few site problems that takes a page completely offline without a single line of broken code on it. The page exists, the server is running, and yet every visitor sees an error screen instead of your content. Behind every too many redirects error is almost always a redirect loop: two or more rules sending the browser back and forth until it gives up.
We get more urgent messages about this error than about almost any other redirect issue, mostly because it tends to appear right after a change that seemed harmless, like turning on SSL, installing a plugin or switching on a CDN. In most cases, the cause turns out to be one of a small number of settings.
Finding which setting is the real cause is the part that takes a little method.
Image 1 Prompt: Flat vector illustration in 16:9, 1200×675 pixels. A browser window in the center showing a simple error icon, with two curved arrows circling around it in an endless loop between two small server icons. Red and orange accents on a clean white background, modern tech blog style, minimal text, no logos.

What Is the Too Many Redirects Error?
When we explain this error to site owners, we start with what the browser is actually doing. A browser follows redirects one after another, and it keeps a count. If the count gets too high without reaching a real page, the browser stops and shows the too many redirects error instead of waiting forever. Most browsers stop after around 20 hops.
Each browser words the too many redirects error a little differently:
| Browser | What the visitor sees |
|---|---|
| Google Chrome | “This page isn’t working. The site redirected you too many times.” with the code ERR_TOO_MANY_REDIRECTS |
| Mozilla Firefox | “The page isn’t redirecting properly” |
| Safari | “Safari can’t open the page” with a note that too many redirects occurred |
| Microsoft Edge | “This page isn’t working right now” with ERR_TOO_MANY_REDIRECTS |
Whatever the wording, the meaning is the same. The server keeps answering with a redirect, and the redirects never lead to a page that returns content. ERR_TOO_MANY_REDIRECTS is simply Chrome’s name for that situation.
Redirect Loop vs Redirect Chain
People often mix these two up when they first look at redirect reports, and they need very different levels of urgency. A redirect chain is a series of hops that eventually reaches a working page. It is slow and messy, but the page loads. If that is what you are dealing with, our guide on what a redirect chain is covers how to shorten it.
A redirect loop never reaches a page at all. URL A points to URL B, and URL B points back to URL A, or the loop runs through three or four URLs before coming back to the start. The browser goes round and round until it hits its limit. That is why a loop always ends in the too many redirects error, while a chain usually does not. If your page loads, even slowly, you are looking at a chain, not this error.
What Causes a Redirect Loop?
On the sites we have fixed, the loop almost never comes from one bad rule on its own. It comes from two settings that are each correct in isolation but point in opposite directions. These are the causes of the too many redirects error we see most often, roughly in order of how common they are.
SSL settings that disagree between the CDN and the server
This is the classic cause of the too many redirects error on sites that use Cloudflare or a similar service. Cloudflare’s own guide to fixing ERR_TOO_MANY_REDIRECTS explains the problem: in Flexible mode, Cloudflare connects to your server over HTTP. If your server is set to force every HTTP request to HTTPS, it redirects Cloudflare’s request, Cloudflare sends it again over HTTP, and the loop never ends. The reverse also happens when Cloudflare is set to Full mode but the server redirects HTTPS back to HTTP.
WordPress URL settings that do not match
WordPress stores two addresses: the WordPress Address and the Site Address. If one uses https and the other uses http, or one uses www and the other does not, WordPress and the server can end up correcting each other endlessly. This is one of the most common reasons for a redirect loop WordPress owners run into after moving to HTTPS.
Two plugins or rules pulling in opposite directions
One plugin forces the www version of the domain. A hosting setting forces the version without www. Each one is doing its job, and together they create a perfect loop. The same thing happens with trailing slash rules, where one rule adds a slash and another removes it.
A redirect rule that points back to itself
When two pages swap URLs, or a page is moved and then moved back, it is easy to end up with A redirecting to B and B redirecting to A. Redirect plugins usually accept these rules without any warning, and the too many redirects error shows up only when someone visits one of the two pages.
A server behind a proxy or load balancer
When a load balancer handles HTTPS and passes requests to the server over plain HTTP, the server may think every request is insecure and redirect it to HTTPS, which arrives as HTTP again. The server needs to read a header from the proxy to know the original request was already secure. Without it, every page on the site can show the too many redirects error at once.
Old cookies and cached redirects
Sometimes the loop is only on your own device. A stale login cookie or a cached 301 from an old setup can keep your browser bouncing even after the server is fixed. This is why the too many redirects error sometimes shows for one person and not for anyone else.
How to Find the Loop With a Redirect Detector
Before changing anything, we always confirm exactly which URLs are in the loop. Guessing leads to changing the wrong setting and sometimes creating a second problem on top of the too many redirects error you started with.
Use an online redirect detector
The quickest way is a tool that follows each hop and reports what it finds. Our redirect detector traces the full path for a URL and flags loops, along with redirects that end at a dead or unreachable page. It also tests the http, https and www versions of your domain, which matters because many loops only affect one of those versions. Look at the list of hops and find the first URL that appears twice. The step just before it is where the loop closes.
Use curl with a hop limit
If you prefer the command line, this command follows redirects but stops after ten hops, instead of running until it errors out:
curl -sIL -max-redirs 10 https://example.com/
Read the “location” lines in the output from top to bottom. When the same addresses start repeating, you have found the loop and the URLs inside it.
Check in a private browser window
Open the page in a private or incognito window. If it loads there but not in your normal window, the server is probably fine and the problem is cookies or cache on your own device. If the too many redirects error appears in both, the loop is on the server or CDN.
Image 2 Prompt: Flat vector illustration in 16:9, 1200×675 pixels. A laptop screen showing a list of four URL rows connected by arrows, where the last arrow loops back to the first row and is highlighted with a red warning badge. A small magnifying glass rests over the loop. Blue and red accents on a white background, clean dashboard style, minimal text, no logos.

How to Fix the Too Many Redirects Error in 7 Easy Steps
These are the steps we follow in order whenever a client reports the too many redirects error. The early steps are quick and harmless, and they often solve the problem before you need to touch any server files. Test the page after each step, and stop as soon as it loads.
Step 1: Clear cookies and browser cache for the site
In Chrome, click the icon to the left of the address bar, open the site settings and delete the cookies and data for that domain. Then reload the page. If the too many redirects error disappears, the server was never the problem. If you run a site with logins, let your team know they may need to do the same.
Step 2: Clear your site, server and CDN cache
Caching plugins, server caches and CDNs can store a redirect and keep serving it after the cause is gone. Purge the cache in your caching plugin, in your hosting panel and in your CDN dashboard, then test again in a private window. A surprising number of cases of the too many redirects error end at this step, especially right after an SSL change.
Step 3: Check your SSL and HTTPS settings
If you use Cloudflare, open the SSL settings and look at the encryption mode. When your server already has an SSL certificate, choose Full or Full (strict) instead of Flexible. Also check that you are not forcing HTTPS in three places at once, such as Cloudflare, a plugin and the server. One place is enough. Our SSL checker confirms whether the certificate on your server is valid, which tells you whether Full mode is safe to use.
Step 4: Make the WordPress Address and Site Address match
In WordPress, go to Settings, then General, and make sure both addresses use exactly the same version of your domain, including https and www if you use them. If you cannot reach the dashboard because of the loop, set both values in the wp-config.php file instead. The official WordPress guide on changing the site URL covers this method. Add these lines above the line that says “That’s all, stop editing”:
define( ‘WP_HOME’, ‘https://www.example.com’ );
define( ‘WP_SITEURL’, ‘https://www.example.com’ );
If your site sits behind a load balancer or proxy that handles HTTPS, add this line too. It tells WordPress the original request was already secure:
if ( isset( $_SERVER[‘HTTP_X_FORWARDED_PROTO’] ) && $_SERVER[‘HTTP_X_FORWARDED_PROTO’] === ‘https’ ) { $_SERVER[‘HTTPS’] = ‘on’; }
Step 5: Turn off plugins to find the one causing the loop
Redirect plugins, SSL plugins, security plugins and caching plugins can all trigger a redirect loop. If you can reach the dashboard, deactivate them one at a time and test after each. If you cannot, connect through FTP or your host’s file manager, open the wp-content folder and rename the plugins folder to something like plugins_off. That turns every plugin off at once. If the site loads, rename the folder back and turn plugins on one by one until the error returns.
Step 6: Reset your .htaccess file
On Apache servers, conflicting rules in the .htaccess file are a frequent cause. Download a backup copy first, then replace the contents with the default WordPress rules below and test the site:
# 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
If the too many redirects error goes away with the default file, add your custom rules back one at a time from the backup until you find the one that closes the loop.
Step 7: Review your redirect rules for circular paths
Open your redirect plugin, Rank Math Redirections or your hosting panel’s redirect list. Search for the URLs your redirect detector showed in the loop. Look for any pair where A points to B and B points back to A, and for rules that send one domain version to another that sends it straight back. Delete or edit the rule that should not exist, save, and run the redirect check again. A fixed URL should show one redirect at most, followed by a 200 response.
Redirect Loop WordPress Fixes: A Quick Reference
Most of the WordPress loops we see fall into a few patterns. If you already know what changed on your site just before the too many redirects error started, this table points you to the fix faster.
| What changed just before the error | Likely cause | Where to fix it |
|---|---|---|
| Turned on Cloudflare or changed its SSL mode | Flexible SSL with HTTPS forced on the server | Cloudflare SSL settings |
| Installed an SSL or HTTPS plugin | Plugin and server both forcing HTTPS | Plugin settings or .htaccess |
| Changed the domain or moved to HTTPS | WordPress Address and Site Address mismatch | Settings, General or wp-config.php |
| Added a new redirect rule | Rule points back to its own source | Redirect plugin or Rank Math Redirections |
| Moved to a new host or load balancer | Server cannot see that requests are already HTTPS | wp-config.php proxy line |
| Nothing, and only you see the error | Old cookies or cached redirects | Browser cookies and cache |
When Only Some Visitors See the Too Many Redirects Error
A few times a year, a client tells us the site works for them but customers keep reporting the error. That pattern points to a loop that depends on something specific to the visitor, and it is one of the harder versions of the too many redirects error to track down.
Logged in users are a common example. A membership or security plugin may redirect logged in users to one URL and logged out users to another, and a misconfigured rule can loop only for one group. Location based redirects are another. A rule that sends visitors from one country to a regional page can loop if the regional page sends them back. Cached pages can also play a part, where one CDN location still holds an old redirect while others have the new one.
To test these cases, check the page while logged out in a private window, ask an affected visitor which country and device they are using, and purge the CDN cache fully rather than for a single URL.
Image 3 Prompt: Flat vector illustration in 16:9, 1200×675 pixels. A simple checklist on a clipboard with seven ticked boxes, next to a browser window that now shows a green check mark and a loaded web page. A small wrench and a shield icon sit beside the clipboard. Green and blue accents on a white background, friendly tech blog style, minimal text, no logos.

How to Stop a Redirect Loop From Coming Back
Once a site has had one too many redirects error, the chances of another are higher, because the conditions that created it are still there. A few habits keep the too many redirects error from returning.
Force HTTPS in one place only. Pick one layer, the CDN, the server or a plugin, and let it handle the HTTPS redirect. Turn the setting off everywhere else.
Keep page redirects in one tool. Whether it is Rank Math or a dedicated redirect plugin, one list of rules is far easier to check for circular paths than three lists spread across different tools.
Test on staging before big changes. SSL changes, domain moves and new plugins should be tried on a staging copy first. A loop on staging costs nothing.
Write down every change. Keep a short log of SSL changes, plugin installs and redirect rules with the date. When the too many redirects error appears, the log usually points straight at the change that caused it.
Run regular checks. A monthly full site audit flags redirect loops, long chains and broken pages together, which means a new loop gets caught before customers find it.
FAQs
What does ERR_TOO_MANY_REDIRECTS mean?
It is Chrome’s code for the too many redirects error. It means the browser followed a series of redirects that never reached a real page, which almost always points to a redirect loop.
Can clearing cookies fix the too many redirects error?
Sometimes. If the loop is caused by an old cookie or a cached redirect on your device, clearing them fixes it straight away. If the loop is on the server or CDN, clearing cookies will not help.
Why did the error start after I installed an SSL certificate?
Usually because HTTPS is now being forced in more than one place, or because your CDN is connecting over HTTP while the server forces HTTPS. Check your CDN SSL mode and remove duplicate HTTPS redirects.
How do I fix a redirect loop in WordPress without dashboard access?
Set the correct site address in wp-config.php, rename the plugins folder through FTP to turn all plugins off, and reset the .htaccess file to the default WordPress rules. Then test after each change.
Does a redirect loop hurt SEO?
Yes, if it lasts. Search engines cannot reach the page, which means it cannot be crawled or kept in the index. A loop fixed within hours rarely causes lasting damage, but one left for weeks can push pages out of search.
How can I check if my site has a redirect loop?
Run your URLs through a redirect detector. It follows every hop and flags any URL that sends visitors back to an address they already passed through.
Get Your Pages Out of the Loop
A too many redirects error feels serious because the page is fully offline, but the fix is rarely complicated once you know which two settings are fighting. Start by finding the exact URLs in the loop, change one setting at a time, and test after every step. Run your homepage and key pages through our free redirect loop checker to see exactly where the loop closes, then follow the steps that match what you find.