Fix ‘Too Many Redirects’ Error in WordPress: Complete Guide (2025)

If you’ve ever tried to open your WordPress site and got hit with a message like “ERR_TOO_MANY_REDIRECTS” or “This page isn’t redirecting properly”, you’re not alone. It’s one of the more frustrating errors because it often locks you out of both the front end and back end of your site. Need immediate help fixing your WordPress redirects? Get emergency WordPress support here.

In this guide, you’ll find:

• What exactly the “Too Many Redirects” error means

• Why it happens (common causes)

• Step‑by‑step fixes (from easiest to advanced)

• Tips to prevent it from happening again

Let’s dive in.

What Does “Too Many Redirects” Mean?

When a browser requests a URL, the server may respond with a redirect (e.g. “go to HTTPS version” or “go to www version”). But in some misconfigurations, two or more redirects end up pointing back and forth — creating an infinite loop. The browser detects this loop and stops, showing the “Too Many Redirects” error instead.

In short: your site is sending visitors into a redirect maze.

Variations of the Error You May See

Depending on browser or context, you might see:

• ERR_TOO_MANY_REDIRECTS

• The page isn’t redirecting properly

• “Too many redirects occurred trying to open”

• “This page isn’t working – redirected you too many times”

All point to the same underlying problem: a redirect loop.

Common Causes of Redirect Loops in WordPress

Understanding what usually triggers the issue helps you diagnose faster. Here are the most frequent culprits:

How to Fix “Too Many Redirects” in WordPress – Step by Step

Below is a structured approach. Try in order — often earlier steps solve it. Before making changes, always back up your site (files + database).

1. Clear browser cache, cookies & force refresh

Sometimes the loop is being cached locally.

• Do a hard refresh (e.g. Ctrl+F5 on Windows or Cmd+Shift+R on Mac)

• Clear browser cookies & cache for your site

• Try in a private/incognito window

If the site works after this, it was a caching glitch.

2. Clear WordPress & server cache

If you’re using a cache plugin (WP Super Cache, W3 Total Cache, WP Rocket, etc.), purge all caches.

Also clear server-level caching (e.g. Varnish, NGINX, host-managed cache) and any CDN cache (e.g. Cloudflare).

Then test again.

3. Check WordPress Address (URL) and Site Address (URL)

Go to Settings → General in your WordPress admin (if accessible). Ensure both WordPress Address (URL) and Site Address (URL) are exactly the same, and they match your real domain (with or without “www”, and with “https” if SSL is used).

If you can’t access the admin panel due to the error, set this manually:

1. Connect via FTP / file manager.

2. Open wp-config.php

3. Add lines (replace with your correct domain):

   define('WP_HOME','https://yourdomain.com');
define('WP_SITEURL','https://yourdomain.com');


4. Save and test

This forces WordPress to use that URL and can prevent mismatches. SSL / HTTPS misconfiguration — If HTTPS is forced from multiple layers (server, plugin, CDN), you may get conflicting rules. This can create redirect loops when the server and WordPress keep bouncing users between HTTP and HTTPS. Learn how to move WordPress to HTTPS without breaking your site, and ensure your HTTPS setup is solid.

4. Temporarily disable plugins

Since plugin conflicts are a common cause, disable all plugins to test:

• Via Admin (if accessible): go to Plugins → deactivate all

• Via FTP / file manager (if admin is unreachable): rename wp-content/plugins to e.g. plugins_disabled

Via FTP / file manager (if admin is unreachable): rename wp-content/plugins to e.g. plugins_disabled. Learn how to disable WordPress plugins without admin access

Check your site. If the error disappears, a plugin was responsible.

Then reactivate plugins one by one (or in small batches), testing after each, until the error reappears. That identifies the culprit.

Common suspects: SSL plugins, redirect plugins, caching plugins, security plugins.

Once found, either reconfigure or replace that plugin.

5. Switch to a default theme

If plugins are not causing the issue, try the theme:

• In WordPress admin, under Appearance → Themes, activate a default theme (e.g. Twenty Twenty‑Four)

• If you can’t access admin, rename your active theme folder via FTP, forcing WP to fall back to a default theme. If you can’t access admin, rename your active theme folder via FTP, forcing WP to fall back to a default theme. Learn how to safely change your WordPress theme via database if you’re completely locked out: how to safely change your WordPress theme via database.

If the redirect error disappears, your theme has custom redirect logic that’s misbehaving.

6. Reset (regenerate) .htaccess file

One of the strongest fixes is to reset your .htaccess file to WordPress defaults. But take care — always back it up first.

1. Use FTP or file manager to find .htaccess in your site root

2. Download a copy (backup)

3. Delete (or rename) the existing .htaccess

4. In WordPress admin → Settings → Permalinks, click Save Changes (you don’t need to change anything). This will regenerate .htaccess with default rules.

5. Test your site again

Default .htaccess for WordPress looks like this:

If your original .htaccess had custom redirect rules, you’ll need to carefully re-add them (if needed) one by one and test to avoid conflicts.

7. Check server / hosting-level redirects & SSL settings

Sometimes the redirect is not coming from WordPress or .htaccess at all, but from your web host or server configuration.

• In hosting control panel (e.g. cPanel, Plesk), check any “redirects” or domain forwarding settings — disable conflicting ones

• Some hosts force HTTPS automatically; if you also force HTTPS from WordPress or plugin, that may loop

• If your server uses Nginx instead of Apache, there’s no .htaccess. Redirect rules live in server config (e.g. nginx.conf)

• If using a CDN (e.g. Cloudflare), check its SSL / redirect settings:

  • Cloudflare’s “Always Use HTTPS” or “Automatic HTTPS Rewrites” may clash with WordPress rules

  • If using Cloudflare, ensure SSL mode is set correctly (often “Full” or “Full (strict)” rather than “Flexible”)

After changes, clear the CDN and server cache and test again.

8. Enable debugging & inspect logs

If you’re unsure how to safely enable and use debug mode, see how to enable WordPress debug mode to find errors. If the problem persists and you can’t figure out the loop, enabling debugging may help:

In wp-config.php, add:

Then examine wp-content/debug.log for clues. Look for messages about redirects, plugin functions, or URL mismatch.

You may also use tools such as redirect checker or httpstatus.io to analyze the redirect chain and see where it loops.

9. Contact your hosting provider

If all else fails, a hidden server configuration (firewall rules, load balancer, proxy) may be causing the loop. Your hosting support can investigate server logs and configurations.

Preventive Measures (Don’t Let This Happen Again)

Once your site is up and running again, here are best practices to avoid redirect loops in future:

1. Keep URL settings consistent
   Stick to one canonical version (e.g. https://www.domain.com) throughout WordPress, .htaccess, plugin settings, and server.

2. Avoid multiple redirect sources
   Don’t force HTTPS in multiple layers. Choose one mechanism (server, plugin, CDN).

3. Use redirect plugins carefully
   If using a redirect plugin, keep your redirect rules simple, avoid redirecting core pages (home, login), and avoid chains (A → B → C).

4. Test on staging before applying to live
   Always test changes (SSL, redirects, new plugins) on a staging or development site first.

5. Clear caches when making redirect / URL changes
   After any URL change or redirect setup or plugin activation, clear all levels of cache (WP plugin, server, CDN, browser).

6. Monitor and audit your redirects
   Use tools like Redirect Checker, Screaming Frog, or httpstatus.io to monitor redirect chains and catch looping setups.

7. Keep plugins, themes, and WordPress updated
   Outdated or poorly coded plugins or themes are more likely to introduce redirect mishaps.

FAQs 

Q1: What does “Too Many Redirects” error mean in WordPress?
A: This error occurs when your website enters a redirect loop, usually caused by misconfigured URLs, HTTPS settings, plugin conflicts, or caching issues. The browser stops the loop and shows the “Too Many Redirects” message.

Q2: How can I fix “Too Many Redirects” in WordPress?
A: You can fix it by following these steps:

1. Clear your browser cache and cookies

2. Clear WordPress, server, and CDN caches

3. Verify WordPress Address (URL) and Site Address (URL)

4. Temporarily disable plugins to find conflicts

5. Switch to a default theme if needed

6. Reset the .htaccess file

7. Check server-level redirects and SSL settings

8. Enable debugging to inspect logs

9. Contact your hosting provider if the issue persists

Q3: Can a plugin cause redirect loops in WordPress?
A: Yes. Plugins like SSL tools, redirection plugins, caching plugins, and security plugins can add conflicting redirects. Deactivating them temporarily helps identify the culprit.

Q4: How do I fix redirects if I cannot access the WordPress admin?
A: You can disable plugins or switch themes manually via FTP, File Manager, or database. There are guides available for safely performing these actions without admin access.

Q5: How can I prevent “Too Many Redirects” errors in the future?
A: To prevent this error:

• Keep URL settings consistent (HTTP/HTTPS, www/non-www)

• Avoid multiple redirect sources

• Use redirect plugins carefully

• Test changes on staging sites first

• Clear caches after any redirect or URL changes

• Regularly monitor redirect chains