Home >Blog

Too Many Redirects: Causes, Diagnosis, and Fixes

Published Updated

Too Many Redirects: What the Error Means

A too many redirects error occurs when a browser is sent from one URL to another repeatedly, or through an unnecessarily long sequence of redirects. The first task is to determine whether the path is a redirect loop that never reaches a final page, or a long redirect chain that eventually completes but adds avoidable requests.

Use Redirect Chain Checker to See the Actual Path

1. Enter the failing URL

Open Redirect Chain Checker and paste the exact public HTTP or HTTPS URL that shows the error. Select Check Redirects to follow the path one hop at a time.

2. Review every response

The report records the source URL, destination URL, HTTP status code, and response time for each request. Check the final destination and hop count, then look for loop, long-chain, broken-target, cross-domain, or HTTPS-downgrade signals.

3. Keep the evidence

Use the report controls to copy the final URL or report, download JSON or CSV, or copy a share link. This makes it easier to compare the observed path with the redirect rules that should apply.

Redirect Loop vs. Long Redirect Chain

Redirect loop

A loop returns to a URL that already appeared earlier in the path, such as URL A redirecting to URL B and URL B redirecting back to URL A. The checker cannot reach a final destination, and browsers commonly display a too many redirects message.

Long redirect chain

A long chain does reach a final URL, but only after several sequential redirects. Redirect Chain Checker warns after ten hops. There is no universal hard limit, but a shorter direct path is easier to audit and avoids extra requests before the final page loads.

Browser Diagnosis Steps

  1. Retry the exact URL in a private browsing window to reduce the effect of existing site cookies.
  2. Clear cookies for the affected site if the error appears only in one browser profile.
  3. Open the browser network panel, preserve the request log, and reload the URL to compare the redirect locations with the checker report.
  4. Confirm that the browser request uses the intended protocol and hostname, including the expected www or non-www version.

Cloudflare Checks

  1. Review the SSL and origin configuration so the visitor-facing HTTPS behavior agrees with the origin server behavior.
  2. Inspect Redirect Rules and any legacy Page Rules for conditions that send a request back to an earlier URL in the path.
  3. Check host, path, and protocol conditions together. A rule that forces HTTPS can loop when another layer redirects the same request back to HTTP.
  4. Run the URL through Redirect Chain Checker again after each change and verify that the reported final destination is reached directly.

Server Redirect Checks

Nginx and Apache

Inspect server-level redirect and rewrite rules before changing application settings. In Nginx, compare return and rewrite directives across the relevant server blocks. In Apache, inspect Redirect and RewriteRule directives in the virtual host configuration and any applicable .htaccess file. Ensure the canonical host and protocol rule has conditions that exclude requests already at the intended destination.

Reverse proxies

When a proxy terminates HTTPS before forwarding to an application, confirm that the application receives the correct forwarded protocol and host information. A mismatch can make the application redirect every request to a URL that the proxy changes back.

WordPress Checks

  1. Compare the WordPress Address and Site Address in the WordPress settings with the public canonical URL.
  2. Check wp-config.php for WP_HOME or WP_SITEURL values that conflict with those settings.
  3. Temporarily review redirect, SSL, cache, and security plugin settings for duplicate host or protocol redirects.
  4. After each change, test the original URL rather than only the homepage, then use the checker report to confirm the path has no repeated URL.

Example: Reading a Report

If the report shows an HTTP URL redirecting to HTTPS, then a hostname change, and finally a 200 response, the page is reachable but may be simplified by redirecting the original URL to the final canonical URL in one step. If a destination repeats a prior source URL, focus on the rules responsible for those two URLs because they form the loop.

Common Questions

Does a 301 or 302 always cause a loop?

No. A 301 is permanent and a 302 is normally temporary. Either status can be part of a valid single redirect or an invalid repeated path. The sequence of URLs determines whether there is a loop.

Should every redirect be removed?

No. A single redirect can be appropriate when a page, hostname, or protocol has changed. The goal is to preserve the intended destination while removing unnecessary intermediate hops and repeated paths.

FAQ

What does too many redirects mean?
It means the requested URL is being redirected repeatedly or through a path that the browser cannot complete. A repeated URL in the path indicates a loop.
How does Redirect Chain Checker help diagnose a redirect error?
It follows a public HTTP or HTTPS URL one hop at a time and shows the source URL, destination URL, HTTP status, response time, hop count, final destination, and relevant warning signals.
What is the difference between a redirect loop and a long redirect chain?
A loop returns to a URL already seen in the path and never reaches a final destination. A long chain eventually reaches a final URL but has unnecessary intermediate redirects.
What should I check in Cloudflare when redirects loop?
Review SSL and origin behavior together, then inspect Redirect Rules and Page Rules for host, path, or protocol conditions that return a request to an earlier URL.
What WordPress settings can cause too many redirects?
Conflicting WordPress Address, Site Address, WP_HOME, WP_SITEURL, or plugin redirect settings can create duplicate host or protocol redirects.

Table of Contents

Information

  • Hits14
  • Published date2026/09/07

Tags

0/500
Share your thoughts respectfully.

More Posts

Explore more articles from this section
301 vs 302 Redirects: When to Use 301, 302, 307, and 308
Aug 26, 202621views

301 vs 302 Redirects: When to Use 301, 302, 307, and 308

Compare permanent and temporary HTTP redirects, understand method preservation in 307 and 308, and verify migr...

#301 redirect#302 redirect#307 redirect#308 redirect
How to Find the Final URL Behind a Short Link
Aug 29, 202620views

How to Find the Final URL Behind a Short Link

Learn how to expand a short link with Redirect Chain Checker, identify the final URL, inspect each redirect ho...

#final URL#short link#URL redirect chain#short link safety
What Is a Redirect Chain? A Clear Guide With Real Examples
Aug 23, 202616views

What Is a Redirect Chain? A Clear Guide With Real Examples

Learn what a redirect chain is, how hops connect a source URL to a final URL, and how to identify and fix sing...

#redirect chain#HTTP redirects#SEO#source URL
Do Redirect Chains Hurt SEO? What Google Recommends
Sep 01, 202613views

Do Redirect Chains Hurt SEO? What Google Recommends

Learn how to use Redirect Chain Checker to distinguish a normal one-hop redirect from an SEO-risky chain, insp...

#redirect chain SEO#redirects#crawl budget#website migration
Redirect Audit Checklist: How to Find Chains, Loops, and Broken Targets
Sep 19, 202612views

Redirect Audit Checklist: How to Find Chains, Loops, and Broken Targets

A practical redirect audit checklist: find chains, loops, and broken targets, measure their SEO impact, and fi...

#redirect audit#redirect chains#redirect loops#broken redirects
How to Set Up and Test HTTP to HTTPS Redirects Correctly
Sep 17, 202611views

How to Set Up and Test HTTP to HTTPS Redirects Correctly

Set up a single canonical HTTPS destination, test HTTP and www variants with Redirect Chain Checker, remove mu...

#HTTP to HTTPS redirect#HTTPS redirect#www redirect#redirect chain