What Website Builder Is This? How to Detect Wix, Squarespace, Webflow & More

Website builders are some of the easiest platforms to identify, because each one serves its assets from a signature domain and usually declares itself right in the page source. If you have ever wondered "what was this site made with?", the answer is often a glance away. This guide covers the exact tells for the major builders — Wix, Squarespace, Webflow, GoDaddy, Weebly, Framer, Carrd and Google Sites — and how to read them in seconds.

For the broader method behind all platform detection, see how to find out what a website is built with; here we focus on builders.

Why identify the builder?

Knowing the builder tells you a lot about a site at a glance: its likely cost and flexibility, how it was made, and who made it. Designers and agencies scope redesigns and migrations around it. Competitive researchers learn whether a rival is on a quick drag-and-drop tool or a more capable platform. Freelancers find prospects on a specific builder. And anyone evaluating a vendor can sanity-check the kind of site they actually ship. There is a research angle too: studying which builders rank well for a given niche tells you what is achievable on each platform before you commit to one. Two signals do most of the heavy lifting — the asset domain and the generator meta tag — and the rest of this guide is mostly about knowing what those signals look like for each platform.

Wix

Wix is unmistakable once you know the tells:

• Assets load from static.wixstatic.com and static.parastorage.com.
• The generator tag reads <meta name="generator" content="Wix.com Website Builder">.
• A wix-warmup-data script block and a global wixBiSession appear in the source.
• X-Wix-* response headers (such as x-wix-request-id) confirm the platform server-side.

Any one of these strongly implies Wix; together they are conclusive.

Squarespace

Squarespace has an equally clear signature:

• Assets load from static1.squarespace.com.
• The generator tag reads Squarespace.
• A SQUARESPACE_ROLLUPS object and Static.SQUARESPACE_CONTEXT data appear in the source.
• Response headers frequently include a squarespace-flavoured server value.

Squarespace sites tend to share a recognisable structural polish, but you never need to guess — the asset domain settles it.

Webflow

Webflow is popular with designers and leaves distinctive markup:

• Assets load from assets.website-files.com (and unpublished sites live on *.webflow.io).
• The HTML element carries data-wf-page and data-wf-site attributes.
• A Powered by Webflow generator tag is present unless removed.

One caveat: Webflow lets you export a static site and host it anywhere. An exported site loses the hosted asset domain and may drop the generator tag, leaving the data-wf-* attributes and class-naming conventions as the surviving clues.

A note on builder versions and tiers

The major builders have generations worth distinguishing. Squarespace sites are either 7.0 (template-family based) or the newer 7.1 (unified templates with the Fluid Engine layout) — the version surfaces in template class names and context data. Wix spans the classic Editor, the older Editor X, and the newer Wix Studio, plus Wix ADI (the AI-built option); the asset domains are shared, but the markup structure differs between them. Webflow layers a CMS and Ecommerce capability on top of its visual editor, which you can spot from CMS collection markup and commerce-specific attributes. Pinning down the exact generation sharpens any migration estimate or competitive read.

GoDaddy, Weebly, Framer, Carrd and Google Sites

The smaller and newer builders are just as identifiable:

Builder	Primary tells
Wix	static.wixstatic.com, generator Wix.com Website Builder, wix-warmup-data
Squarespace	static1.squarespace.com, generator Squarespace, SQUARESPACE_ROLLUPS
Webflow	assets.website-files.com, data-wf-page, generator Powered by Webflow
GoDaddy Website Builder	img1.wsimg.com assets, GoDaddy/Starfield infrastructure tells
Weebly	editmysite.com assets, _W global object, generator Weebly
Framer	framerusercontent.com assets, framer markers in the source
Carrd	single-page structure, carrd asset references
Google Sites	sites.google.com host, Google static asset domains

A single matching asset domain from this table is usually enough to name the builder with confidence.

What the builder tells you about a site

Identifying the builder is a shortcut to several conclusions. It signals the likely budget and effort: a Carrd or free-tier Wix site sits at one end, a Webflow or Wix Studio build at the other. It hints at flexibility and limits — drag-and-drop platforms trade some control for speed, which affects what a redesign can realistically achieve. It shapes SEO and performance expectations, since each platform has its own rendering and markup characteristics. And it suggests who built it: agencies gravitate toward Webflow and Wix Studio, while small-business owners often self-serve on Wix, Squarespace or GoDaddy. For sales, partnerships or competitive work, that profile is frequently more actionable than the visual design.

Thinking about migrating off a builder?

Detection is often the first step before a migration. Each builder has its own export story. Squarespace and Wix are largely closed systems, so moving usually means rebuilding content on the new platform rather than exporting templates cleanly. Webflow can export static HTML and CSS, though its dynamic CMS and commerce features do not come along. Knowing the source builder tells you how much of the project is content migration versus a full rebuild, what URL redirects you will need to protect SEO, and whether the design can be preserved or must be recreated. That is the difference between a weekend job and a multi-week one — which is exactly why scoping it accurately up front pays off.

Builder vs CMS vs framework

It is worth separating three concepts people often conflate. A website builder (Wix, Squarespace, Webflow) is an all-in-one hosted platform for designing and publishing without code. A content management system such as WordPress focuses on managing content and is frequently self-hosted. A JavaScript framework such as React or Vue is a developer tool for building interfaces. A site runs essentially one builder, but a builder-made page can still embed a framework for interactive components — so detecting a framework does not contradict detecting a builder. (If you suspect a framework, see how to check if a website uses React, Vue, or Angular.)

How to check without developer tools

You do not always need devtools. On desktop, "View Page Source" (Ctrl/Cmd + U) shows the asset domains and the generator tag in plain text — a quick Ctrl/Cmd + F for "wixstatic", "squarespace" or "website-files" usually answers the question outright. On mobile, view-source is awkward, so the easiest route is a detection tool you can open in any browser: paste the URL and read the result. That is also the most efficient approach when you are checking many sites in a row and do not want to inspect each one by hand.

When the signals are hidden

Detection gets harder when a site has been exported and self-hosted (the Webflow case), sits behind a reverse proxy or CDN that rewrites headers, or uses a custom domain with aggressive caching. None of these fully erase the platform: builder-specific class names, leftover data- attributes, and structural conventions usually survive. As always, corroborate two independent signals before you commit to an answer.

Common mistakes when identifying a builder

A few traps lead to wrong calls. Confusing an embedded widget for the platform is the classic one — a WordPress site can embed a Typeform or a Wix booking widget without being built on either. Reading a third-party script as the builder: analytics, chat and marketing tags belong to tools layered on top, not the platform itself. And trusting a single class name: generic utility classes are shared across many tools, so anchor on the asset domain or generator tag, not on styling alone. When two independent builder signals disagree, the asset domain that serves the bulk of the page's own assets is almost always the real platform.

How accurate is builder detection?

Builder detection is among the most reliable forms of web fingerprinting, because builders are hosted platforms that serve from their own infrastructure and rarely hide it. The main accuracy gap is exported static sites, where the hosted tells are stripped by design. Outside that case, an asset domain plus a generator tag is close to definitive.

The fast, reliable workflow

1. Read the asset domains in the Network tab or source — they often name the builder directly.
2. Check the generator meta tag in the <head>.
3. Search the source for builder globals and data- attributes (SQUARESPACE_ROLLUPS, data-wf-page, wix-warmup-data).
4. Glance at the response headers for builder-specific entries.
5. Cross-check two signals before concluding — especially for sites that may have been exported.

Go deeper

• The full method: how to find out what a website is built with.
• Selling online? How to tell if a website is built with Shopify.
• Suspect a framework underneath? How to check if a website uses React, Vue, or Angular.

Skip the manual checks — analyse any website with StackOptic to identify its builder, CMS, framework and full stack in one report, free.