How WordPress.org Counts Active Installs (And Why It Lies)

WordPress.org doesn't count active installs the way you'd count rows in a database. It estimates them from a daily telemetry ping that WordPress core sends home, then rounds the result into a public bucket like "10,000+ active installations." If your number jumped by thousands overnight, or refused to budge for a week after a big launch, the estimation method is the reason.

How WordPress.org Counts Active Installs

Every WordPress site running the default cron setup checks in with api.wordpress.org roughly once or twice a day via the wp_version_check job. That request reports PHP and MySQL versions, the active theme, the locale, whether the site is multisite, and — critically — the list of currently active plugins.

WordPress.org never sees a running total of "sites using Plugin X." Instead it calculates what percentage of sites that checked in during a given window have Plugin X active, then applies that percentage to its internal estimate of total WordPress sites worldwide. The result is a projection, not a census.

Why the badge is a range, not a count

The number on your plugin page never shows a precise figure. It snaps to one of a fixed set of thresholds:

Two plugins can both display "10,000+" while one has 10,200 real installs and the other has 19,800. If you want to see where you actually sit relative to the field, cross-reference your bucket against the WordPress plugin rankings, which track movement over time instead of one static snapshot.

What Actually Gets Counted (and What Doesn't)

• Active, not installed. A plugin sitting deactivated in wp-admin doesn't report back. Only currently-active plugins show up in the daily payload.
• Multisite typically counts once per network, not per subsite. If a network of 500 sites network-activates your plugin, that generally registers as a single reporting install — not 500. This is the biggest reason install counts for agency- and enterprise-favored plugins look smaller than their real footprint.
• Sites that block the check-in don't count. Agencies that disable wp-cron, firewall outbound requests, or run staging/local environments (Local, DevKinsta) often never phone home at all.
• Downloads aren't installs. Someone who grabbed your zip from the repo but never activated it contributes nothing to the number.

This matters most for plugins sold into enterprise and agency channels — think WooCommerce extensions or server-side tools like LiteSpeed Cache — where multisite and locked-down hosting are common. Your real footprint can be meaningfully larger than the public badge suggests.

How Active Installs Affect Your WordPress.org Ranking

Active installs are one input to search relevance, not the whole formula. The directory also weighs keyword and title match, star rating, review volume, support-thread resolution rate, and how recently you've shipped an update tested against the current WordPress version.

That's why a plugin with 2,000 installs and a 4.9-star rating with fast support replies can outrank one with 20,000 installs and a stale "tested up to" tag. If ranking is the real goal, install count alone won't get you there — see our WordPress Plugin SEO guide for the full relevance checklist, and run your target terms through keyword research before you rewrite your readme.txt.

Plugins that prove the point

Elementor and Yoast SEO sit in the millions-plus bucket because they combine high installs with strong ratings and a constant update cadence. Classic Editor, by contrast, has held a massive bucket for years on pure inertia — millions of sites keep it active just to avoid the block editor, with minimal new feature development. Installs measure adoption; they don't measure momentum.

Reading the Growth Chart Without Fooling Yourself

Every plugin's "Advanced View" stats page on WordPress.org shows a historical trend line. Treat it as directional, not precise:

1. There's reporting lag. Daily numbers are smoothed estimates, so a real-world spike — a viral tutorial, a holiday promo — shows up gradually, not as a vertical line.
2. Bucket snapping hides small moves. You can gain or lose a few hundred installs with zero visible change in your public badge if you're mid-bucket.
3. A breaking update causes visible cliffs. Mass deactivations after a bad release show up within days, because deactivated sites stop reporting the plugin as active almost immediately.

If you need a cleaner signal, compare your trend against named competitors using competitor analysis rather than eyeballing one chart in isolation.

Practical Ways to Track Your Real Numbers

• Watch your bucket and category percentile on the WordPress plugin rankings, or the theme rankings if you ship a theme.
• Use the plugin & theme detector to see which live sites — including competitors' customer sites — are actually running a given plugin, a ground-truth check the install badge can't give you.
• Audit your readme.txt and support forum response time; both move the relevance score independent of install count. Our practitioner's guide to the best WordPress plugins in 2026 breaks down what actually earns a top-of-category spot.
• If a competitor like Contact Form 7 dominates your niche's install count, don't chase the raw number — chase the rating and update-cadence gap instead, since that's where newer entrants actually win share.

FAQ: How WordPress.org Counts Active Installs

Does deactivating a plugin remove it from the active install count?

Yes. The count comes from a daily check-in that reports only currently active plugins, so once you deactivate, your site stops being counted in future pings and the aggregate number drifts down within days.

Do multisite networks count as one install or one per site?

Typically one. When a plugin is network-activated across a multisite install, the check-in generally reports a single registration for the network rather than one per subsite — a common reason agency-favored plugins show lower counts than their real footprint.

Why did my active install count drop after I shipped an update?

Usually one of two things: the update broke something and triggered mass deactivations, which get reported within days, or your previous count was near the bottom of its bucket and ordinary week-to-week churn pushed you into a lower displayed range.

How often does WordPress.org update the public active install number?

The underlying telemetry is aggregated daily, but the number on the plugin page and the Advanced View stats chart can lag by a day or more, and it only changes visibly when you cross into a new bucket threshold.

Does disabling usage tracking or blocking wp-cron affect the official count?

Yes, it undercounts you. Sites that block the version-check request — common on hardened hosting, firewalled intranets, and local or staging environments — never report active plugins, so the published number is always a floor on real usage, not a ceiling.

Is the active install count the same as downloads?

No. Downloads reflect how many times a zip file has been pulled from the repository, while active installs reflect the estimated number of sites currently running the plugin — almost always a much smaller number than lifetime downloads.

Does a higher active install count guarantee better ranking on WordPress.org?

No. Installs are one input among several; search relevance also weighs star rating, review volume, support-thread resolution, keyword match, and how recently you've tested against the current WordPress version.