Download websites that use Kadence WP Blocks

About Kadence WP Blocks

Software that updates itself should converge on a single release. Kadence WP Blocks has not converged. Across the sites where we detect it we record 28 distinct versions, with the centre of gravity sitting at 2.4.22. A spread that wide inside one plugin population says something useful before any other fact is introduced, because it means automatic updates are switched off, sites are frozen deliberately, or the installs belong to owners who stopped paying attention after launch.

The plugin itself is a block library. Built by Kadence WP in 2019 and distributed under GPL v2, written in PHP on the WordPress side, it extends the native block editor with the layout pieces core leaves out, including accordions, info boxes, icon lists, tabs and carousels along with typography and spacing controls. Site builders reach for it when they want page builder capability without adopting a separate page builder, and it pairs naturally with the theme from the same house.

Presence therefore carries an intent signal that a generic plugin does not. Somebody was designing marketing pages in the block editor rather than writing posts, which points at a business site with landing pages, service pages and a person or agency responsible for them. As of October 2026 the plugin is detected on 61,175 sites, 29,702 of which are attributed to United States, with .com dominant among the domain endings. Concentration in an English speaking market fits a product sold mainly through the WordPress agency and freelancer channel.

The version spread matters again when you look at why people buy this kind of list. Security researchers want the tail rather than the head, because a block plugin renders on the public page and old rendering code is exactly where markup and script issues live. Agencies want the tail for the opposite reason, as an install running a release several generations behind is a site whose owner has no retainer. Vendors of competing block libraries want the head, since a current version means an active build worth pitching against.

Honesty about the detection matters here more than usual. A block plugin leaves a trace on a page only when one of its blocks actually renders there, so a site that uses it deep in the structure while keeping a plain home page can be missed entirely. Aggressive caching and asset optimisation plugins merge and rewrite the very stylesheet and script files a version reading depends on, which can hide the plugin or leave a stale version string behind. The count should be treated as a floor, and the version distribution as strong evidence about the sites where the marker survived rather than a perfect inventory.

Those limits are also why a per domain lookup answers so little. Checking one site tells you it uses the plugin, which you often already suspected. The population file answers the questions that only exist in aggregate, such as how many installs sit behind the current release, which theme and commerce stack travel with the plugin, which countries and domain endings the users cluster in, and how the version curve shifts from one snapshot to the next. Those are segment questions, and a segment cannot be assembled one domain at a time.