Has anyone experienced a situation where after migrating a WordPress site to Webflow and connecting the domain from GoDaddy, BuiltWith still shows WordPress as the CMS instead of Webflow?
TL;DR
- Confirm DNS has fully propagated to Webflow IPs using tools like DNS Checker.
- Remove all legacy WordPress metadata, HTTP headers, and redirects from your site and hosting setup.
- Verify Webflow is actively hosting your domain and no old server records remain in GoDaddy’s DNS settings.
- Use tools to check for leftover references and request a re-scan on BuiltWith.
When migrating from WordPress to Webflow and pointing a domain from GoDaddy, it's possible that services like BuiltWith still detect WordPress due to leftover server responses, DNS caching, or unremoved files.
1. Check DNS Propagation
- DNS changes can take up to 48 hours to fully propagate. During this time, some tools might still hit the old server.
- Use online tools like DNS Checker or What's My DNS to confirm that your domain is resolving to Webflow’s IPs:
(a) 75.2.70.75,
(b) 99.83.190.102.
2. Clear or Remove Legacy WordPress References
- If your WordPress site had plugins like Yoast SEO or embedded JSON-LD structured data referencing WordPress, these may still appear if:
- You exported and re-used the same content on Webflow without stripping old metadata.
- Third-party services have cached the old metadata.
- Inspect your Webflow site’s source code (in-browser) to confirm all meta tags, comments, or headers referring to WordPress are removed.
3. Investigate HTTP Headers
- Tools like SecurityHeaders.com or curl can show if any HTTP headers (e.g.,
X-Powered-By: WordPress) are still being served. - If you used Cloudflare or a proxy CDN, ensure it isn’t caching and serving legacy headers or content.
4. Re-Scan on BuiltWith and Similar Tools
- BuiltWith might display outdated data if its spider hasn’t re-crawled your updated site.
- You can request a re-scan on BuiltWith by visiting their site and submitting a new scan.
5. Ensure Webflow Hosting is Active
- In Webflow → Project Settings → Hosting, verify that:
- The domain is connected and set as the default domain.
- Webflow is confirmed as handling hosting (green “Connected” status).
6. Check for Mixed Hosting or Misconfigured Redirects
- Ensure that your GoDaddy DNS settings do not have extra A or CNAME records pointing to old WordPress hosting environments.
- Remove any legacy 301 redirects that point back to WordPress-hosted URLs.
Summary
If BuiltWith shows WordPress after a Webflow migration, the most common causes are DNS propagation delays, cached metadata, or residual WordPress headers. Confirm Webflow hosting is active, clean your site content of legacy tags, and request a BuiltWith re-scan.