Download websites that use WooCommerce

About WooCommerce

An online store is easy to spot from the outside and hard to qualify. Anything can put a photograph of a product on a page. What separates a shop from a brochure is the machinery underneath it, the catalogue, the cart, the tax table and the payment integration, and that machinery is what a technology scan can actually see.

WooCommerce is that machinery for a large part of the self-hosted web. Built as an extension to a content management system rather than sold as a hosted service, released under GPL v3 and owned by Automattic since some years after its 2011 debut, the plugin turns an ordinary site into a merchant. Detecting it on a domain is a stronger commercial signal than detecting a payment button, because the plugin implies inventory, order handling and an administrator who has been through a setup wizard.

As of October 2026 we detect the platform on 3,384,343 sites, 1,211,631 of them resolving to United States, mostly under .com. Alongside that we resolve 2,756 distinct version strings, with 11.2.1 the reading we record most frequently. A version spread of that size is the defining fact about self-hosted commerce. Software that a hosting company updates centrally converges on a handful of builds. Software that each merchant updates on their own schedule does not converge at all, and the tail is populated by stores that were configured once, made money, and were never touched again.

That tail carries real consequences for several different readers. A security researcher sees an exposure curve. A plugin or extension vendor sees a compatibility matrix and a support cost. An agency selling retainers sees stores that are demonstrably running unattended. A payment provider, a shipping integrator or a tax automation service sees merchants whose current configuration can be inferred from what else is detected on the same page, which is a far better qualifier than company size.

Geography changes the meaning of every one of those readings, because commerce is regulated locally. Currency, invoicing rules, consumer protection and sales tax all follow the merchant's market rather than the software, so a list of stores without countries and suffixes attached is close to useless for anyone selling a compliance sensitive product. A store on a national suffix answering from within that same country is a different prospect from a store on a generic suffix answering from a different continent, even when both run identical software.

The limits are worth naming plainly. We detect the platform from front end traces, which means aggressively cached storefronts, heavily customised themes and headless setups where the shop is rendered by a separate application can all escape us, so the count is a floor. A detected store is not necessarily an active store, since abandoned shops keep serving markup for years. We cannot see revenue, order volume or catalogue depth, and no scan of a public page ever will. Anyone who tells you otherwise is modelling, not measuring.

Given those limits, the value of a downloadable list is specifically that it answers a population question rather than a per-site one. Checking one domain tells you a competitor's supplier. An export tells you how many merchants exist in a chosen market, on a chosen suffix, running alongside a chosen payment or analytics stack, which is the input to territory planning, partner recruitment and pricing work. Fetched one domain at a time, that answer costs more than it is worth. Downloaded as a single file, the same answer is a morning's work in a spreadsheet.