Your Webflow site may show a “site not found” error even after publishing if your custom domain isn’t properly configured or DNS changes haven’t fully propagated.
1. Verify Custom Domain Is Correctly Connected
- Go to Project Settings > Hosting and scroll to Custom Domains.
- Ensure the main domain is set as the default domain (indicated by “default domain” label).
- Check whether both the www version and root domain are added (e.g.,
www.example.com and example.com).
2. Confirm DNS Records Are Set Properly
- For A records, use Webflow’s required IPs:
(a) 75.2.70.75,
(b) 99.83.190.102
- For the www CNAME record, point it to proxy-ssl.webflow.com.
3. Check SSL Settings
- In Project Settings > Hosting, ensure SSL is enabled.
- If you made recent changes, click Save, then Publish again.
4. Allow Time for DNS Propagation
- DNS changes can take up to 48 hours, though most resolve within a few minutes to hours.
- Use tools like whatsmydns.net to check global DNS propagation.
5. Publishing to the Correct Domain
- When clicking Publish, double-check that your custom domain is selected, not just the Webflow.io staging domain.
6. Clear Cache or Use a Private Window
- Sometimes your browser may cache an old version.
- Open your site in Incognito mode or a different browser to test.
Summary
To resolve the "site not found" error, make sure your custom domain is properly configured with the correct DNS records, set as the default domain, and has been allowed time to propagate. Also, verify you're publishing to the correct domain and SSL is enabled.