ERR_TOO_MANY_REDIRECTS error: Causes and solutions for redirect loops

Mismatch between the WordPress address and site address

The most common cause of WordPress too many redirects is the two addresses under Settings › General conflicting with server rules. WordPress tries to send visitors to the registered address; if the server or another layer forces a different address, a loop forms.

According to WordPress’s Changing the site URL documentation, “WordPress Address (URL)” is where core files reside, while “Site Address (URL)” is what visitors type to reach the site. The same documentation states that both settings should include https:// and no trailing slash. If the server redirects to an https address with www while these fields contain http or non-www addresses, the problem originates here.

When the panel is inaccessible, addresses can be fixed by adding WP_HOME and WP_SITEURL constants to wp-config.php. The documentation also notes that this is not the best solution, hardcodes the values, and prevents later changes through General Settings. If the RELOCATE method in the same documentation was used, remove that line from wp-config.php after the operation as required by its security warning.

Conflicting HTTPS and www rules in .htaccess

On Apache or LiteSpeed servers, multiple HTTPS or www rules added to .htaccess over the years can act in opposite directions, producing a redirect loop and ERR_TOO_MANY_REDIRECTS. One rule removing www while another adds it is a typical example.

Follow this sequence when examining .htaccess:

• Take a copy of the file; edit only after copying.
• Mark RewriteCond and RewriteRule lines containing HTTPS, www, and the domain.
• If two rules perform the same task, retain only one; define the preferred address with a single rule.
• Note unfamiliar rules outside WordPress’s own “# BEGIN WordPress” block separately.

If a hosting panel option such as “Force HTTPS” is enabled while .htaccess has the same rule, two redirects overlap. Rules sending users to an unfamiliar domain may indicate a security issue rather than configuration; this situation is covered in the hacking section below.

When Cloudflare SSL mode conflicts with server redirection

The best-known cause of loops on Cloudflare sites is SSL/TLS encryption mode being “Flexible” while the server redirects HTTP to HTTPS. The visitor connects to Cloudflare over HTTPS, Cloudflare reaches the server over HTTP, the server redirects to HTTPS, and the cycle repeats.

Cloudflare’s ERR_TOO_MANY_REDIRECTS troubleshooting documentation lists the causes as follows:

In our maintenance experience, the lasting approach is generally installing a valid server certificate and setting Cloudflare to Full (strict); in Flexible mode, traffic between the server and Cloudflare remains unencrypted. WordPress’s HTTPS documentation also states that sites behind a reverse proxy providing SSL may enter infinite redirect loops and recommends configuration based on HTTP_X_FORWARDED_PROTO. What Cloudflare adds to a site and its basic settings in the Cloudflare guide is explained.

When SSL, redirection, and caching plugins overlap

A loop can form when two plugins doing the same job, or a plugin and a server rule, redirect simultaneously. An SSL plugin forcing HTTPS while an old http entry remains in a redirection plugin is a typical example.

Items checked in a plugin-related loop:

• SSL plugins: While a plugin forces HTTPS, does the server or Cloudflare also perform the same redirect?
• Redirection plugins: Are there two entries with identical sources and destinations or entries pointing to each other?
• Caching plugins: Is an old redirect response cached and served to everyone?
• Security and multilingual plugins: Is a setting changing the login address or adding a language prefix participating in the loop?

If the panel is inaccessible, disable the suspected plugin by renaming its folder under wp-content/plugins through FTP or the file manager. Then clear the caching plugin, server, and CDN caches; otherwise, the repaired site may continue showing the old response for a while. If the loop occurs only on the login screen, also check browser cookies, FORCE_SSL_ADMIN in wp-config.php, and any security plugin changing the login address.

Loops appearing after site migration and HTTPS transition

When ERR_TOO_MANY_REDIRECTS appears immediately after migration or a domain change, the source is often an old address remaining in the database. Files have moved to the new server, but siteurl and home still point to the old domain or http.

The places checked for post-migration loops are database address records, .htaccess copied from the old server, automatic HTTPS redirection enabled on the new hosting, and whether DNS still points to the old server. WordPress migration documentation describes methods such as General Settings, wp-config.php constants, and temporary update_option usage in functions.php for address changes. Database addresses are not changed manually one by one; bulk updates use tools that change them without breaking serialized data.

When HTTPS transition and migration happen on the same day, sources of error double. If migration is to be planned together with address, redirection, and SSL steps, the WordPress site migration service covers this process from beginning to end.

Step-by-step solution: In what sequence should you proceed?

The aim in resolving ERR_TOO_MANY_REDIRECTS is to determine one preferred address and leave redirection to it in only one layer. Proceeding by reading the chain instead of guessing settings prevents a second loop on the same day.

1. Define the preferred address in writing: https, with www, or without www?
2. Confirm with a private window and header check that the problem affects everyone.
3. Back up files and the database; take separate copies of .htaccess and wp-config.php.
4. Map the redirect chain and note both ends of the loop.
5. If there is a CDN, check its SSL mode and redirect rules.
6. Align WordPress Address and Site Address with the preferred address.
7. Remove duplicate redirection from .htaccess and the hosting panel.
8. Check plugins individually, clear every cache layer, and retest the chain.

Common mistakes and the correct method

The most time is lost when resolving a loop by changing multiple settings simultaneously. Make one change, test it, record the outcome, then proceed to the next. Permanently disabling the Cloudflare proxy, deleting the SSL plugin and abandoning https, or deleting .htaccess without a backup may open the site briefly while creating new problems. The correct method is to keep redirection in one place as a permanent 301.

How does the too many redirects error affect SEO?

Because a looping page cannot serve content to any visitor, including Googlebot, it cannot be indexed and may eventually lose its place in search results. According to Google’s HTTP status codes documentation, Google crawlers follow a maximum of 10 redirect hops by default, and the redirecting address’s content is ignored while only the final destination’s content is processed.

The same documentation states that Search Console produces error messages for failed redirects. Because a loop never produces a final destination, no content remains to be processed. Google’s Redirects documentation recommends using permanent server-side redirects wherever possible for permanent moves.

In practice, correct setup is a one-step 301 from the old address to the new: http://alanadi.com goes directly to https://www.alanadi.com with no intermediate stop. The difference between permanent and temporary redirects and correct setup in the 301 redirect guide is explained.

How does this differ from a hacked redirect?

ERR_TOO_MANY_REDIRECTS is a site continually circulating between its own addresses; a hacked redirect sends visitors to another, unfamiliar website. The first is a settings conflict and the second a security breach, with entirely different solutions.

• Destination: A loop always shows the same domain; a malicious redirect leads to an unfamiliar domain such as a gambling, drug, or fake-prize website.
• Consistency: A loop generally happens for everyone every time; a malicious redirect often appears only on mobile or for visitors arriving from Google.
• Source: A loop comes from a known setting; malicious redirection comes from unfamiliar code, users, or files.

If an unfamiliar domain appears in the chain, perform a security review instead of adjusting settings. Symptoms and the cleanup sequence in the WordPress hacked redirects guide are also covered separately.

When should you consult a specialist for WordPress too many redirects?

Specialist support saves time if the loop persists after reading the chain and aligning address settings, or if the panel is completely inaccessible. The order of changes matters on websites where several layers, including the hosting panel, .htaccess, CDN, and plugins, redirect simultaneously.

Specialist support for ERR_TOO_MANY_REDIRECTS is particularly necessary when an e-commerce checkout or cart page loops, database addresses need bulk replacement after migration, Cloudflare access is unavailable, or an unfamiliar address appears in the chain. Our repair process takes a backup first, records the chain, repeats header checks after every change, and shares the work performed in writing.

For one-time failures, the WordPress troubleshooting service identifies and resolves the source of the loop. If updates, SSL, and cache settings are to be checked regularly, WordPress maintenance costs 500–2,000 TL per month depending on the site’s scope.