Download websites that use GoDaddy CoBlocks

About GoDaddy CoBlocks

Some software on a website was chosen and some of it simply arrived. GoDaddy CoBlocks belongs mostly to the second group, and reading this list correctly depends on holding that difference in mind.

The plugin is a block library for the WordPress editor, written in PHP and published under GPL v2 by GoDaddy Inc. since 2018. The block set extends the native editor with layouts, galleries, pricing tables, carousels and form elements, so a site owner can assemble a page without buying a separate page builder. Nothing about the code is unusual. What makes the population interesting is the distribution channel.

The vendor is a registrar and a hosting company before it is a software publisher, and the blocks ship inside the themes and onboarding flows sold to its own customers. Presence on a site therefore says more about where the site is hosted and which plan it was bought on than about any technical evaluation. A site owner who has never heard the plugin's name can be running it on every page.

Bundled distribution also changes what the technology predicts. A deliberately installed plugin tells you about a builder's taste, while a bundled one tells you about a purchase. Sites in this group tend to share the rest of their stack as well, because the same onboarding installs the same analytics, the same contact form and the same commerce path, which is why cross referencing this cohort against other fields produces cleaner segments than most editor plugins do.

The geography follows directly. As of October 2026 we detect the blocks on 62,568 sites, of which 57,001 sit in United States, and the domain mix leans heavily toward .com. The concentration is a property of the seller's customer base, which is small and medium businesses buying a domain and a website in one transaction, rather than a property of the software. Comparable block libraries with no hosting company behind them spread far more evenly across markets.

For a commercial researcher this makes the segment unusually well defined. Filtering a dataset to this technology returns a cohort of small business sites on a managed WordPress stack, mostly commercial, mostly assembled rather than engineered, and reachable through a predictable set of contact patterns. Hosting companies use cohorts like this for migration campaigns, theme and plugin vendors use them to size an addressable market inside one host's estate, agencies use them to find sites that have outgrown a builder, and analysts use them as a rough proxy for one hosting brand's share of a national small business web.

Two limits deserve stating plainly. Detection depends on block markup and stylesheet handles being present on the page that was fetched, so a site running the plugin that renders no blocks on the page we saw will be missing, which pushes the total down. In the other direction, a deactivated plugin can leave cached assets behind in a theme for months. The honest description of the number is a well sized cohort of hosting customers rather than an exact install count, and for the questions people actually ask of it, the difference rarely matters.