How to Detect What Website Builder a Site Uses (2026 Guide)
2026-04-02
The tool analyzes 80+ builders including every major AI-native platform. It is free, requires no account, and handles about 85–90% of sites in under five seconds.
---
Method 2: Inspect the HTML Source
When you want to verify a result, dig deeper, or investigate a site that was not identified automatically — inspecting the page source is the most reliable manual method.
Open it with Ctrl+U on Windows/Linux or Cmd+Option+U on Mac. Then use Ctrl+F to search for platform-specific strings.
WordPress
WordPress leaks its identity through script and stylesheet paths. Search for /wp-content/ in the source — this appears in virtually every WordPress site's asset URLs (themes, plugins). Also look for /wp-includes/ in script paths and a generator meta tag reading "WordPress" followed by a version number. WooCommerce adds its own scripts under /wp-content/plugins/woocommerce/.
Webflow
Webflow injects several identifiers. Look for uploads-ssl.webflow.com or webflow.com in stylesheet URLs, and data-wf-domain, data-wf-page, or data-wf-site attributes on the html element. The Cloudfront CDN URL (d3e54v103j8qbb.cloudfront.net) for jQuery is also a common Webflow signal.
Shopify
Search for cdn.shopify.com in script sources or shopify-checkout-api-token in meta tags. Shopify's checkout scripts and product API endpoints (/cart.js, /recommendations/products.json) are also reliable signals.
Squarespace
The generator meta tag reads "Squarespace" and stylesheet URLs point to static1.squarespace.com. Squarespace also exposes itself through the X-Powered-By HTTP response header.
Framer
Framer sites load images from framerusercontent.com and inject data-framer- prefixed attributes throughout the DOM. A generator meta tag reading "Framer" is present on most Framer sites. The events script at events.framer.com is another strong signal.
Wix
Wix sites load assets from static.wixstatic.com and scripts from static.parastorage.com. A generator meta tag reading "Wix.com Website Builder" is present on most Wix sites.
Ghost
Ghost sites either use a ghost.io subdomain (managed hosting) or include a generator meta tag with "Ghost" and a version number. The /ghost/api/ path appears in network requests for CMS content.
Bubble
Bubble sites load from cdn.bubble.io and include data-bubble-* attributes on interactive elements. A Bubble-specific JavaScript namespace appears in the page's global variables.
Lovable (formerly GPT Engineer)
Lovable-generated sites often include scripts from cdn.gpteng.co or reference lovable.dev in their source. Apps deployed from Lovable typically use Supabase as their backend, so supabase.co API calls in the network tab are a supporting signal.
Bolt (by StackBlitz)
Bolt-generated sites vary by framework but are often deployed on Vercel or Netlify with no platform-specific CDN. The strongest signal is the stack: React or Vue with Tailwind CSS, Supabase for data, and a Vercel deployment — all indicators of an AI-built site even without a Bolt fingerprint.
v0 by Vercel
v0 generates Next.js components and sites are deployed on Vercel. Look for _next/static/ in script paths (Next.js) combined with Vercel-specific response headers (x-vercel-id). v0-generated components often use shadcn/ui component patterns.
Carrd
Carrd sites load assets from assets.carrd.co and include a generator meta tag reading "Carrd". They are typically single-page sites with Carrd's characteristic minimal HTML structure.
Durable
Durable sites load from assets.durable.co and include a generator meta tag. The AI-generated content structure (business name, service description, contact form) is also recognizable.
---
Method 3: Check HTTP Response Headers
HTTP headers reveal the server and hosting layer before you even look at HTML. Open DevTools (F12) → Network tab → click the main document in the list → Headers section.
| Header | What It Reveals |
These globals are set by the platform's own JavaScript and cannot be removed without breaking functionality — making them among the most reliable detection signals.
---
Method 5: Inspect Network Requests
Open DevTools → Network tab → reload the page → filter by Fetch/XHR to see API calls. The endpoints a site makes often reveal its backend:
---
Method 6: Check robots.txt and sitemap.xml
Visit example.com/robots.txt and example.com/sitemap.xml directly. These files often reveal platform paths.
WordPress robots.txt typically disallows /wp-admin/ while explicitly allowing /wp-admin/admin-ajax.php.
Webflow sitemaps are hosted at the webflow.io subdomain before custom domain setup.
Shopify robots.txt disallows /admin/ and /checkout/ paths, and the sitemap URL pattern includes myshopify.com.
Ghost includes a generator comment in sitemap files and uses ghost-sitemap paths.
---
Method 7: Use DNS Records
DNS CNAME records reveal the hosting provider even when the site uses a custom domain. Use a tool like MXToolbox or run "dig CNAME example.com" in your terminal:
---
Platform Detection Reference
| Platform | Strongest HTML Signal | JS Global | Header |