When your browser reports “too many redirects” or ERR_TOO_MANY_REDIRECTS, your site is bouncing between two addresses endlessly and never landing anywhere. It takes the whole site offline, but the causes are few and the fix is usually quick.
What a redirect loop is
A loop happens when address A redirects to B, and B redirects back to A. The browser follows the bouncing until it gives up. In WordPress this is nearly always about the site URL, HTTPS settings, or a redirect plugin — three things fighting over where a visitor should end up.
Check your site URLs
The most common cause is a mismatch between your WordPress Address and Site Address settings. If one says http:// and the other https://, or one has www and the other doesn’t, they redirect back and forth. Since you may be locked out of the dashboard, set them firmly in wp-config.php:
define('WP_HOME', 'https://yourdomain.com');
define('WP_SITEURL', 'https://yourdomain.com');Make both identical and correct. This alone fixes most loops.
Review your .htaccess redirects
Conflicting rules in .htaccess cause loops too — for example, a rule forcing HTTPS combined with another forcing www, written in a way that they contradict. Temporarily rename .htaccess to test whether it’s the source, then rebuild it carefully with one clean HTTPS/www redirect rather than several overlapping ones.
Clear cookies and cache
Sometimes the loop is cached in your browser even after you’ve fixed the server. Clear your browser’s cookies and cache for the site, or test in an incognito window, so you’re seeing the real current behaviour.
Disable a suspect plugin
SSL, caching and redirect plugins can all create loops, especially if two of them try to enforce HTTPS in different ways. Disable plugins by renaming the plugins folder in File Manager. If the loop clears, reactivate them one at a time to find the offender.
Check for a plugin fighting the server
A frequent culprit is an SSL plugin forcing HTTPS while the server is also redirecting — pick one method, not both. If your server handles the HTTPS redirect via .htaccess, you don’t need a plugin doing the same job.
Set the URLs correctly and use a single, clean redirect rule, and the loop breaks. If it persists after all this, there may be a server-level redirect involved — send us the domain and we’ll trace it.
