What Is the “Too Many Redirects” Error?
The “too many redirects” error happens when redirects on your website are set up incorrectly, creating an endless loop that stops the page from loading. This negatively impacts SEO and user experience because both search engines and visitors are unable to reach the page.
For instance, imagine URL X redirects to URL Y, and then URL Y redirects back to URL X.
This forms a loop. The browser keeps switching between the two URLs until it eventually stops and displays an error.
Most browsers will follow roughly 20 redirects before giving up. If no final destination is reached within that limit, an error message appears.
In Chrome, you’ll see a message stating that the page isn’t working because it redirected too many times, often suggesting that you clear your cookies.
What Triggers the “Too Many Redirects” Error?
This error occurs when the browser gets stuck in a continuous redirect cycle without landing on a final page.
According to Dan Taylor, Partner & Head of Technical SEO at SALT.agency, the issue is most often linked to cookie or cache mismanagement.
He explains that in his experience, problems with cache or cookies—such as session handling or incorrect cache-control headers—are usually responsible. In the past, HTTP to HTTPS conflicts were more common, but that’s less of an issue today.
Other frequent causes include:
- Outdated server cache: The server may still be serving an older version of the site that contains incorrect redirect rules
- CDN cache problems: A content delivery network might deliver cached pages with outdated redirect settings
- Conflicting third-party tools or plugins: Two systems (like a firewall and a plugin) trying to manage redirects differently can create loops
How to Check for “Too Many Redirects” Errors
You can manually test for the ERR_TOO_MANY_REDIRECTS issue by visiting your site in various browsers.
Dan recommends first reviewing redirect rules directly by checking the .htaccess file or server configuration to ensure there are no conflicting instructions.
He also verifies that redirects between HTTP and HTTPS and between www and non-www versions are configured consistently.
You can also use Semrush’s Site Audit tool to scan for redirect-related issues:
- Set up your project and run an audit.
- After completion, go to the “Issues” tab and search for “redirect.”
- If redirect chains or loops exist, you’ll see an error highlighting them.
- Click the issue to view affected URLs.
Keep in mind that this method primarily detects loops caused by incorrect redirect rules. Other technical problems may also contribute.
8 Ways to Fix the “Too Many Redirects” Error
1. Clear Browser Cache and Cookies
Removing cached data and cookies eliminates stored redirect paths that may be causing the loop.
Dan recommends clearing cache and cookies as an early troubleshooting step to rule out stored redirect information.
This is especially helpful if only one user—or only you—are experiencing the issue.
You can clear cookies and cached files through the privacy or browsing data settings in browsers like Chrome, Firefox, Safari, and Microsoft Edge by selecting the relevant options and choosing the “All time” range.
2. Clear Your CMS Cache
If your content management system or caching plugin is storing outdated redirect instructions, clearing the CMS cache can resolve the problem.
For WordPress users with caching plugins like WP Super Cache, you can delete cached pages directly from the plugin settings in the dashboard.
For other platforms such as Drupal, Joomla, or OpenCart, follow their respective documentation to clear cache.
3. Clear Server Cache
Your hosting server may also store cached files with faulty redirect rules. Clearing the server cache ensures outdated files aren’t being served.
Most hosting providers offer cache-clearing tools within their dashboards. If unsure, contact your hosting support team for assistance.
4. Remove Old Redirects from Your CDN
A CDN stores copies of your website across multiple locations. If those copies contain outdated redirect settings, they can continue causing loops.
For example, in Cloudflare, you can purge cached content from the dashboard by selecting the caching configuration and choosing “Purge Everything.”
Other CDNs like Fastly, Akamai, or Azure CDN provide similar cache-clearing options in their documentation.
5. Check for HTTPS Issues
Improper SSL setup or forcing HTTPS without a valid certificate can lead to redirect loops.
Use an SSL checker tool to confirm your certificate is valid and properly installed. If problems are detected, reach out to your hosting provider.
You can also identify HTTPS-related errors in Semrush’s Site Audit under the HTTPS section in the Overview report.
6. Review and Correct Redirect Rules
Conflicting or incorrect redirect rules are a common cause of loops.
In Site Audit’s Issues report, you can view redirect chains and loops. To fix them, update or remove problematic rules using the tool or platform where they were created—such as a plugin, CMS settings, or server configuration files.
In WordPress, plugins like Redirection allow you to view and modify active rules directly from the dashboard.
If you’re using Apache, redirect rules may be stored in the .htaccess file. You can back up and reset this file to the default WordPress configuration if needed—but only if you’re confident editing server files or have developer support.
If your server runs on Nginx or another system, contact your hosting provider or developer for assistance.
7. Verify URL Settings in Your CMS
Redirect loops can happen if your CMS has mismatched site URLs.
In WordPress, check “Settings” > “General” and confirm that the “WordPress Address (URL)” and “Site Address (URL)” are identical.
Differences between HTTP and HTTPS or between www and non-www versions can trigger loops.
Update both fields so they match exactly.
For other platforms, follow their documentation to adjust the main site URL.
8. Disable or Adjust Plugins and Extensions
A plugin or extension may be creating conflicting redirect rules.
In WordPress, you can deactivate all plugins from the “Installed Plugins” section using bulk actions. If the error disappears, reactivate them one by one to identify the problematic one.
Once identified, consider replacing it and notify the developer about the issue.
A similar approach can be used with other CMS platforms.
How to Prevent “Too Many Redirects” Errors
Most redirect loops can be avoided by thoroughly testing updates before making them live.
Dan recommends conducting proper QA whenever changes affect URLs, redirects, cookies, or asset delivery.
To prevent future issues:
- Manually test common redirect paths after updates to ensure pages resolve correctly
- Review plugins or custom scripts that manage redirects
- Run a full site audit after major changes such as redesigns, migrations, or domain updates
- Perform regular technical audits to catch potential issues before they impact SEO or traffic
Consistent monitoring and careful testing can help you avoid redirect loops and maintain smooth website performance.
FAQs
1. What does the “Too Many Redirects” error mean?
The “Too Many Redirects” error (also known as a redirect loop) occurs when a browser cannot load a webpage because it keeps being redirected between two or more URLs repeatedly. This prevents the page from fully loading.
In browsers like Google Chrome, you may see messages such as “ERR_TOO_MANY_REDIRECTS.”
2. What causes a redirect loop?
Common causes include:
- Incorrect HTTP to HTTPS redirects
- Conflicting WordPress plugin settings
- Misconfigured .htaccess file
- Incorrect CMS URL settings
- CDN or server misconfiguration
Even a small redirect rule mistake can create a loop.
3. Is the “Too Many Redirects” error bad for SEO?
Yes. Search engines like Google cannot properly crawl pages stuck in redirect loops. This can lead to:
- Deindexing
- Lost rankings
- Poor user experience
- Reduced crawl efficiency
Fixing redirect issues quickly is important for SEO health.
4. How do you fix the “Too Many Redirects” error?
You can fix it by:
- Clearing browser cookies and cache
- Checking redirect rules in your .htaccess file
- Verifying WordPress site URL settings
- Disabling conflicting plugins
- Reviewing server-level redirects
- Checking CDN configurations
Testing redirects with SEO tools can help identify loops.
5. Can SSL configuration cause redirect loops?
Yes. Improper HTTP → HTTPS redirection or incorrect SSL settings can create infinite redirect loops. Ensure your SSL certificate is properly installed and that only one redirection rule is applied.
6. How do you check redirect chains?
You can use:
- Google Search Console
- Browser developer tools
- SEO tools like Ahrefs or SEMrush
These tools help detect redirect chains and loops.
7. What is the difference between a redirect chain and a redirect loop?
- Redirect chain → URL A → URL B → URL C
- Redirect loop → URL A → URL B → URL A (infinite cycle)
Chains slow down performance, while loops break the page entirely.
8. Does clearing browser cookies fix the issue?
Sometimes. If the error is caused by corrupted cookies or cached data, clearing them may resolve the issue. However, server-side configuration problems require backend fixes.
9. Can WordPress cause “Too Many Redirects” errors?
Yes. In WordPress websites, common causes include:
- Incorrect “WordPress Address” and “Site Address” settings
- Redirect plugins
- Security plugins
- HTTPS enforcement conflicts
Careful configuration helps prevent loops.
10. How do you prevent redirect issues in the future?
Best practices include:
- Keeping redirect rules simple
- Avoiding unnecessary multiple redirects
- Testing changes before deployment
- Monitoring crawl errors regularly
- Using proper canonical tags
Regular technical SEO audits help maintain site health.
11. What HTTP status codes are involved in redirects?
Redirects commonly use:
- 301 (Permanent Redirect)
- 302 (Temporary Redirect)
- 307 (Temporary Redirect)
Improper implementation of these can contribute to redirect issues.
12. How long does it take to recover SEO rankings after fixing redirect errors?
Recovery depends on:
- Severity of the issue
- Crawl frequency
- Site authority
Once fixed, search engines typically re-crawl and reprocess affected pages within a few days to weeks.
