Download websites that use SiteOrigin Page Builder

About SiteOrigin Page Builder

Page builders are sediment. A site's builder tells you roughly when it was made and how much attention it has had since, because the builder is the one component that survives theme changes, content rewrites and hosting moves. SiteOrigin Page Builder belongs to the generation that arrived before the block editor, released in 2012 by SiteOrigin and given away under GPL v2, and finding it on a domain today usually means the site was assembled a long time ago and has been left to run.

Leaving it alone is rational, which is the part outsiders get wrong. A builder stores its layouts in its own structures inside the database rather than as portable markup, so moving to blocks or to another builder means rebuilding pages by hand instead of exporting them. For a small business site with a few dozen pages, the cost of that rebuild is real money spent against no visible benefit. The result is a large population of working, unfashionable, quietly maintained sites.

As of October 2026 we see SiteOrigin Page Builder on 42,504 sites in the Page builders category, with 12,957 of them attributed to United States and the domain list weighted toward .com. Written in PHP and distributed free through the plugin repository, the builder spread through exactly the channels that produce this kind of long tail: hobbyist installs, template themes, and agencies that standardised on it long ago and never revisited the decision.

Because the plugin is free, its version data means something different than it would for a paid product. We record 230 distinct version strings, with 2.36.0 on the current release line. There is no licence key to expire here, so a site running an old build is not a lapsed customer. Old builds indicate automatic updates switched off, a host that pins versions, or an owner who stopped logging in. For anyone assessing risk across a portfolio of sites, an unattended PHP plugin is a more useful finding than an out of date paid one, because nobody is watching it.

Detection has an honest limit. We identify the builder from the markup and stylesheets it emits, and a theme that heavily overrides or inlines those styles can hide it. The companion widget bundle is also frequently installed alongside the builder, and the two are not the same product, so a list built from a careless signature will mix them together. The count should be read as a floor.

The reason to download the list rather than check domains individually is that every interesting question about a legacy builder is a question about a population. Which hosts carry large numbers of these sites, so a migration offer can be made through them rather than one owner at a time. How many sit on old PHP versions and will break at the next platform upgrade. Whether the population is shrinking between snapshots, and how fast, which is what tells a competing builder whether the migration market is still worth chasing. A per domain lookup confirms one site. A file covering 42,504 domains lets you find the pattern that makes the outreach worth doing.