After migrating from WordPress to Webflow and updating your GoDaddy domain, some users notice that BuiltWith still shows WordPress as the CMS. This can happen due to caching issues, incomplete DNS propagation, or leftover server headers from previous hosting environments.
1. Check DNS Propagation
- Use a DNS checker tool (like whatsmydns.net) to ensure your domain points only to Webflow’s IPs:
(a) 75.2.70.75, (b) 99.83.190.102.
- If your domain still points to old WordPress server IPs in some regions, BuiltWith may be seeing outdated records.
2. Inspect HTTP Headers
- Use a tool like SecurityHeaders.com or your browser’s Inspect > Network tab to check for:
- “x-powered-by: WordPress” or similar indicators.
- These may be remnants from the previous host or improperly cached CDN headers.
3. Clear Third-Party CDN or Caching Layers
- If you're using Cloudflare or another caching/CDN service, clear the cache fully.
- Make sure it’s delivering Webflow content and not proxying old WordPress responses.
4. Confirm Complete Migration
- Ensure you’re not embedding any WordPress assets (stylesheets, scripts, etc.) in the Webflow site or using iframes that load WordPress-powered pages.
- Check the page source (Ctrl+U) to verify Webflow’s class structure and no WordPress-related metadata.
5. Request a Re-Scan from BuiltWith
- Go to BuiltWith Technology Lookup, enter your domain, and submit a Refresh Scan at the bottom of the report.
- BuiltWith may take time to update if they have the site cached.
Summary
If BuiltWith still shows WordPress after migrating to Webflow, check your DNS propagation, cache layers, and server headers, and trigger a re-scan on BuiltWith. Ensure no WordPress assets or headers are still present in your final deployment.