How to fix "too many redirects" errors on your website

Why redirect loops happen, how to trace them, and how to fix the common causes, from HTTPS and CDN settings to www rules and CMS URLs.

By the UK Technology Hub teamPublished 4 minute read

The short answer

A "too many redirects" error means pages keep redirecting in a loop, so the browser gives up. Common causes are conflicting HTTPS rules between your server and a CDN, opposing www and non-www redirects, wrong site URLs in your CMS, plugin conflicts and cached redirects. Trace the redirect chain with a checker tool, find where the loop starts and remove the conflicting rule.

"This page isn't working: redirected you too many times." Visitors see this when page A redirects to page B, which redirects back to A, or through a longer loop. Browsers stop after a set number of redirects. Here's how to find and break the loop.

Step 1: Rule out your browser

Old cookies or cached redirects can cause loops even after the server is fixed. Test in a private window or a different browser, and clear cookies for the site. If the error disappears, cookies were the problem; if it remains, the issue is on the server.

Step 2: Trace the redirect chain

Use an online redirect checker or browser developer tools (Network tab) to see each step: which URL redirects where, and with which status code. You'll typically spot a pattern like:

  • http to https, then https back to http.
  • www to non-www, then non-www back to www.
  • /page to /page/, then /page/ back to /page.

Common causes and fixes

HTTPS loops with a CDN or proxy

A classic cause: a CDN or proxy connects to your server over HTTP while your server forces HTTPS, which redirects again, endlessly. For example, some CDN "flexible" SSL modes connect to the origin over HTTP. Fix by:

  • Installing a certificate on your origin server.
  • Setting the CDN to a full or strict SSL mode that connects to the origin over HTTPS.
  • Making sure only one layer handles the HTTP to HTTPS redirect.

Conflicting www rules

If your host redirects to www but your CMS or another rule redirects to non-www, they fight. Choose one preferred version and configure it in one place only.

Wrong site URLs in your CMS

In WordPress, the Site Address and WordPress Address settings must match your actual domain and protocol. If you can't reach the dashboard, these can be set in wp-config.php or updated in the database.

Trailing slash conflicts

Server rules and application settings may disagree about whether URLs end with a slash. Pick one convention and apply it consistently.

Plugin or app conflicts

SEO, security, caching and redirect plugins can add competing rules. Disable them one at a time to find the conflict.

Redirect rules gone wrong

A broad redirect rule may unintentionally match its own destination. Review recently added rules in .htaccess, server configuration, hosting dashboards or redirect plugins.

Cached redirects

Permanent (301) redirects are cached by browsers and CDNs. After fixing, purge CDN caches and test in a fresh browser.

Once loops are fixed, check pages for insecure content warnings. Our guide to fixing mixed content warnings covers the next step in a smooth HTTPS setup.

Step 4: Test thoroughly

Test the homepage, inner pages, admin areas, forms and logins, with and without www, and with http and https. Check that each variation reaches the final URL in a single redirect where possible.

Server errors

If you see a 500 error instead of a loop after editing configuration files, see our guide to fixing 500 internal server errors.

Prevention

  • Manage redirects in as few places as possible.
  • Document redirect rules and who owns them.
  • Test changes on staging first.
  • Avoid stacking multiple plugins that handle redirects.

Redirect loops after an HTTPS migration

Loops are especially common right after moving to HTTPS. Check every place that might force HTTPS: the web server, hosting dashboard, CDN, CMS settings and plugins. Keep only one, ideally at the server or CDN level, and make sure all of them agree on the final URL format.

Testing redirect rules safely

Test new redirect rules on a staging site first. Use temporary (302) redirects while testing, switching to permanent (301) once you're confident, so mistakes aren't cached by browsers for long periods.

Documenting redirects

Keep a list of redirect rules, why each exists and where it's configured. This saves hours when troubleshooting and prevents conflicting rules being added later.

How we help

Our maintenance and support team untangles redirect loops and HTTPS problems. Our web development team configures CDNs, SSL and redirects correctly from the start, and our CMS development team resolves plugin conflicts.

Frequently asked questions

Why do I get too many redirects only in one browser?

Cached redirects or cookies in that browser. Clear cookies and cache, or try a private window.

Can Cloudflare or another CDN cause redirect loops?

Yes, especially when SSL modes conflict with HTTPS redirects on your server.

Do redirect loops hurt SEO?

Yes, if they persist. Search engines can't reach affected pages, which can lead to them dropping from results.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

How to fix the WordPress white screen of death

A calm, step-by-step guide to diagnosing and fixing a blank white WordPress page, from recovery mode and debug logs to plugins, themes and memory limits.

All bug fixes & troubleshooting guides