How to Fix the “Too Many Redirects” Error in Webflow

Seeing a “Too Many Redirects” error in Webflow? You’re not alone, and the good news is, it’s almost always fixable with a few simple steps.

This error typically means your browser is stuck in a loop: it's being told to go from one page to another, then back again, over and over. As a result, it gives up and shows this message:

• ERR_TOO_MANY_REDIRECTS
• Webflow redirected you too many times
• CloudFront Webflow too many automatic redirections were attempted

Whether you’ve just added a custom domain, configured Cloudflare, or set up redirects in Webflow, this guide will help you get things working again. Rest assured, this is a common misconfiguration, not a bug or major system failure. Let’s walk through the fixes.

Understand What Causes Redirect Loops in Webflow

A redirect loop occurs when your browser keeps bouncing between conflicting URLs with no resolution — for example, from www.yoursite.com to yoursite.com and back again.

The most common cause? A conflict between your www and non-www domains. If both are configured incorrectly, they can endlessly redirect to each other.

Other potential culprits:

• Cloudflare’s proxy settings
• CloudFront reverse proxy misconfigurations
• Improper 301 redirects set up in Webflow

If you’re unsure how redirects work in Webflow or want to future-proof your setup, here’s a step-by-step guide on how to set up 301 redirects in Webflow.

Set WWW as Your Default Domain

The first (and most effective) fix for this issue is making sure your www version is set as the default domain in Webflow.

Here’s how:

1. Go to your Webflow Site Settings → Publishing tab.
2. Scroll to the “Custom Domains” section.
3. Click the ‘Make default’ button next to the www.yoursite.com domain (not the root yoursite.com).
4. Re-publish your site.

Why this matters:

Many redirect loops happen because both the www and non-www versions of your site are competing, redirecting back and forth.

By setting the www version as the default, you tell Webflow (and your browser) to always point to one consistent version. This eliminates one of the most common sources of redirect conflicts.

This fix alone resolves the issue in most cases, especially after recent domain setups or migrations.

Clear Your Browser Cache

If you’ve already fixed your domain settings and are still seeing the redirect error, your browser might be caching the old redirect loop.

To rule this out:

• Open the site in an Incognito window (or Private tab)
• Try loading the site on a different device or network
• Or manually clear your browser cache

Clearing your cache ensures you’re not seeing a stored error page. Redirect errors can stick around locally even after they’ve been fixed on the server side.

Once you’ve cleared the cache or tested in private mode, try reloading your site to check if the loop is gone.

This step doesn’t fix a bad config, but it’s often the difference between thinking something’s broken… and realizing it’s already fixed.

Check Your Webflow Redirect Settings

Redirect loops don’t just happen at the domain level. They can also be caused by your custom redirect rules inside Webflow.

To check:

1. Open your Webflow Site Settings → Publishing tab.
2. Scroll down to the 301 Redirects section.

Look out for:

• Circular redirects (e.g., /page-a → /page-b, then /page-b → /page-a)
• Conflicting wildcard redirects that unintentionally catch the same path more than once

If you’re unsure, try this:

• Temporarily remove all redirect rules
• Re-publish your site
• Test to see if the redirect error goes away

Once confirmed, reintroduce redirects one by one to identify the culprit.

If you want to learn more about how Webflow handles SEO and redirects, you might enjoy our in-depth article on Webflow SEO.

Verify Your Custom Domain DNS

Sometimes the redirect issue isn’t in Webflow at all, but at your domain registrar.

To resolve it:

1. Log in to your domain provider (e.g., GoDaddy, Namecheap).
2. Make sure your DNS settings match Webflow’s recommended values:
   
   • A record → 75.2.70.75
   • CNAME (for www) → proxy-ssl.webflow.com

If you recently made DNS changes, remember: DNS propagation can take up to 48 hours to fully resolve globally.

Want to double-check? Use a tool like DNSChecker to confirm that your DNS settings are visible worldwide.

DNS misconfigurations are a common source of redirect loops, especially after launching a new site or switching hosts.

If you're looking for help from a team that handles both Webflow and technical SEO, we offer exactly that as a specialized SEO agency for tech startups.

Fixing Webflow Redirects Caused by Cloudflare

If you’re using Cloudflare, it could be interfering with Webflow’s redirect behavior.

To troubleshoot:

• Go to your DNS settings in Cloudflare
• Make sure the orange cloud (proxy) is turned OFF; switch to DNS Only (gray cloud)
• Under SSL/TLS settings, choose Full or Full (strict), not Flexible

Why? Webflow handles SSL on its own, and Flexible SSL on Cloudflare can break the handshake, causing redirect issues.

CloudFront: “Too Many Automatic Redirections Were Attempted” Error

Using AWS CloudFront to reverse proxy a Webflow project?

This setup is not supported by default unless you’re on Webflow’s Enterprise plan with custom proxy handling. In other cases, this often causes redirect issues such as:

• CloudFront Webflow too many automatic redirections were attempted

This happens because CloudFront may mishandle Host headers, SSL settings, or forward traffic between root and www incorrectly, especially if you're not setting the same domain defaults in Webflow and CloudFront.

To fix or avoid this:

• Avoid using CloudFront unless you're on Webflow’s Enterprise plan
• If necessary, ensure Host headers are forwarded correctly and domain behavior mirrors your Webflow configuration
• Consider using Webflow’s native CDN unless you have specific enterprise-level needs

We recommend reviewing FlowRadar’s guide on reverse proxy setups with Webflow if you're set on using CloudFront.

Use a Redirect Checker Tool to Diagnose the Issue

If you’ve tried the main fixes and the redirect loop still isn’t resolved, a redirect checker tool can help you understand what’s actually happening.

These tools trace each redirect your browser encounters, including 301s, 302s, and loops, giving you visibility into the full redirect chain.

Helpful tools:

• httpsaurus — Easily check status codes, response headers, and redirect chains.‍
• Redirect Checker — Check redirects and status codes.

How to use them:

1. Enter your full domain URL.
2. Review the output to identify any loops or unexpected redirects.
3. Use this data to revisit your DNS settings or 301 redirect rules.

This isn’t a fix by itself, but it’s one of the best ways to troubleshoot complex redirect chains when simple solutions haven’t worked.

Still Not Fixed? Try These Final Steps

If you’ve walked through every fix and are still seeing the redirect error, here are a few final things to try before escalating:

• Unpublish and Re-publish your Webflow site
• Test on a different network or device (mobile hotspot, friend’s computer)
• Check browser extensions — some privacy plugins or proxies can cause false positives
• Wait it out — if you made DNS changes recently, give it 24–48 hours to propagate fully

If none of that works, it may be time to contact Webflow Support directly. Include:

• Your domain name
• A screenshot of your redirect settings
• A list of steps you’ve already taken

They can help you spot issues that aren’t visible from your dashboard.

FAQs

Why does Webflow say "redirected you too many times"?

This usually means your domain settings are misconfigured; most often, it's a conflict between the www and non-www versions of your site.

How do I fix ERR_TOO_MANY_REDIRECTS in Webflow?

Start by setting the www version of your site as the default domain in Webflow Publishing settings. Then check your redirect rules, Cloudflare/CloudFront settings, and browser cache.

Conclusion: Clean Redirects = Happy Site

To recap: the most common fix is to set your www version as the default domain in Webflow. That alone resolves the issue for most users.

If that doesn’t work, revisit your custom redirects, Cloudflare or CloudFront setup, and domain DNS configuration. When in doubt, a redirect checker tool will show you what’s happening behind the scenes.

Want to learn how Webflow handles SEO out of the box? Check out our guide to Webflow’s SEO capabilities.

And if you’d rather leave the heavy lifting to pros, our team can help. Whether you need a custom Webflow setup or ongoing growth support, we’re here as your Webflow development company.