Download websites that use All in One SEO Pack

About All in One SEO Pack

An SEO plugin is chosen once, usually on the day a site is built, and then it stays. Nobody migrates one for pleasure, because the titles, the descriptions, the sitemap rules and the schema markup all live inside it, and moving means doing that work twice. What accumulates is a record of decisions frozen at the moment of installation rather than a picture of how anyone practises search optimisation today.

All in One SEO Pack is old enough for the distinction to matter. Written in PHP and released in 2007, the plugin predates most of what the WordPress ecosystem now assumes, and it collected its installs across two decades of site building rather than in a single wave. As of October 2026 we detect it on 31,696 sites. The installs behind that figure were not made at the same time, by the same kind of builder, or for the same reason.

Version data turns the point into something measurable. We record 202 distinct version strings in production, and 2.12 still recurs widely across the population, a branch from long before the plugin was rebuilt under Awesome Motive. A site reporting a release that old has not had its plugins touched in years, so the version string is doing double duty here. The string identifies the SEO tool, and it dates the last time anybody maintained the site.

Geography sharpens the same reading. Japan carries 9,079 of the detections, a concentration that an American plugin distributed in English does not explain on its own. Clusters of that shape normally trace back to a local ecosystem rather than to a local preference: a hosting company shipping a standard stack, a theme sold heavily in one market, a generation of agencies that standardised on one toolkit and never revisited the choice. The population sits mainly in the .com zone, which follows commercial registration and says little on its own.

GPL v2 licensing is part of why the footprint spread the way it did. Anyone may bundle the plugin, preinstall it on a hosting template or ship it inside a commercial theme, so a great many of these installs were never chosen by the site owner at all. The person who made the decision is often an integrator two steps removed from the domain.

For anyone selling a competing SEO product, the useful query is not who runs the plugin but who runs an unmaintained copy of it in a market where you already have a partner. For an agency, the same population read the other way is a list of sites whose owners are one incident away from needing help. Both questions need version, country and platform on the same row, which is exactly what a per-domain lookup cannot give you, because a lookup answers only about the site you had already thought of.

The honest limits are worth stating. Detection depends on markers the plugin leaves in a page, so an installation configured to strip them, or one active only on pages outside the crawl, does not appear. Free and paid tiers are not separable from outside, which means the count describes deployments rather than customers. The version is what the site discloses, not necessarily what is on disk.

The webatla export lists every domain where we found the plugin, with the version we observed, the hosting country, the domain zone and the rest of the stack detected on the same site, in one file rebuilt daily and filtered on your own machine.