How Do I Fix Too Many Redirects on My Website?
Trace redirect loops across domains, HTTPS settings and application rules, then verify one controlled correction instead of deleting every redirect.
Part of our guide: What Are URL Redirects and Why Are They Important?
“Too many redirects” means the browser has been sent onward repeatedly without reaching a usable final page. The underlying problem may be conflicting rules rather than too many pages or too much website content.
A typical loop sends one address to a second address, then sends the second back to the first. MDN’s redirection guide explains this class of failure. Your maintainer needs the actual route sequence to identify which settings disagree.
Save the starting point
Record the exact address that fails, the time and how you reached it. Does the homepage fail, or only login, checkout or a particular service page?
Try a private window as a comparison, without disabling security protection. A different outcome can suggest session-specific behaviour, but it does not prove that cookies are the only cause.
If clearing site data is proposed, explain that it may sign you out or discard a local cart. Do not ask every customer to erase all browser history as a substitute for fixing a repeatable server-side loop.
Draw the observed sequence
Ask the developer to capture response status and destination headers for the failing route. A small chain is easier to reason about than several screenshots of the same error.
An illustrative loop might be:
- The hosting rule sends HTTP to HTTPS.
- A misconfigured application believes the request is insecure.
- Another rule sends the request back to HTTP.
- The first rule runs again.
This is a hypothetical explanation, not a diagnosis of your installation. Similar disagreement can happen between www and non-www addresses or between trailing-slash conventions.
Identify every place that controls redirects
Redirects can be configured at the hosting service, a CDN or proxy, the application and an extension. Two individually reasonable rules can conflict.
Make a short inventory of who controls each layer and what the intended canonical address is. The redirect overview explains their normal purpose; a loop is a fault in that routing, not a reason to remove all forwarding.
If the problem began after a deployment, compare the previous and current configuration before making unrelated changes.
Change one responsible rule
Take a recoverable configuration copy and agree a rollback route. A developer should adjust the identified conflict, then retest the same starting address.
Do not indiscriminately disable all security or SEO extensions on a live revenue-critical website. Where application isolation is needed, use a controlled staging environment and the plugin-conflict process.
If the loop involves login or payment, involve the people responsible for those systems before experimenting.
Verify more than the homepage
Use a short test list:
| Route | What to confirm |
|---|---|
| Original failing URL | Reaches the correct final page |
| HTTP and HTTPS entry points | Follow the intended secure route |
| www and non-www forms | Resolve consistently where supported |
| Login or booking | Completes without cycling |
| Old marketing link | Still reaches relevant content |
A redirect ending in a missing page is not a successful repair. Check the content and customer task as well as the status sequence.
Keep the reason for the rule
Document the final destination, configuration owner and reason for the redirect. Add the incident to the change record so another supplier does not reintroduce the conflicting setting later.
For a larger rebuild, the SEO migration guide helps preserve old routes deliberately. Stable, understandable routing is the goal; the smallest possible number of rules is not always the right measure.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
