The ERR_TOO_MANY_REDIRECTS error means the browser is being sent between URLs repeatedly and never reaches the requested WordPress page. The browser eventually stops the loop and displays a redirect error.
On WordPress websites, the most common causes are conflicting HTTP and HTTPS settings, incorrect WordPress URLs, overlapping redirect rules, caching, or a proxy configuration problem.
What Causes Too Many Redirects in WordPress?
A redirect loop often happens when one system sends visitors to one URL while another system sends them back. Common conflicts include:
- HTTP redirecting to HTTPS while another rule redirects back to HTTP
- www redirecting to non-www while another rule reverses it
- Incorrect WordPress Address or Site Address settings
- Duplicate redirects in WordPress, the server, and a CDN
- A caching plugin serving an outdated redirect
- Cloudflare or another proxy using the wrong SSL mode
- A plugin forcing a login, language, or canonical redirect
1. Test the URL in a Private Browser Window
Open the affected URL in a private or incognito window. If it works there, clear the cookies and cache for the domain in your normal browser.
If the error affects every browser and device, the loop is probably coming from the website, server, or CDN configuration.
2. Clear Every Cache Layer
Clear the caches you actually use:
- WordPress page cache
- Managed hosting cache
- Object cache such as Redis
- CDN or Cloudflare cache
- Browser cache and cookies
Clearing only the WordPress plugin cache may not remove a redirect stored at the host or CDN level.
3. Check the WordPress Address Settings
In WordPress, go to Settings, then General. Confirm that both addresses use the correct domain and protocol:
- WordPress Address URL
- Site Address URL
For most standard installations, these values should match exactly. A difference between http and https, or between www and non-www, can create a loop.
If the dashboard is unavailable, review WP_HOME and WP_SITEURL inside wp-config.php. The official WordPress wp-config.php documentation explains how these constants override the database values.
define( 'WP_HOME', 'https://example.com' );
define( 'WP_SITEURL', 'https://example.com' );Replace the example domain with the website’s correct canonical URL. Do not add these lines unless you understand why the existing values are wrong.
4. Check HTTPS and SSL Settings
Confirm that the website has a valid SSL certificate and that WordPress, the hosting account, and any CDN agree on how HTTPS is handled.
If Cloudflare or another reverse proxy is active, an incorrect SSL mode can cause the origin server and proxy to redirect requests back and forth. Avoid using a flexible SSL configuration when the origin server already forces HTTPS.
5. Disable Redirect and SSL Plugins
Temporarily deactivate plugins that manage:
- Redirects
- SSL or HTTPS
- Caching
- Security
- Language or country redirection
- Login URLs
If the dashboard is unavailable, rename the suspected plugin folder inside wp-content/plugins. Test the affected URL after disabling one likely source at a time.
6. Review Server Redirect Rules
Check the website’s .htaccess file on Apache servers or the server configuration on Nginx. Look for duplicate rules controlling HTTPS, www, domains, folders, or old URLs.
A redirect may also exist in cPanel, the hosting dashboard, a migration plugin, Rank Math, Redirection, or another SEO plugin. Keep each redirect in one intentional location whenever possible.
Create a backup before changing server configuration files.
7. Temporarily Reset the WordPress .htaccess File
On a standard Apache installation, a damaged or heavily modified .htaccess file may contribute to the loop.
- Download a backup of the existing
.htaccessfile. - Rename it to
.htaccess-old. - Test the website.
- If WordPress loads, go to Settings, then Permalinks.
- Save the permalink settings to generate fresh WordPress rules.
This will not fix redirect rules controlled by Nginx, a CDN, or the hosting platform.
8. Trace the Redirect Chain
Use a redirect checker or browser developer tools to identify every URL in the chain. Pay attention to changes involving:
- HTTP and HTTPS
- www and non-www
- Trailing slashes
- Uppercase and lowercase characters
- Login or language paths
- Old and new domains
The repeating pair usually reveals which two systems disagree.
Can Redirect Loops Hurt SEO?
Yes. Search engines cannot reach content trapped behind a redirect loop. The affected URLs may become temporarily inaccessible, waste crawl activity, lose conversions, and eventually drop from search results if the problem continues.
After fixing the loop, confirm that the final page returns a successful 200 status code and review Google Search Console for redirect or server errors.
How to Prevent Redirect Loops
- Choose one canonical HTTPS domain format.
- Avoid managing the same redirect in multiple places.
- Document redirects added through plugins, hosting, and CDNs.
- Test migrations and domain changes on staging.
- Review redirect chains during ongoing WordPress website maintenance.
Need Help Fixing a WordPress Redirect Loop?
If the website remains trapped in redirects after clearing caches and checking the main URL settings, stop adding new redirect rules. Additional rules can make the chain harder to diagnose.
