WordPress Plugin Scraper - Installs & Ratings

What does WordPress Plugin Scraper do?

The 68,589 plugins in the WordPress directory, with what actually decides whether to install one: how many sites run it, whether anyone still maintains it, and whether its support answers.

The directory publishes all of that, scattered. A support resolution rate you have to compute. A compatibility figure expressed as a version number you have to compare against the current WordPress release. A rating out of 100 when the interface shows five stars.

No API key. No account.

---

The number nobody computes

The directory reports "48 support threads, 36 resolved" and never the ratio. It is the best available answer to the question that matters when something breaks at 2am on a client site.

Measured across 300 popular plugins, 112 had enough support activity to judge — and the spread is not subtle:

Plugin	Resolved	Threads	Active installs
WPS Hide Login	0%	0 / 6	2,000,000
…
Elementor	75%	36 / 48	10,000,000

Two million sites running a plugin whose support has resolved nothing. That is not visible anywhere on its directory page.

---

The four things this does that the source does not

1. The support resolution rate.

supportResolutionPct, alongside the raw counts so you can see whether the rate rests on six threads or six hundred.

2. Obsolescence, dated and qualified.

tested says which WordPress version a plugin was verified against. The Actor fetches the current WordPress release at runtime and compares — so isOutdated stays correct as WordPress ships, instead of being frozen against a constant that ages. daysSinceUpdate carries the other half.

3. Downloads per install.

Elementor: 10,000,000 active installs, 887,457,954 downloads — 88.7 per site. That ratio is the update cadence. A very low one means a plugin people install once and never update, which is its own kind of risk.

4. The rating as stars, with the distribution behind it.

90/100 becomes 4.5 stars, and ratings1 through ratings5 show what it is made of. Elementor's 4.5 rests on 6,145 five-star reviews and 684 one-star ones — a shape the single number hides. hasEnoughRatings flags anything resting on fewer than 50.

---

Field coverage

Measured on 300 popular plugins.

Field	Coverage
name, activeInstalls, totalDownloads	100%
ratingStars, ratingCount, review distribution	100%
lastUpdated, ageYears, testedUpTo, requiresPhp	100%
downloadsPerInstall	100%
daysSinceUpdate	98%
homepage	93%
supportThreads	87%
supportResolutionPct	69%

supportResolutionPct is empty where a plugin has no support threads at all — no activity, no rate. That is an absence, not a gap, and it is left empty rather than reported as zero.

---

What it is for

• Choosing a plugin for a client site. Installs, rating shape, support resolution and last update in one table, for every candidate.
• Auditing an existing site. Feed in the slugs a site runs and see which ones stopped being maintained.
• Competitive research. A competitor's whole catalogue by author, with adoption and support quality per plugin.
• Finding a gap. Search a category, sort by installs, and look for plugins with large user bases, poor support and no recent release.
• Acquisition screening. Plugins with real adoption and an absent maintainer are the ones that get bought.

Three dataset views ship with the Actor: Plugins, Support quality and Maintenance risk.

---

Limits

Stated plainly, because they affect what you can conclude.

• Active installs are bucketed, not exact. WordPress reports 10,000,000 or 90,000 — rounded figures, not counts. Treat them as orders of magnitude.
• Support threads count the last two months only. A plugin with six threads is not a plugin with six problems ever; it is a snapshot of recent activity, and small numbers make an unreliable rate.
• Reviews are cumulative and never expire. A plugin that was bad in 2019 and good since still carries those one-star reviews. Read the distribution alongside ageYears.
• isOutdated is a heuristic. Plugins are marked untested when they lag the current release by roughly two major versions. A plugin can be perfectly functional and simply not re-tested.
• Directory plugins only. Premium and commercial plugins distributed outside wordpress.org — a large part of the real market — are not here at all.
• downloadsPerInstall is not a ratio of people. Downloads include every automatic update, mirror and CI fetch.
• Search is the directory's own. Relevance ordering is WordPress's, and it is not the same as ordering by quality or adoption.

---

How much does it cost?

You pay per plugin returned: $0.003 each, that is $3.00 per 1,000. There is no start fee, and subscription plans pay less per plugin.

The example input below asks for up to 500 plugins, so it costs $1.50 at most.

If a run reaches the spending limit you set, the output stops at that limit and never goes past it. You are never charged for rows that were not delivered.

Use WordPress Plugin Scraper as an API

Call it from your own code with the Apify client, here in Python:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("DataIO/wordpress-org-plugin-stats").call(run_input={
    'browse': 'popular',
    'minActiveInstalls': 10000,
    'maxItems': 500,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

It also works from JavaScript, Make, Zapier, n8n, and from AI agents through the Apify MCP server.

Other actors you might like

• npm Downloads Scraper: Package Trends & Growth
• crt.sh Subdomain Finder: Certificate Search
• Domain Expiry Checker: RDAP Registrar & Status

FAQ

Is it legal to use this data?

The actor reads public data from its official source, without logging in and without bypassing any access control. What you do with the data, for example contacting people listed in it, is your responsibility under the laws that apply to you, such as GDPR in Europe.

Can I run it on a schedule?

Yes. Create a schedule in Apify Console, daily or weekly for example, and each run delivers a fresh dataset, which you can send by email, webhook or integration.

Can AI agents use it?

Yes. It is available through the Apify MCP server, and every input field is described in its input schema, so an agent can call it directly.

Source

The public WordPress.org plugin API, the same endpoint behind the plugin browser in every WordPress install, plus the core version-check API for the current release. No authentication. This Actor is not affiliated with WordPress.org or Automattic.