# WordPress Plugin Scraper & Stats API (`thimbleroot/wordpress-plugin-intel`) Actor

Get WordPress.org plugin data from the official API: installs, ratings, days since update, support resolution rate, compatibility and recent reviews.

- **URL**: https://apify.com/thimbleroot/wordpress-plugin-intel.md
- **Developed by:** [Thimbleroot Studio](https://apify.com/thimbleroot) (community)
- **Categories:** Developer tools, SEO tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 plugin scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 & Stats API

Want to know if a WordPress plugin is still maintained before you install it? Or how a competitor's installs and ratings are trending? This Actor pulls plugin data from WordPress.org and gives you one tidy row per plugin, plus the newest reviews if you want those too.

Plugin details come from the official WordPress.org plugin API (`api.wordpress.org/plugins/info/1.2/`). You don't need a login, an API key or proxies. Export to JSON, CSV or Excel, or call it from your own code through the Apify API.

### What you get

Along with the usual directory fields (name, version, author, installs, rating), every plugin row also includes:

- **daysSinceUpdate**: makes abandoned plugins easy to spot.
- **supportResolvedRate**: the share of support threads marked resolved. It's a good sign of whether the author actually answers.
- **Compatibility**: requires WP, tested up to, requires PHP.
- **ratingDistribution**: the count of 1 to 5 star ratings, not just the average.
- **reviewInsights**: reviews in the last 30 and 90 days, the recent average rating, the share of negative reviews and the share of reviews that got a reply.

### Who uses it

- Agencies auditing client sites or vetting plugins before installing them.
- Plugin authors keeping an eye on competitors.
- Buyers doing due diligence on a plugin business.
- Marketers and researchers mapping a niche, for example every plugin tagged `seo`.

### Example inputs

**1. Check a shortlist**

```json
{ "plugins": ["akismet", "contact-form-7", "https://wordpress.org/plugins/wordpress-seo/"], "includeReviews": true, "maxReviewsPerPlugin": 20 }
```

**2. Map a niche cheaply (no reviews)**

```json
{ "tag": "seo", "maxPlugins": 200, "includeReviews": false }
```

**3. Everything from one author, recent reviews only**

```json
{ "author": "automattic", "maxPlugins": 50, "includeReviews": true, "reviewsSince": "2026-01-01" }
```

### Sample output (plugin rows, shortened)

| name | slug | activeInstalls | rating | numRatings | daysSinceUpdate | supportResolvedRate | testedUpTo |
|---|---|---|---|---|---|---|---|
| Akismet Anti-spam: Spam Protection | akismet | 5,000,000 | 4.7 | 1,187 | 58 | 0.62 | 7.1.3 |
| Contact Form 7 | contact-form-7 | 10,000,000 | 4.0 | 2,100 | 21 | 0.35 | 7.1.3 |
| Yoast SEO | wordpress-seo | 10,000,000 | 4.8 | 27,000 | 9 | 0.71 | 7.1.3 |

(Example values. Your run returns live numbers.)

Review rows have: pluginSlug, date, rating, title, reviewer, replyCount and reviewUrl. If a plugin can't be found, you get an `error` row (which is free) and the run keeps going.

### Pricing

You pay per result: **$3 per 1,000 plugins** and **$0.50 per 1,000 reviews**. Turn reviews off for the cheapest runs.

### Tips

- Plugins you list by slug are always included. Search, tag, author and browse all share the **Max plugins** cap.
- Leave the request delay at 1000 ms to stay polite to WordPress.org.
- Sort by `daysSinceUpdate` and `supportResolvedRate` to find risky plugins fast.

### Fair use

This Actor only reads public data. Thimbleroot isn't affiliated with WordPress.org or the WordPress Foundation. Questions or feature requests: use the Issues tab.

# Actor input Schema

## `plugins` (type: `array`):

WordPress.org plugin slugs or plugin page URLs to fetch, one per item. The slug is the last path segment of the plugin URL, e.g. 'akismet', 'contact-form-7', or 'https://wordpress.org/plugins/wordpress-seo/'. These are always included in addition to any search/tag/author/browse results. Leave empty if you only use search/tag/author/browse.

## `search` (type: `string`):

Optional free-text query run against the WordPress.org plugin directory, e.g. 'backup' or 'contact form'. Matching plugins are added, up to 'maxPlugins'.

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

Optional WordPress.org plugin tag (lowercase, hyphenated), e.g. 'seo', 'woocommerce', 'security', 'contact-form'. Plugins with this tag are added, up to 'maxPlugins'.

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

Optional WordPress.org username of a plugin author (from https://profiles.wordpress.org/<username>/), e.g. 'automattic'. All their plugins are added, up to 'maxPlugins'.

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

Optional WordPress.org browse list to add plugins from: 'popular', 'new', 'updated' (recently updated) or 'top-rated'. Leave empty to skip.

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

Maximum number of plugins added from search, tag, author and browse combined (1-5000). Does not limit plugins listed explicitly in 'plugins'. Higher values mean longer runs and higher cost.

## `includeReviews` (type: `boolean`):

If true, also scrape each plugin's newest public reviews (output as 'review' records) and compute reviewInsights (reviews in the last 30/90 days, recent average rating, negative share, reply share). Set false for faster, cheaper runs with plugin stats only.

## `maxReviewsPerPlugin` (type: `integer`):

Maximum number of newest reviews to fetch per plugin when 'includeReviews' is true. 0 disables review records. Default 20.

## `reviewsSince` (type: `string`):

Optional cutoff date in YYYY-MM-DD format, e.g. '2026-01-01'. Review paging stops once reviews are older than this date.

## `requestDelayMs` (type: `integer`):

Pause in milliseconds between requests to wordpress.org, to stay polite. Default 1000; lowering it is not recommended.

## Actor input object example

```json
{
  "plugins": [
    "akismet"
  ],
  "browse": "",
  "maxPlugins": 5,
  "includeReviews": true,
  "maxReviewsPerPlugin": 20,
  "requestDelayMs": 1000
}
```

# Actor output Schema

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

No description

# 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 = {
    "plugins": [
        "akismet"
    ],
    "maxReviewsPerPlugin": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("thimbleroot/wordpress-plugin-intel").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 = {
    "plugins": ["akismet"],
    "maxReviewsPerPlugin": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("thimbleroot/wordpress-plugin-intel").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 '{
  "plugins": [
    "akismet"
  ],
  "maxReviewsPerPlugin": 20
}' |
apify call thimbleroot/wordpress-plugin-intel --silent --output-dataset

```

## MCP server setup

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

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/Y8naK354bhJYMnzOp/builds/aIyV9PnMJiyWGN8LW/openapi.json