Download websites that use Squarespace Commerce

About Squarespace Commerce

This entry covers the commerce capability rather than the website platform underneath it, and the distinction is worth making explicitly because our current figures do not separate the two as cleanly as they should. As of September 2026 the detection count stands at 9,173,707 sites, which currently tracks the parent platform closely rather than isolating stores that have actually enabled selling.

We would rather flag that than let the number be read as a store count. The commerce layer shares scripts, asset paths and markup with the wider platform, so a fingerprint that is reliable for one is prone to over-matching the other. Anyone sizing an addressable market from this row specifically should treat it as an upper bound and qualify further using the signals that only appear on an actual storefront: a cart, a checkout path, a payment integration or a commerce-specific analytics event.

That qualification is possible with the export precisely because it carries every detection on a domain rather than a single label. A store with payment tooling, a shipping integration and transactional email attached is a real merchant. A row carrying only the platform is a website that happens to sit on infrastructure capable of selling.

Read with that discipline, the population is a useful one. Merchants on a hosted commerce platform have outsourced the technical problems and concentrated their remaining decisions into a narrow band of apps, themes and payment choices. If you sell into that band the qualification rate is high. If you sell infrastructure it is close to zero, and knowing which side you are on before building a campaign is worth more than the raw count.

Geographically United States accounts for 8,877,447 of detections, which on a hosted platform describes serving infrastructure rather than merchant location. The .com zone leads, consistent with a commercially motivated customer base.

The wider pattern to take away is that hosted commerce populations are always defined by what sits around the platform rather than by the platform itself. Uniform infrastructure means uniform fingerprints, and every commercially meaningful difference between two stores lives in the layer they added on top.

The general lesson here applies well beyond this one entry. Whenever a capability is delivered as part of a larger platform rather than as a separate installation, its detection boundary is fuzzy, and any count published without that caveat will be too high. We would rather carry the row with an explicit warning than either drop it or quietly present an inflated figure as fact.

For anyone building on this data, the workable approach is to treat platform detections as the starting population and commercial detections as the qualifier. A cart, a payment provider, a shipping calculator or a transactional email service each independently confirm that selling is actually happening, and requiring two of them removes almost all of the false positives that a platform-level fingerprint introduces.

Squarespace operates the platform under a Proprietary model and the commerce capability has been part of the offering since 2013.