How to Tell if a Website Is Built with Wix or Squarespace

Need to tell whether a site is built with Wix or Squarespace — and which one? Both are hosted website builders that leave clear, distinct fingerprints, so distinguishing them is usually a matter of one quick check. The single fastest discriminator is the response header: a Server: Squarespace header means Squarespace, while an X-Wix-Request-Id (or any X-Wix-* header) means Wix. Back that up with asset domains — static.wixstatic.com for Wix, static1.squarespace.com for Squarespace — and the generator meta tag each one sets, and you have a conclusive answer. This guide gives you every signal side by side, plus what confirming either platform tells you.

This is a focused companion to how to tell what website builder a site uses; here we concentrate on telling these two apart.

What Wix and Squarespace are

Both are hosted, all-in-one website builders aimed at people who want a professional site without writing code. They bundle templates, a visual editor, hosting, a domain, and built-in features like blogs, stores and forms into a single subscription. Squarespace is known for its polished, design-led templates and is a favourite of portfolios, photographers, restaurants, boutiques and creatives who want something that looks good out of the box. Wix offers a more freeform, drag-anywhere editor and an enormous app market, appealing to small businesses and sole traders who want flexibility and lots of add-ons. Confirming either one tells you the same essential fact: the site was assembled from templates on a managed platform, not hand-coded or self-hosted — which shapes how it can be edited, extended and migrated.

The fastest discriminator: response headers

The quickest way to tell them apart is to read one header. Run curl -I https://example.com from a terminal, or open DevTools (F12) → Network tab, reload, and click the document request to read its Response Headers. The decisive lines:

• Squarespace returns a clean Server: Squarespace header. This is unusually candid — most platforms hide behind a generic or CDN server value — which makes it arguably the single cleanest tell in the entire builder category.
• Wix sets X-Wix-* headers, most reliably X-Wix-Request-Id, and often others. Wix also typically sits behind its own infrastructure, but the X-Wix- prefix is the giveaway.

One curl -I usually distinguishes the two outright. If you see Server: Squarespace, you are done; if you see X-Wix-Request-Id, likewise. Headers come straight from the server and cannot be styled away, which is why they are the most trustworthy starting point. For more on reading them, see how to read a website's HTTP headers.

Asset domains and generator tags

The headers are confirmed by where each platform serves its assets and by the generator tag in the source. Open the Network tab and watch the domains, or View Source (Ctrl+U) and search for generator and the asset hosts:

Wix:

• Assets from static.wixstatic.com (images and media) and static.parastorage.com (scripts and platform code).
• A generator meta tag: <meta name="generator" content="Wix.com Website Builder" />.
• A _wixCIDX cookie and other Wix cookies in the Application tab.
• Unpublished sites on *.wixsite.com subdomains.

Squarespace:

• Assets from static1.squarespace.com and images from images.squarespace-cdn.com.
• A generator meta tag: <meta name="generator" content="Squarespace" />.
• Many pages respond to a ?format=json query with JSON — a Squarespace-specific behaviour.
• Config and template hints under /config and Squarespace's own script bundles.

Seeing wixstatic.com assets with an X-Wix header, or squarespace-cdn.com images with a Server: Squarespace header, is a textbook two-point confirmation.

Side-by-side comparison

Here are the two platforms' fingerprints next to each other, which is the quickest reference when you have a site open.

Signal type	Wix	Squarespace
Response header	X-Wix-Request-Id, other X-Wix-*	Server: Squarespace
Asset domain	static.wixstatic.com, static.parastorage.com	static1.squarespace.com, images.squarespace-cdn.com
Generator tag	"Wix.com Website Builder"	"Squarespace"
Cookie tell	_wixCIDX and other Wix cookies	Squarespace session cookies
Staging domain	*.wixsite.com	*.squarespace.com (built-in domain)
Special behaviour	freeform editor markup	?format=json returns JSON

Reading one row from each column — a header and an asset domain, say — gives you a confident identification. The platforms are different enough that signals rarely conflict.

Methods, step by step

The practical sequence is short and works for either platform:

1. curl -I the URL (or read Response Headers in the Network tab) and look for Server: Squarespace or X-Wix-*.
2. View Source and search for the generator tag and the platform's asset domain.
3. Watch the Network tab for wixstatic.com / parastorage.com versus squarespace-cdn.com requests.
4. Check cookies in the Application tab (_wixCIDX for Wix).
5. For Squarespace, try appending ?format=json to a page URL and see whether JSON comes back.
6. Check the domain for a *.wixsite.com staging address.

Most of the time the first step alone tells you which of the two you are looking at; the rest are corroboration.

Tools that detect them automatically

If you would rather click than inspect, the standard detectors recognise both platforms:

• Wappalyzer — the browser extension reports "Wix" or "Squarespace" for the current page.
• BuiltWith — profiles the domain and names the builder, with history on paid tiers.
• View Source, DevTools and curl -I — the manual tools behind the automated answer, and how you verify it.
• StackOptic — a full website audit that identifies the builder alongside hosting, performance, SEO and accessibility in a single report.

These tools read the same headers, asset domains and generator tags you can read yourself, so confirm an important result with a quick manual check.

Detecting the store: Wix Stores versus Squarespace Commerce

Both platforms also power online shops, and the commerce layer carries its own tells on top of the builder fingerprints. A Wix Stores site is still a Wix site underneath — the X-Wix-* headers and static.wixstatic.com assets remain — but it adds Wix Stores widgets and product markup, and its cart and checkout run on Wix's own commerce infrastructure. A Squarespace Commerce store likewise keeps the Server: Squarespace header and squarespace-cdn.com assets, while adding commerce-specific markup, product URLs and a Squarespace-hosted checkout. So the detection sequence is two-layered: first confirm the builder from the headers and asset domains, then look for the commerce widgets and checkout to establish that it is a store rather than a brochure site. Because the underlying platform does not change when you add a shop, the builder signals you already trust still apply — the commerce markers simply sit on top. This is the same layered logic that governs e-commerce detection generally, where the platform and the store are separate questions you answer in turn.

Performance and SEO implications of each

Identifying the builder is also a useful starting point for a performance or SEO conversation, because hosted builders make their own trade-offs. Both Wix and Squarespace handle hosting, security and updates for you, which is a genuine convenience, but they also ship a fair amount of platform JavaScript and templated markup that you cannot fully control. Squarespace's design-forward templates can be image-heavy, and Wix's freeform editor can produce pages with more script than a hand-built equivalent. Neither fact condemns the platforms — both can host fast, well-ranked sites — but it does mean that once you have confirmed the builder, the natural next checks are the page weight, the Core Web Vitals and the rendered HTML. Because you cannot edit the platform's own code, optimisation on these builders centres on the levers you do control: image sizes and formats, the number of apps or blocks you add, and your content structure. Knowing which builder you are on tells you exactly which knobs are available and which are locked, which is precisely the kind of context a full audit surfaces.

Common mistakes when distinguishing them

A few traps recur. Reading a CDN or generic Server header as conclusive — Wix does not always expose a friendly Server value, so rely on the X-Wix-* prefix rather than the bare server name. Mistaking an embedded widget for the platform — a site can embed a Wix or Squarespace form or store widget without being built on it, so check that the page's own assets and headers match. Confusing either with a self-hosted CMS — neither is WordPress, so the absence of /wp-content/ is expected and not a clue in itself; if you are unsure whether you are even looking at a builder, start with how to tell what CMS a website is using. And stopping at one ambiguous signal — corroborate a header with an asset domain before committing.

Why these two get compared so often

Wix and Squarespace are the two builders people most often weigh against each other, which is exactly why telling them apart is a common task. They occupy the same market — non-technical users who want a managed, template-based site — but with different philosophies: Squarespace leans on curated, design-forward templates and a more structured editor, while Wix offers a freeform, drag-anywhere canvas and a sprawling app market. That difference shows up in the output, too. A Squarespace site tends to feel consistent and tightly designed; a Wix site can be more idiosyncratic because of the freeform editor. Even before you read a header, that feel can hint at which to check for first — though the header always settles it definitively. For the third major builder aimed at a more design-savvy audience, see how to tell if a website is built with Webflow.

What confirming the platform tells you

Once you know which builder a site uses, useful conclusions follow. The site is hosted on the platform, so its performance, uptime and security are managed by Wix or Squarespace rather than a separate host. Content and design are edited in the platform's own editor, not a code repository or a traditional CMS dashboard. The build was almost certainly done without hand-coding the front end, often by the business owner or a designer rather than a developer. And migration away from either platform is a known quantity — an export-and-rebuild rather than a code port. For competitive research, scoping a redesign, or simply understanding what you are dealing with, identifying Wix or Squarespace gives you that context immediately. The broader skill of reading these signals across all platforms is covered in how to find out what a website is built with.

The fast, reliable workflow

1. curl -I or read Response Headers: Server: Squarespace versus X-Wix-Request-Id.
2. View Source: find the generator tag and the asset domain.
3. Network tab: wixstatic.com/parastorage.com versus squarespace-cdn.com.
4. Squarespace check: append ?format=json and look for a JSON response.
5. Wix check: look for the _wixCIDX cookie and any *.wixsite.com domain.
6. Cross-check two signals — a header plus an asset domain — before concluding.

Go deeper

• The general question: how to tell what website builder a site uses.
• The design-led builder: how to tell if a website is built with Webflow.
• The complete method: how to find out what a website is built with.
• The header skill behind it: how to read a website's HTTP headers.

Want the builder, hosting and full stack identified in one pass? Analyse any website with StackOptic — one report, free, no sign-up.