# WordPress Plugin Scraper — Installs & Ratings (`hichemdev/wordpress-plugins-scraper`) Actor

Scrape the WordPress.org plugin directory: slug, name, author, version, active installs, total downloads, star rating, number of ratings, last update, WP and PHP requirements, tags and support resolution rate. Search by keyword, browse popular or top-rated, filter by tag or author. No API key.

- **URL**: https://apify.com/hichemdev/wordpress-plugins-scraper.md
- **Developed by:** [Hichem Ben Moussa](https://apify.com/hichemdev) (community)
- **Categories:** Developer tools, Business, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 plugins

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## WordPress Plugin Scraper — Installs, Ratings, Downloads & Versions

Scrape the **WordPress.org plugin directory** — over 59,000 plugins with active install counts, lifetime downloads, star ratings, version and compatibility data, and support-forum health.

Search by keyword, browse the most popular or top-rated, filter by tag or author, or pull exact plugins by slug.

No API key required.

### What you get

| Field | Description |
|---|---|
| `slug`, `name` | Plugin identifier and display name |
| `author`, `authorProfile` | Developer and their WordPress.org profile |
| `version` | Current release |
| `activeInstalls` | Active installations — the real adoption number |
| `downloaded` | Lifetime downloads |
| `rating` | Stars out of 5 |
| `ratingPercent` | Raw 0–100 score as WordPress.org stores it |
| `numRatings` | How many people rated it |
| `lastUpdated`, `added` | Release recency and age |
| `requiresWp`, `testedUpTo`, `requiresPhp` | Compatibility |
| `supportThreads`, `supportThreadsResolved` | Support-forum volume |
| `supportResolutionRate` | Percentage of threads resolved — a maintenance-quality signal |
| `tags` | Directory tags |
| `shortDescription` | Plugin summary |
| `downloadLink`, `homepage`, `icon`, `url` | Assets and links |

### Example input

```json
{
  "searchTerm": "seo",
  "minActiveInstalls": 10000,
  "maxPlugins": 100
}
```

Other modes:

```json
{ "browse": "popular", "maxPlugins": 500 }
{ "tag": "ecommerce", "browse": "top-rated" }
{ "author": "automattic" }
{ "slugs": ["wordpress-seo", "elementor", "woocommerce"] }
```

### Example output

```json
{
  "slug": "wordpress-seo",
  "name": "Yoast SEO – Advanced SEO with real-time guidance and built-in AI",
  "version": "28.5",
  "author": "Yoast",
  "activeInstalls": 10000000,
  "downloaded": 1002566087,
  "rating": 4.8,
  "ratingPercent": 96,
  "numRatings": 27820,
  "lastUpdated": "2026-09-15 6:43am GMT",
  "testedUpTo": "7.1.2",
  "supportThreads": 100,
  "supportThreadsResolved": 71,
  "supportResolutionRate": 71,
  "url": "https://wordpress.org/plugins/wordpress-seo/"
}
```

Plugin names and descriptions are HTML-encoded at the source; the actor decodes them, so you get `Yoast SEO – Advanced SEO` rather than `Yoast SEO – Advanced SEO`.

### Who uses this

- **Plugin developers** — track your own install growth and your competitors' week over week
- **Market research** — find categories where demand is high and the incumbents are stale or badly rated
- **WordPress agencies** — vet plugins before shipping them to clients: is it updated, tested on the current WP version, is support answered?
- **Security and maintenance teams** — flag abandoned plugins (`lastUpdated` old, `testedUpTo` behind) across the plugins your sites depend on
- **Acquisition scouts** — spot plugins with large install bases, weak support and an inactive author
- **Content and SEO teams** — build "best plugins for X" roundups from real numbers rather than opinion

### About `activeInstalls`

WordPress.org reports active installs in **buckets**, not exact figures — you will see 10, 100, 1000, 10000, 1000000 and so on. That is how the directory publishes the data; no source gives an exact count. `downloaded` is an exact lifetime total and is more granular, which makes it the better field for measuring short-term momentum.

### Pricing

Pay per result. Each plugin returned counts as one result.

### Notes

- Data comes from the public WordPress.org plugin information API.
- `rating` is derived from the directory's 0–100 score; both forms are included so you can use whichever your pipeline expects.
- `supportResolutionRate` is `null` when a plugin has no support threads in the current window rather than `0`, so an unused forum is not mistaken for a neglected one.
- This is an unofficial actor and is not affiliated with WordPress.org, Automattic or the WordPress Foundation.

# Actor input Schema

## `searchTerm` (type: `string`):

Keyword to search the plugin directory for, e.g. seo, woocommerce, backup, cache.

## `browse` (type: `string`):

Use instead of a search term to list the directory. Defaults to popular when nothing else is set.

## `tag` (type: `string`):

Filter by a directory tag, e.g. ecommerce, security, gutenberg.

## `author` (type: `string`):

Filter by a WordPress.org author username, e.g. automattic.

## `slugs` (type: `array`):

Fetch these exact plugins instead of searching. Use the slug from the directory URL, e.g. wordpress-seo, elementor, woocommerce.

## `minActiveInstalls` (type: `integer`):

Skip plugins with fewer active installations than this.

## `maxPlugins` (type: `integer`):

Stop after this many plugins.

## `proxyConfiguration` (type: `object`):

Optional. A proxy is not required for this actor.

## Actor input object example

```json
{
  "searchTerm": "seo",
  "browse": "",
  "minActiveInstalls": 0,
  "maxPlugins": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped items as JSON.

## `overview` (type: `string`):

Browse results in the Apify Console.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchTerm": "seo",
    "maxPlugins": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("hichemdev/wordpress-plugins-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchTerm": "seo",
    "maxPlugins": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("hichemdev/wordpress-plugins-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchTerm": "seo",
  "maxPlugins": 50
}' |
apify call hichemdev/wordpress-plugins-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hichemdev/wordpress-plugins-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jLDeDbOJVWJPihbpw/builds/AIkU3FYuz1FMqljDb/openapi.json