Download websites that use Site Kit

About Site Kit

Most technology signals describe what a site is built from. A few describe the person who runs it. Site Kit belongs firmly to the second group, and the distinction is the reason it deserves a different reading from the other Analytics entries on this site.

The plugin exists to pull search reporting, traffic reporting and performance scoring into a single dashboard inside the content management system. Getting it working requires somebody to log in, connect external accounts, grant permissions and verify ownership of the property. Installation is therefore not a build decision made once by a contractor and forgotten. Installation is evidence of ongoing attention from somebody who wants to know how the site is performing, which is a rare and commercially valuable thing to be able to infer from the outside.

Scale confirms how quickly a signal of that kind can propagate through an official plugin directory. As of September 2026 we detect Site Kit on 3,305,659 sites, with 1,115,571 of those resolving to United States and .com the common suffix. A tool published only since 2019, distributed under Apache 2.0 and maintained by Google, reaching a footprint of that size says less about the tool than about the distribution channel it travels through, where a single directory listing reaches millions of administrators without a sales conversation.

Release cadence tells a second story. We resolve 208 distinct version strings for the plugin, and 1.185.0 is the reading we record most frequently. A concentrated distribution over a large number of releases is the fingerprint of automatic updates working as intended, which is close to the opposite of what we see in self-hosted software that owners update by hand. The small residue of older builds is correspondingly meaningful, because falling behind on a plugin that updates itself usually means the site is broken, deliberately frozen or genuinely abandoned.

For a search agency, this is a prospecting list with the qualification already done, since every entry is a site whose owner has voluntarily connected search reporting and can be assumed to care about the numbers. For a competing analytics or reporting vendor, the same list is a displacement target. For a privacy researcher, the presence of the plugin describes a data relationship between a site and a large platform that visitors never see. For anyone selling into the content management ecosystem, it is a marker of an administrator who installs things, which is the single best predictor that they will install something else.

The caveats are real and specific. We infer the plugin from traces available in the delivered page, and those traces are neither universal nor guaranteed, so the count is a floor rather than a census. Presence tells us the plugin is installed, not that every service behind it is connected, active or being read by a human. Sites where the plugin exists purely in the administrative area, without emitting anything a visitor could see, are invisible to us by construction. None of that undermines comparison between markets or between neighbouring technologies, because the bias is consistent, but it does rule out treating the figure as a total.

A per-domain lookup tells you whether one prospect has the plugin, which is a fine thing to check before a call and a useless basis for planning. The downloadable list answers the question that comes first. How many such site owners exist, where are they, what suffixes do they use, what else runs alongside them, and how many of those are worth contacting at all. That is a population question, and populations come as files.