If changes appear correctly on your Webflow.io staging domain but not on your custom domain, this usually indicates an issue with domain configuration or cached content.
1. Check DNS Settings
- Go to Project Settings > Hosting, and review the instructions under Custom Domains.
- Ensure your custom domain's DNS settings include:
- A records pointing to Webflow’s IPs: (a) 75.2.70.75, (b) 99.83.190.102.
- CNAME record (for
www.domain.com
) pointing to proxy-ssl.webflow.com. - Make sure you only use the correct records—extra or incorrect DNS entries can cause propagation or routing issues.
2. Ensure SSL Is Enabled
- In Project Settings > Hosting, make sure SSL is turned on.
- If you recently enabled SSL, DNS records may need up to 48 hours to propagate.
- After enabling SSL, republish the site to all domains.
3. Set the Default Domain Correctly
- In Hosting settings, make sure the desired custom domain (typically
www.domain.com
) is set as Default. - If the root domain (
domain.com
) is being used without proper redirects, it can cause issues. - Webflow recommends using the www version as the default and redirecting the root domain to it.
4. Clear Cache or Try Incognito
- Your browser may be loading an older cached version of the site on the custom domain.
- Try viewing the site in incognito/private mode, or clear browser cache.
- You can also bypass caches by adding a query string like
?nocache=1
to your URL.
5. Check for CDN Propagation Delay
- Custom domains go through Webflow’s Amazon CloudFront CDN, which may introduce short delays (usually under 15 minutes).
- If the issue just started, wait a bit and verify again.
6. Disable and Re-enable Custom Domain Publishing
- In the Publish dialog, uncheck your custom domain, publish only to
webflow.io
, then wait 1–2 minutes. - Then re-select and publish to the custom domain. This can often force refresh the deployment.
Summary
If your Webflow.io domain reflects updates, but your custom domain doesn't, it's likely due to DNS mismatches, caching, or CDN delay. Ensure correct DNS setup, clear your browser cache, and verify SSL and default domain settings. Re-publishing with adjusted settings often resolves the issue.