# WordPress Plugin Directory Scraper: Installs, Ratings, No Login (`one_dollar_store/wordpress-plugin-directory-scraper`) Actor

WordPress.org plugins: active installs, rating, ratings count, version, tested up to, required WordPress and PHP, last updated, tags, links. Search, author, tag, popular, new, updated, or plugin slugs. $1 per 1,000 results, platform usage included.

- **URL**: https://apify.com/one_dollar_store/wordpress-plugin-directory-scraper.md
- **Developed by:** [One Dollar Store](https://apify.com/one_dollar_store) (community)
- **Categories:** Developer tools, Open source, SEO tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 and versions from the plugin directory

**$1 per 1,000 plugins. Platform usage included. No rental, no minimum.**

WordPress Plugin Scraper returns plugin data from the WordPress.org plugin directory. Each row has the active installs, rating, number of ratings, version, tested up to version and last updated date. You pick plugins by search words, tag, author, the popular, new or updated lists, or a list of plugin slugs.

The four most used WordPress plugin actors on Apify Store charge $2.00 to $20.00 per 1,000 results, and one or more add platform usage on top (Store prices checked 24 October 2026). This actor returns plugin data from the WordPress.org directory for $1.

[Open it in Apify Console](https://console.apify.com/actors/xEFLt9vp3b3lqYWZR/input)

### How much does WordPress Plugin Scraper cost?

| Plugins | This actor | Most used WordPress plugin actors on the Store |
|---|---|---|
| 1,000 | $1.00 | $2.00 to $20.00 |
| 10,000 | $10.00 | $20 to $200 |
| 100,000 | $100.00 | $200 to $2,000 |

Tracking the 50 most popular plugins once a day is 50 results, so $0.05 a run and about $1.50 a month.

### Why people switch

- **One flat price.** Compute is included, so the bill follows the number of plugins and nothing else.
- **Five ways to pick plugins.** Search words, a tag, an author, the popular, new or updated list, or a list of plugin slugs. Search words and a tag work together.
- **The numbers people compare.** Active installs, total downloads, star rating, number of ratings and how many ratings each star level got, support threads opened and resolved, tested up to, required WordPress and PHP versions, last updated and date added.
- **Small answers.** The actor switches off the long description that the directory sends by default, so each request of 100 plugins is about 120 KB instead of about 400 KB.
- **No key, no login.** It reads the public WordPress.org plugin directory API.

### How to use WordPress Plugin Scraper

1. Open the actor, type a search word such as `woocommerce` and a tag such as `ecommerce`, press **Start**.
2. Or paste this input:

```json
{ "searchQuery": "woocommerce", "tag": "ecommerce", "maxItems": 100 }
```

3. Download the results as JSON, CSV or Excel, or read them through the API.

### Use it from code

```bash
curl -X POST "https://api.apify.com/v2/acts/one_dollar_store~wordpress-plugin-directory-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQuery": "woocommerce", "tag": "ecommerce", "maxItems": 50}'
```

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("one_dollar_store/wordpress-plugin-directory-scraper").call(
    run_input={"searchQuery": "woocommerce", "tag": "ecommerce", "maxItems": 50}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["slug"], item.get("activeInstalls"), item.get("rating"), item.get("testedUpTo"))
```

### Use it from an AI assistant

Claude, ChatGPT, Cursor and other assistants can call this actor through Apify's MCP server. Add it with this server address:

```
https://mcp.apify.com?tools=one_dollar_store/wordpress-plugin-directory-scraper
```

Then ask, for example: "List the 30 most installed WordPress plugins tagged seo, with rating, tested up to version and last updated date."

### Switching from another WordPress plugin actor

Most WordPress plugin actors take a search keyword and a result limit. Here they are `searchQuery` and `maxItems`, plus `tag`, `author`, `browse` and `pluginSlugs`. The core output fields are `slug`, `name`, `version`, `activeInstalls`, `rating`, `numRatings`, `testedUpTo`, `lastUpdated` and `pluginUrl`.

### Input

| Field | Type | Default | What it does |
|---|---|---|---|
| `searchQuery` | text | none | Words to look for in plugin names, descriptions and tags, for example `seo` or `contact form`. |
| `tag` | text | none | A plugin tag, for example `woocommerce`. Works together with `searchQuery`. |
| `author` | text | none | A WordPress.org username, for example `automattic`. |
| `browse` | text | `popular` | `popular`, `new` or `updated`. Used only when `searchQuery`, `tag`, `author` and `pluginSlugs` are all empty. |
| `pluginSlugs` | list of text | none | Plugin slugs or plugin page addresses, one per line. Up to 400. |
| `maxItems` | number | 100 | Most plugins to return (10 to 10,000). |

How the inputs combine:

- `searchQuery` with `tag`: the directory applies both, and a plugin must match both.
- `author` alone: the plugins that list this user as author or contributor.
- `author` with `searchQuery` or `tag`: the directory cannot combine them, so the actor reads the author's plugins and keeps those where the tag is present and every search word appears in the name, slug, short description or tags.
- `pluginSlugs` with any of the above: both run, and a plugin that comes up twice is returned once.
- Nothing filled in: the `browse` list, `popular` by default.

Example:

```json
{ "author": "automattic", "tag": "ecommerce", "maxItems": 200 }
```

### What data does WordPress Plugin Scraper return?

| Field | Meaning |
|---|---|
| `slug`, `name`, `version` | The plugin slug (last part of its WordPress.org address), its name and current version. |
| `author`, `authorUsername`, `authorUrl` | Author name as shown, the WordPress.org username, and the profile link. |
| `activeInstalls` | Active installs as WordPress.org reports them, in rounded steps (for example 10, 20000, 90000, 5000000). The highest step we saw is 10000000. Treat it as a lower bound, not an exact count. |
| `downloads` | Total downloads since the plugin was added. |
| `rating`, `ratingPercent` | Average rating in stars (0 to 5, one decimal) and on the 0 to 100 scale the API uses. Left out when the plugin has no ratings. |
| `numRatings`, `ratingCounts` | Number of ratings, and the count for each star level (keys 1 to 5). |
| `testedUpTo`, `requiresWordPress`, `requiresPhp` | Highest WordPress version tested, lowest WordPress and PHP versions needed. `requiresPhp` is left out when the author set none. |
| `requiresPlugins` | Plugins that must be installed first, when there are any. |
| `lastUpdated`, `added` | Last release time in UTC (ISO 8601) and the date the plugin was added to the directory. |
| `shortDescription`, `tags` | The short description and the tag slugs. |
| `homepage`, `downloadUrl`, `donateUrl`, `iconUrl` | The author's website, the zip of the current version, the donation link and the icon image, when the plugin has them. |
| `pluginUrl`, `supportUrl` | The plugin page and its support forum on WordPress.org. |
| `supportThreads`, `supportThreadsResolved` | Support threads and how many are marked resolved, as the directory counts them. |

Empty values are left out of a row instead of being sent as null.

### Sample results

Real rows from test runs on 24 October 2026: a popular plugin, a plugin looked up by slug, and two plugins found by author (the second has no ratings, so the rating fields are left out).

```json
[
  {"slug": "wordpress-seo", "name": "Yoast SEO \u2013 Advanced SEO with real-time guidance and built-in AI", "version": "28.7", "author": "Yoast", "authorUsername": "yoast", "authorUrl": "https://profiles.wordpress.org/yoast/", "activeInstalls": 10000000, "downloads": 1013620826, "rating": 4.8, "ratingPercent": 96, "numRatings": 27821, "ratingCounts": {"1": 846, "2": 139, "3": 201, "4": 642, "5": 25993}, "testedUpTo": "7.1.3", "requiresWordPress": "6.9", "requiresPhp": "7.4", "lastUpdated": "2026-10-13T05:27:00Z", "added": "2010-10-11", "shortDescription": "Real-time SEO guidance, schema, and AI built in. Help search engines and AI systems understand your content. All AI tools included, no hidden fees.", "tags": ["content-analysis", "readability", "schema", "seo", "xml-sitemap"], "homepage": "https://yoa.st/1uj", "downloadUrl": "https://downloads.wordpress.org/plugin/wordpress-seo.28.7.zip", "pluginUrl": "https://wordpress.org/plugins/wordpress-seo/", "supportUrl": "https://wordpress.org/support/plugin/wordpress-seo/", "supportThreads": 41, "supportThreadsResolved": 40, "donateUrl": "https://yoa.st/1up", "iconUrl": "https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908"},
  {"slug": "akismet", "name": "Akismet Anti-spam: Spam Protection", "version": "5.7.2", "author": "Automattic", "authorUsername": "automattic", "authorUrl": "https://profiles.wordpress.org/automattic/", "activeInstalls": 5000000, "downloads": 408018640, "rating": 4.7, "ratingPercent": 94, "numRatings": 1187, "ratingCounts": {"1": 57, "2": 13, "3": 16, "4": 67, "5": 1034}, "testedUpTo": "7.1.3", "requiresWordPress": "5.8", "requiresPhp": "7.2", "lastUpdated": "2026-08-18T23:42:00Z", "added": "2005-10-20", "shortDescription": "The best anti-spam protection to block spam comments and spam in a contact form. The most trusted antispam solution for WordPress and WooCommerce.", "tags": ["anti-spam", "antispam", "comments", "contact-form", "spam"], "homepage": "https://akismet.com/", "downloadUrl": "https://downloads.wordpress.org/plugin/akismet.5.7.2.zip", "pluginUrl": "https://wordpress.org/plugins/akismet/", "supportUrl": "https://wordpress.org/support/plugin/akismet/", "supportThreads": 1, "supportThreadsResolved": 0, "iconUrl": "https://ps.w.org/akismet/assets/icon-256x256.png?rev=2818463"},
  {"slug": "action-scheduler", "name": "Action Scheduler", "version": "4.2.0", "author": "Automattic", "authorUsername": "automattic", "authorUrl": "https://profiles.wordpress.org/automattic/", "activeInstalls": 20000, "downloads": 772679, "rating": 3.5, "ratingPercent": 70, "numRatings": 13, "ratingCounts": {"1": 4, "2": 1, "3": 0, "4": 0, "5": 8}, "testedUpTo": "7.1.3", "requiresWordPress": "6.9", "requiresPhp": "7.2", "lastUpdated": "2026-09-16T21:53:00Z", "added": "2020-07-14", "shortDescription": "Action Scheduler - Job Queue for WordPress", "tags": ["cron", "scheduler"], "homepage": "https://actionscheduler.org", "downloadUrl": "https://downloads.wordpress.org/plugin/action-scheduler.4.2.0.zip", "pluginUrl": "https://wordpress.org/plugins/action-scheduler/", "supportUrl": "https://wordpress.org/support/plugin/action-scheduler/", "supportThreads": 1, "supportThreadsResolved": 1, "iconUrl": "https://s.w.org/plugins/geopattern-icon/action-scheduler.svg"},
  {"slug": "a8c-3d-model-viewer", "name": "A8C 3D Model Viewer Block", "version": "1.0.0", "author": "Automattic", "authorUsername": "automattic", "authorUrl": "https://profiles.wordpress.org/automattic/", "activeInstalls": 10, "downloads": 2712, "numRatings": 0, "ratingCounts": {"1": 0, "2": 0, "3": 0, "4": 0, "5": 0}, "testedUpTo": "6.0.17", "requiresWordPress": "6.0", "lastUpdated": "2022-05-17T14:00:00Z", "added": "2022-05-17", "shortDescription": "View 3D models", "tags": ["3d", "block", "blocks", "model"], "downloadUrl": "https://downloads.wordpress.org/plugin/a8c-3d-model-viewer.zip", "pluginUrl": "https://wordpress.org/plugins/a8c-3d-model-viewer/", "supportUrl": "https://wordpress.org/support/plugin/a8c-3d-model-viewer/", "supportThreads": 0, "supportThreadsResolved": 0, "iconUrl": "https://s.w.org/plugins/geopattern-icon/a8c-3d-model-viewer.svg"}
]
```

### Limits

- **Where the data comes from.** The actor reads the public plugin directory API at api.wordpress.org, the service WordPress sites use for their own plugin screens. The robots.txt of that host asks automated clients not to crawl it. The actor is therefore a light client: one request at a time, at most one request per second, up to 100 plugins per request, and a User-Agent that names the actor and its Apify page. You decide how to use the data (see the legal question in the FAQ).
- **It stops when the API says no.** If the API refuses three requests in a row (HTTP 403 or 429), the run stops by itself, keeps the plugins already delivered, and says so in the status message and in `RUN_SUMMARY` under `stoppedByRefusals`. If nothing had been delivered, the run ends as failed with the same message.
- **Speed.** The actor asks for 100 plugins at a time and leaves at least 1.1 seconds between requests, so 10,000 plugins need about 100 requests. In a test run of 2,000 plugins the 21 requests took 6.5 seconds in total. Saving the rows on the platform is the slower part, about a tenth of a second per plugin: that run took 3 minutes 31 seconds. For more than about 4,000 plugins, raise Timeout under Run options (the default is 1 hour, enough for about 30,000 rows at this speed, more than the 10,000 plugins a run can return). A lookup by slug costs one request per plugin, so 400 slugs take about 8 minutes.
- **At most 10,000 plugins per run.** The popular list alone holds more than 72,000 plugins. Split bigger pulls by tag or author.
- **A snapshot.** Each row is the directory record at the time of the run. There is no history, no list of past versions, no review text, no changelog, no full description and no screenshots.
- **Rounded installs.** WordPress.org reports `activeInstalls` in rounded steps, so two plugins with the same number can differ a lot. The highest step we saw is 10,000,000.
- **Short descriptions are cut.** The directory shortens descriptions longer than about 150 characters and ends them with an ellipsis.
- **Search is the directory's own.** Results come in the directory's relevance order. The largest match count we saw for a search was 10,000, so treat 10,000 as the ceiling.
- **Exact names.** `tag` needs a tag slug and `author` a WordPress.org username. A name that does not exist gives no rows, and the run still ends as succeeded with the message "No results for this input."
- **Unknown slugs.** A slug that the directory does not return is listed under `notFound` in `RUN_SUMMARY` and costs nothing.
- **Counts move.** Totals and ratings change while the directory is edited, so two runs a few minutes apart can differ slightly.

### FAQ

**What is the cheapest WordPress plugin scraper on Apify?**
This actor costs $1 per 1,000 plugins with platform usage included. The four most used WordPress plugin actors on the Store charged $2.00 to $20.00 per 1,000 when we checked on 24 October 2026, and one or more add platform usage on top.

**How much does it cost to scrape 10,000 WordPress plugins?**
$10.

**Do I pay for compute or proxy on top?**
No. Platform usage is included in the $1 per 1,000 price. The actor needs no proxy.

**Where does the data come from?**
From the WordPress.org plugin directory API (api.wordpress.org/plugins/info/1.2/). No key is needed.

**Is it legal?**
The actor reads public plugin directory data only, with no login. The robots.txt of the API host asks automated clients not to crawl it, and we found no separate terms page for the API. The actor is a light, rate limited client of the public directory API: one request per second, a User-Agent that names the actor, and a stop after three refusals in a row. Buyers decide for themselves how to use the data. Every plugin has its own author and licence, so follow the law where you live and any terms that apply to you.

**Is this an official WordPress.org product?**
No. It is an independent tool and is not affiliated with or endorsed by WordPress.org.

**What does `activeInstalls` mean?**
It is the number of active installs that WordPress.org reports for the plugin, in rounded steps such as 20000, 90000 or 5000000. Use it to compare plugins by size, not as an exact count.

**How do I find plugins that look abandoned?**
Read a tag or a search, then sort the results by `lastUpdated` and `testedUpTo`. A plugin last updated years ago and tested only up to an old WordPress version is a candidate.

**How do I watch a set of plugins over time?**
Schedule a run with `pluginSlugs` set to your list and keep each run's results. Compare `version`, `lastUpdated`, `activeInstalls`, `rating` and `numRatings` between runs.

### Feedback and support

Found a problem or want a field added? Open an issue on the Issues tab of this actor and it gets read. If the actor saved you time, an honest rating on the Reviews tab helps other people find it.

**Do I need an Apify account?**
Yes. Actors run from an Apify account, and a free account is enough to start: it includes $5 of platform usage every month. You can [sign up here](https://www.apify.com?fpr=ymnoit). This is a referral link and it costs you nothing.

### More from The One Dollar Store

Every actor here costs $1 per 1,000 results, platform usage included. See the whole store: https://apify.com/one_dollar_store

**Domains and apps**

- [Apple App Store Scraper](https://apify.com/one_dollar_store/app-store-apps-scraper): App details, ratings and search results.
- [DNS Records Lookup](https://apify.com/one_dollar_store/dns-records-lookup): DNS records for any list of domains.
- [Domain WHOIS Lookup](https://apify.com/one_dollar_store/domain-whois-rdap-lookup): Registrar, dates and name servers for any domain.
- [Subdomain Finder](https://apify.com/one_dollar_store/subdomain-finder-crtsh): Subdomains found in certificate logs.
- [Shopify App Store Scraper](https://apify.com/one_dollar_store/shopify-app-store-scraper): Shopify apps with ratings and pricing.
- [Hugging Face Scraper](https://apify.com/one_dollar_store/hugging-face-models-scraper): Models and datasets with downloads and tags.
- [crates.io Scraper](https://apify.com/one_dollar_store/crates-io-packages-scraper): Rust crates with downloads and versions.

### Changelog

- 26 October 2026: clearer description and headings, field details for AI tools. Price and output unchanged.
- October 2026: first release.

# Actor input Schema

## `searchQuery` (type: `string`):

Optional. Words to look for in plugin names, descriptions and tags, for example seo or contact form. Works together with Tag. Leave empty to use the Browse list below.

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

Optional. A plugin tag, for example woocommerce or contact-form. Returns plugins that carry the tag, most used first. Works together with Search words.

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

Optional. The WordPress.org username of an author, for example automattic. It is the last part of the profile address. Returns the plugins that list this user as author or contributor. If you also fill in Search words or Tag, the actor reads the author's plugins and keeps only those that match.

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

Used only when Search words, Tag, Author and Plugin slugs are all empty. Popular is the directory's own popular ranking, New is newest first, Updated is most recently updated first.

## `pluginSlugs` (type: `array`):

Optional. One plugin per line: the slug (akismet) or the plugin page address (https://wordpress.org/plugins/akismet/). Each plugin is looked up directly and costs one request, at one request per second.

## `maxItems` (type: `integer`):

The run stops after this many plugins. Minimum 10, maximum 10,000. The directory is read at one request per second, up to 100 plugins per request. Saving results takes about a tenth of a second per plugin, so above about 4,000 plugins raise Timeout under Run options.

## Actor input object example

```json
{
  "browse": "popular",
  "maxItems": 50
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "browse": "popular",
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("one_dollar_store/wordpress-plugin-directory-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 = {
    "browse": "popular",
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("one_dollar_store/wordpress-plugin-directory-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 '{
  "browse": "popular",
  "maxItems": 50
}' |
apify call one_dollar_store/wordpress-plugin-directory-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,one_dollar_store/wordpress-plugin-directory-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/xEFLt9vp3b3lqYWZR/builds/CWnSViZlzBs7Ku8F1/openapi.json
