Why am I getting a "too many redirects" error when using Google's DNS for hosting on Webflow, and what are the steps to resolve it?
- Set the www version as the default domain in Webflow and ensure SSL is enabled.
- Configure Google Domains DNS with A records (75.2.70.75, 99.83.190.102) for @, and a CNAME for www pointing to proxy-ssl.webflow.com.
- Avoid adding URL forwarding in Google Domains to prevent redirect loops.
- Allow up to 48 hours for DNS/SSL propagation and confirm redirects work correctly by testing both domain versions.
A "too many redirects" error typically means your domain is caught in a redirection loop, often caused by incorrect DNS or SSL settings when connecting a custom domain to Webflow via Google Domains (or using Google’s DNS settings).
1. Check Your Domain Configuration in Webflow
- Go to Project Settings in Webflow and click on the Hosting tab.
- Make sure your custom domain (e.g., www.example.com) is added.
- Webflow recommends setting the www version as the default domain, and this impacts redirects.
2. Confirm Proper DNS Settings in Google Domains
In your Google Domains dashboard, open the DNS settings for your domain.
Under Custom resource records or similar, set:
A records pointing to:
- (a) 75.2.70.75
- (b) 99.83.190.102
These should be assigned to the @ (root domain).
CNAME record for www pointing to proxy-ssl.webflow.com.
Do not set a forwarding rule from example.com → www.example.com in Google Domains if you're also using Webflow's default domain redirect, as these can conflict.
3. Avoid Duplicate Redirects
- If Webflow is handling the www redirect, avoid setting up an additional HTTP redirect or URL forwarding in Google Domains for the same domain.
- Doing so results in a redirection loop like: example.com → www.example.com → example.com → ...
4. Enable SSL and Wait for Propagation
- In Webflow, under the Hosting tab, make sure SSL is enabled.
- After changes, it can take up to 48 hours for DNS and SSL to fully propagate.
- Keep checking the site via incognito or with cache cleared to avoid browser-level redirect cache issues.
5. Test Default Domain and Redirects
- After DNS updates have propagated, load both example.com and www.example.com.
- Ensure that each correctly redirects to the default domain set in Webflow (usually www).
Summary
"Too many redirects" errors with Google DNS and Webflow are usually caused by conflicting redirects or incorrect DNS/SSL settings. To fix it, ensure only Webflow handles domain redirection, set www as the default domain, and use the correct A and CNAME records. Avoid setting up redundant forwarding in Google Domains.