WordPress ERR_TOO_MANY_REDIRECTS: Complete Technical Guide

Understanding the ERR_TOO_MANY_REDIRECTS Error

You've just tried to access your WordPress site and instead of your homepage, you're staring at a browser error. The page shows "ERR_TOO_MANY_REDIRECTS" or "This page isn't redirecting properly." Your site is trapped in an infinite loop.

The ERR_TOO_MANY_REDIRECTS error occurs when a browser detects an infinite redirect loop during the HTTP request-response cycle. Modern browsers implement a redirect limit (typically 20-30 hops) to prevent endless loops. When this limit is exceeded, the browser terminates the connection and displays the error message. This differs from other WordPress errors because it prevents any page from loading, including the admin dashboard. The error indicates a misconfiguration in how URLs are being rewritten or redirected at either the server level, application level, or CDN level.

Browser-Specific Error Messages

Despite the different messaging, all these errors indicate the same fundamental problem: a circular redirect chain that the browser cannot resolve.

Redirect loops don't just frustrate visitors--they waste crawl budget as search engines cycle through infinite chains. Our technical SEO services include comprehensive site architecture audits to identify and resolve these configuration issues before they impact your search performance. Understanding how search engine bots render your pages is essential for diagnosing redirect issues that affect crawl efficiency.

Root Causes: Technical Analysis

WordPress URL Configuration Mismatches

The WordPress Address (WP_HOME) and Site Address (WP_SITEURL) settings in wp-admin → Settings → General are the most common source of redirect loops. When these two values differ (for example, one with www and one without, or one using HTTP while the other uses HTTPS), WordPress attempts to reconcile the difference through redirects.

If the server-level configuration also contains redirect rules addressing the same discrepancy, you create a loop:

Browser → HTTP → Server redirect to HTTPS → WordPress redirect to HTTP → Server redirect to HTTPS → [LOOP]

HTTPS and SSL Certificate Configuration

SSL/TLS misconfiguration is the second-leading cause of redirect loops:

• Forcing HTTPS without valid SSL: If WordPress forces HTTPS but no valid certificate exists
• Certificate chain issues: Intermediate certificates must be properly installed for browsers to establish secure connections
• Mixed content redirects: Insecure resources loading on secure pages can trigger additional redirects

Use the Qualys SSL Labs tool to verify certificate configuration and identify issues that may cause redirect conflicts.

Plugin and Theme Conflicts

WordPress plugins that handle URL redirection--especially SEO plugins, security plugins, and caching plugins--can create conflicting rules:

• Multiple plugins each attempting to manage redirects independently
• Plugins that force HTTPS without checking for existing server-level rules
• Caching plugins that store redirect responses incorrectly

For sites with multiple redirect-management plugins, we recommend consolidating to a single source of truth--either server configuration or a dedicated redirect plugin. This approach aligns with our crawl optimization strategy to maximize search engine efficiency. Proper server configuration also requires understanding JavaScript rendering requirements for modern WordPress sites using page builders and dynamic content.

If you're experiencing redirect conflicts alongside performance issues, our web development team can audit your server configuration and WordPress setup to identify and resolve these conflicts systematically.

Server-Level Redirect Rules

Apache (.htaccess) Configuration

# Only one redirect rule for HTTP→HTTPS
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Nginx Server Block Configuration

server {
 listen 80;
 server_name example.com www.example.com;
 return 301 https://example.com$request_uri;
}

server {
 listen 443 ssl;
 server_name example.com www.example.com;
 # ... SSL configuration
 location / {
 try_files $uri $uri/ /index.php?$args;
 }
}

The key is ensuring only one layer handles the HTTP-to-HTTPS redirect. When multiple configuration layers (WordPress, server, CDN) each attempt to manage redirects, conflicts emerge.

CDN and Reverse Proxy Configuration

Cloudflare's "Flexible SSL" option is notorious for causing redirect loops. When Flexible SSL is enabled, Cloudflare terminates SSL at their edge while communicating with your origin server over HTTP:

Cloudflare (HTTPS) → Origin (HTTP) → Origin redirect to HTTPS → Cloudflare (HTTPS) → [LOOP]

Solution: Set Cloudflare SSL to "Full" or "Full (strict)" when your origin has SSL configured. This ensures consistent protocol handling across all layers of your content delivery infrastructure.

Our AI automation services can help monitor redirect configurations and alert you to issues before they affect your site's availability. Additionally, implementing mobile-first web design principles ensures that redirect configurations work correctly across all device types and CDN edge locations.

Diagnostic Procedures

Step 1: Browser-Level Diagnostics

Before touching server configurations, rule out browser-side issues:

1. Clear browser cookies specifically for your domain - cookies can store outdated redirect information
2. Test in incognito/private mode to disable extensions that might interfere
3. Try a different browser entirely to isolate browser-specific caching issues

Step 2: External Redirect Analysis

Use online tools to trace the redirect chain without triggering browser security blocks:

• Redirect Checker: Shows complete redirect chain with status codes
• httpstatus.io: Visual representation of HTTP responses through the redirect chain
• Redirect Path browser extension: Real-time redirect tracking in Chrome

These tools reveal where the loop originates--whether at the CDN, server, or application level.

Step 3: Server Log Analysis

Server error logs contain entries for redirect chains. Look for patterns of repeated 301 or 302 responses to the same URLs. Access logs show the complete request path including redirect hops.

Resolution Procedures

Fixing WordPress URL Settings

If you can access wp-admin, navigate to Settings → General and ensure WordPress Address and Site Address are identical. Include the correct protocol (https://) and use either www or non-www consistently.

If locked out of admin, add to wp-config.php before /* That's all, stop editing! */:

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

Plugin Conflict Resolution

1. Deactivate all plugins via FTP/SFTP by renaming /wp-content/plugins/ to /wp-content/plugins.old/
2. Test site functionality
3. Reactivate plugins one by one, testing after each activation
4. Identify the conflicting plugin and find an alternative or configuration fix

Redirect loops directly impact Core Web Vitals metrics--LCP is delayed by redirect chains, CLS becomes unstable as redirects resolve, and INP suffers during loop detection. Understanding Core Web Vitals scoring helps you recognize how redirect issues affect your overall SEO performance.

Sources

1. Kinsta: How to Fix The ERR_TOO_MANY_REDIRECTS Error - Comprehensive guide covering all causes including cookie deletion, cache clearing, HTTPS settings, and server configurations

2. Hostinger: How to fix ERR_TOO_MANY_REDIRECTS in WordPress - Step-by-step tutorial with practical solutions including WordPress URL configuration and prevention strategies

3. Cloudways: How to Fix the ERR_TOO_MANY_REDIRECTS Error - Detailed guide covering redirect loops, browser variations, and cloud hosting considerations

4. Cloudflare Support: SSL/TLS Settings - Official documentation on Flexible SSL causing redirect loops

5. Mozilla Support: Delete Cookies - Browser recommendations for cookie deletion