BuiltWith or other site profiling tools may still show WordPress as the CMS after migrating to Webflow due to leftover infrastructure, caching, or misconfigured DNS settings.
1. Check DNS Propagation and Domain Connection
- Ensure Webflow is correctly connected: In Webflow Project Settings > Hosting, verify that the domain is marked as ✔ Connected.
- Check correct DNS settings: On GoDaddy, make sure you've added:
- A records: (a) 75.2.70.75, (b) 99.83.190.102
- CNAME record: For
www
, pointing to proxy-ssl.webflow.com
- Use whatsmydns.net to see if DNS is fully propagated.
2. Clear Caches and CDN Layers
- Browser & device caches may still show content or details from the previous WordPress site.
- GoDaddy or third-party CDN (like Cloudflare) may still serve cached headers or pages — check and purge any existing caches.
- Use httpstatus.io to inspect headers and ensure they are being served by Webflow.
3. Check for Old WordPress URLs and Headers
- Make sure no old WordPress assets or URLs are still accessible (e.g.,
/wp-content/
, /wp-login.php
). - Webflow does not produce WordPress-style headers. If BuiltWith detects WordPress, it might be analyzing outdated or cached header information.
- Test using multiple tools like BuiltWith, Wappalyzer, or Netcraft to confirm.
- Run
curl -I yourdomain.com
and check for headers that indicate Webflow hosting (like x-powered-by: Webflow
) versus WordPress-specific indicators.
5. Check for Hosting Overlap
- It’s possible the WordPress hosting is still active, especially if you didn’t disable or remove the old hosting on the server. BuiltWith might still be hitting the WordPress origin instead of the new Webflow deployment.
Summary
If BuiltWith still shows WordPress, check for DNS misconfiguration, stale caches, or residual access to your old WordPress hosting. Make sure Webflow fully serves your domain, and no WordPress files or headers are still accessible. Once cleaned up, BuiltWith should update its results after their next scan.