Download websites that use WooCommerce Blocks

About WooCommerce Blocks

Some software gets installed on purpose and some arrives attached to something else. WooCommerce Blocks is mostly the latter. Published in 2019 by Automattic under GPL v3 and written in JavaScript, the extension brings WooCommerce product grids, filters, cart and checkout into the WordPress block editor, and on most stores it lands as part of a routine WooCommerce update rather than as a decision anyone made.

The distinction changes what a detection actually means. A merchant did not shop for the component, so its presence is not a taste signal, and the release a store carries becomes a proxy for maintenance discipline instead. Across the detected population we track 35 distinct release strings, and 1.4.0 recurs often enough to show how much of the base sits well behind the current development line. Stores that defer one update tend to defer all of them, so an old build here usually travels with an old payment gateway, an old theme and an aging server runtime.

For several kinds of buyer that maintenance signal is the product. Security researchers use it to bound the exposure of a known issue in a specific release band. Plugin and theme vendors use it to decide which builds they still have to support. Agencies selling maintenance retainers use it to find stores that visibly need one, and payment providers use it to find merchants whose checkout is old enough to be worth replacing.

There is another reading of the same tag, and the reading is architectural. A store that renders its catalogue through blocks is a store whose front end is assembled in the editor rather than written into a bespoke theme, which changes both who can be sold to and what can be sold. Editor built storefronts are usually owner maintained or handled by a small agency, they accept new components readily, and they are cheap to modify. A bespoke theme means a developer relationship, a longer sales cycle and a higher bar for anything that wants to be added.

As of October 2026 we record the extension on 56 sites, and a caveat belongs next to the number. Detection depends on block assets actually being emitted on a page we fetch, so a store whose scanned pages carry no block based storefront content can run the extension without showing it. The count is therefore a lower bound, and it should not be read as a count of merchants who chose the WordPress plugins component deliberately, since for most of them the choice was made upstream.

A per domain lookup answers whether a particular shop runs the extension and which release it reports. The downloadable file answers the questions that only exist at population scale, such as how the release distribution is shaped, how quickly a new line displaces an old one, which segment of the WooCommerce base updates and which does not, and where unmaintained stores are concentrated enough to build an outreach campaign or a research paper on.