Your Webflow site showing a "Site Not Found" error despite being published with a green checkmark typically points to a domain configuration issue.
1. Check Custom Domain Settings in Webflow
- Go to Project Settings > Hosting tab.
- Under Custom Domains, ensure your domain is correctly added (e.g.,
www.example.com
). - Make sure the correct default domain is selected (ideally the
www
version). - Look for any warnings or red errors next to your custom domains—these indicate DNS misconfiguration.
2. Verify DNS Settings at Your Domain Registrar
- Log in to your domain registrar (GoDaddy, Namecheap, etc.).
- Check the A records are pointing to both:
- (a) 75.2.70.75, and
- (b) 99.83.190.102 for root domain (
@
). - Make sure
CNAME
for the www subdomain is set to proxy-ssl.webflow.com. - Avoid redirect chains between non-www and www versions—Webflow requires one domain to redirect to the other, not both looping.
3. Wait for DNS Propagation
- DNS changes can take up to 24–48 hours to propagate fully.
- Use tools like whatsmydns.net to check if the domain settings are live globally.
4. Clear Browser Cache or Try Incognito Mode
- Sometimes your browser caches the previous error state.
- Test in incognito mode or clear your browser cache.
5. Disable SSL, Re-Enable If Needed
- In Webflow Hosting tab, try turning SSL off, waiting a few minutes, and turning it back on.
- Then republish the site to both Webflow and custom domains.
6. Publish to Custom Domain Explicitly
- From the Webflow Designer or Project Settings, click Publish, then ensure your custom domain is selected along with the Webflow.io domain.
- Sometimes publishing only to the Webflow.io domain can leave the custom domain showing an error.
Summary
A "Site Not Found" error on a published Webflow site usually means your custom domain DNS is not properly configured. Double-check the A records, CNAME settings, and default domain status in Webflow, and republish to your custom domain. Use DNS testing tools to confirm everything is live.