Your Webflow site may show a "site not found" error even when published if there’s a mismatch or error in the custom domain setup or DNS records.
1. Confirm the Correct Default Domain
- Go to Project Settings > Hosting.
- Check which domain is marked as the default domain (it should have a blue “Default” label).
- Make sure the preferred domain (e.g.,
www.yoursite.com
) is selected as default if both root and subdomain are configured.
2. Verify DNS Settings with Your Domain Registrar
- Go to your domain registrar (e.g., GoDaddy, Namecheap).
- Ensure the following DNS records are correctly set for a Webflow custom domain:
- A Records: Point the root domain (e.g.,
yourdomain.com
) to Webflow’s IPs:- (a) 75.2.70.75
- (b) 99.83.190.102
- CNAME Record: For the
www
subdomain:- Target:
proxy-ssl.webflow.com
3. Wait for DNS Propagation
- DNS changes may take time to propagate (up to 48 hours, usually less).
- Use tools like whatsmydns.net to check if the new records have propagated globally.
4. Check Webflow Domain Status
- In Project Settings > Hosting, at the bottom of the page, review the Domain Status indicators.
- A green check means domains are correctly setup. Click "Check status" to force an update if you recently changed records.
5. Use the Correct URL
- Make sure you’re accessing the site via the published default domain.
- If only the
www
version works, the root domain may not be correctly redirecting.
6. HTTPS Settings
- Ensure SSL is enabled under Project Settings > Hosting.
- If SSL is enabled and DNS records are correct, Webflow will automatically provision HTTPS certificates.
Summary
Even if your Webflow site shows a green check mark, a "site not found" error usually stems from incorrect DNS configuration or the wrong default domain set in Webflow. Double-check that your DNS records match Webflow’s requirements and that the correct domain is marked as default.