Back to Community
Home / Community / Plugin → Redirection

Troubleshooting Infinite Redirect Loops with the Redirection Plugin

50 threads Sep 16, 2025 Plugin → Redirection

Content

Encountering an infinite redirect loop, often signaled by a browser error like "Too many redirects," is a common and frustrating issue for WordPress users. This problem can make parts of your site, or even the entire site, inaccessible to visitors. Based on community discussions, this guide will help you understand why these loops happen and how to resolve them.

What is an Infinite Redirect Loop?

An infinite redirect loop occurs when a URL is configured to redirect to another URL, which in turn redirects back to the original URL or another URL in a never-ending cycle. The browser eventually stops the process and displays an error.

Common Causes and Their Solutions

1. Conflicting Redirect Rules Within Redirection

The most straightforward cause is creating two or more redirect rules that point to each other. For example:

  • Rule 1: /blog/page1/ → /page1/
  • Rule 2: /page1/ → /blog/page1/

This creates a perfect loop that the browser cannot resolve.

How to fix it:

  • Carefully review your list of redirects in the Redirection plugin. Look for any pairs of rules where the source of one is the target of another and vice versa.
  • Delete or modify one of the rules to break the cycle. The goal is to have a clear, final destination URL.

2. Another Plugin or Theme is Causing the Redirect

Often, the Redirection plugin is mistakenly blamed for a loop it isn't causing. Many other plugins (like Yoast SEO) and themes have their own redirect features that can conflict.

How to fix it:

  • Check the Redirection Logs: The Redirection plugin includes a log feature. If the logs do not show any activity for the problematic URL during the time of the error, it is strong evidence that another source is causing the redirect.
  • Conflict Test: Deactivate all other plugins except Redirection and switch to a default WordPress theme (like Twenty Twenty-Four). If the loop stops, reactivate your plugins one by one to identify the culprit.

3. Server-Level or Caching Configuration

Redirects can also be set at the server level (e.g., in an .htaccess file) or by a caching service like Cloudflare. These redirects will happen before WordPress or the Redirection plugin even loads.

How to fix it:

  • Inspect your site's .htaccess file for any redirect rules that might be creating a conflict.
  • If you use a caching plugin, clear its cache completely. Also, check if the caching plugin has its own redirect settings.
  • For services like Cloudflare, check the Rules or Page Rules sections for any configured redirects and clear Cloudflare's cache.

4. HTTP to HTTPS Forced Redirects

A common and usually harmless form of "chain" redirect is when a request first goes to an HTTP version of a site and is forced to HTTPS by the server, and then the Redirection plugin handles a path change. While this is typically not an infinite loop, it's important to understand the flow.

Example:
http://example.com/old-page/ → (Server forces HTTPS) → https://example.com/old-page/ → (Redirection rule) → https://example.com/new-page/

Proactive Tip: Preventing Future Loops

When creating a new redirect, always test the target URL in your browser first to ensure it doesn't redirect somewhere unexpected. The Redirection plugin team has indicated that a feature to show warnings for potentially problematic redirects is under development.

Conclusion

Infinite redirect loops are rarely caused by a single factor. The key to solving them is a methodical approach: first check your Redirection rules for obvious conflicts, then investigate other plugins, and finally look at server and caching configurations. By following these steps, you can identify the root cause and restore your site's functionality.

Related Support Threads Support