# Wordpress Plugins Scraper (`klondikeking/wordpress-plugins-scraper`) Actor

- **URL**: https://apify.com/klondikeking/wordpress-plugins-scraper.md
- **Developed by:** [Pierrick McD0nald](https://apify.com/klondikeking) (community)
- **Categories:** E-commerce, Developer tools
- **Stats:** 4 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 plugin extracteds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## WordPress Plugins Scraper

Extract comprehensive WordPress plugin data from WordPress.org with ease. Get plugin metadata, active install counts, ratings, reviews, changelogs, and compatibility information in structured JSON format. Perfect for plugin developers, market researchers, WordPress agencies, and competitive intelligence professionals.

### Why Use This Scraper?

WordPress powers over 43% of all websites, with 59,000+ plugins in the official repository. Understanding the plugin landscape is crucial for developers building competitive products, agencies selecting reliable tools, and researchers analyzing market trends. This scraper extracts rich, structured data directly from the WordPress.org API, giving you insights that are impossible to gather manually at scale.

### Use Cases

**Plugin Developer Competitive Analysis**
Research existing plugins in your niche before building. Analyze active install counts, user ratings, feature sets, and update frequency to identify market gaps and position your plugin effectively. Understand what users love (and hate) about competing solutions.

**WordPress Agency Tool Evaluation**
Make data-driven decisions when selecting plugins for client projects. Compare reliability metrics, support response rates, compatibility data, and user satisfaction scores. Build curated plugin stacks backed by real usage data.

**Market Research & Trend Analysis**
Track plugin popularity trends over time, identify emerging categories, and analyze the WordPress ecosystem's evolution. Perfect for investment research, industry reports, and strategic planning in the WordPress space.

### Features

- **Complete Plugin Metadata**: Extract name, version, author, description, homepage, and download links
- **Active Install Counts**: Get real user adoption metrics (10+, 100+, 1,000+, 1M+ installs)
- **Rating & Review Data**: Average ratings, rating distribution (1-5 stars), total review counts
- **Changelog Parsing**: Structured version history with release dates and change descriptions
- **Screenshot Extraction**: URLs for all plugin screenshots and banner images
- **Compatibility Information**: WordPress version tested up to, minimum requirements, PHP version
- **Support Metrics**: Number of support threads and resolution rates
- **Batch Processing**: Search by keyword or provide specific plugin slugs
- **Tag & Category Extraction**: Discover plugin categorization and taxonomy

### Input Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| searchQuery | string | No | - | Search term to find plugins (e.g., "seo", "contact form") |
| pluginSlugs | array | No | \[] | Direct plugin slugs to scrape (overrides searchQuery) |
| maxPlugins | integer | Yes | 50 | Maximum plugins to extract (1-1000) |
| includeReviews | boolean | No | true | Include user reviews and ratings |
| includeChangelog | boolean | No | true | Extract version changelog |
| includeScreenshots | boolean | No | true | Include screenshot URLs |

### Output Example

```json
{
  "slug": "wordpress-seo",
  "name": "Yoast SEO",
  "version": "23.2",
  "author": "Team Yoast",
  "authorProfile": "https://profiles.wordpress.org/yoast/",
  "description": "Improve your WordPress SEO...",
  "shortDescription": "Improve your WordPress SEO",
  "url": "https://wordpress.org/plugins/wordpress-seo/",
  "homepage": "https://yoa.st/1uj",
  "downloadLink": "https://downloads.wordpress.org/plugin/wordpress-seo.23.2.zip",
  "activeInstalls": 5000000,
  "rating": 96,
  "ratingCount": 27384,
  "ratingsBreakdown": {
    "5": 26384,
    "4": 584,
    "3": 184,
    "2": 124,
    "1": 108
  },
  "tested": "6.5",
  "requires": "6.3",
  "requiresPHP": "7.2.5",
  "lastUpdated": "2024-03-15 10:30:00",
  "added": "2010-10-18",
  "tags": ["seo", "xml-sitemap", "social", "content-analysis"],
  "supportThreads": 145,
  "supportThreadsResolved": 142,
  "screenshots": [
    "https://ps.w.org/wordpress-seo/assets/screenshot-1.png",
    "https://ps.w.org/wordpress-seo/assets/screenshot-2.png"
  ],
  "icons": {
    "1x": "https://ps.w.org/wordpress-seo/assets/icon-128x128.png",
    "2x": "https://ps.w.org/wordpress-seo/assets/icon-256x256.png"
  },
  "banners": {
    "low": "https://ps.w.org/wordpress-seo/assets/banner-772x250.jpg",
    "high": "https://ps.w.org/wordpress-seo/assets/banner-1544x500.jpg"
  },
  "changelog": [
    {
      "version": "23.2",
      "date": "2024-03-15",
      "changes": [
        "Adds support for WordPress 6.5",
        "Improves sitemap generation performance",
        "Fixes schema markup for breadcrumbs"
      ]
    }
  ]
}
```

### Pricing

This actor uses Pay-Per-Event pricing:

| Event | Price |
|-------|-------|
| Plugin extracted | $0.001 per plugin |

**Cost Example**: Extracting data for 100 plugins costs $0.10. No monthly fees, no minimums — pay only for what you use.

### FAQ

**Q: Do I need a WordPress.org account?**
No. This scraper uses the public WordPress.org API, which requires no authentication.

**Q: What data can I extract?**
All publicly available plugin information: metadata, install counts, ratings, reviews, changelogs, screenshots, and compatibility data. Private plugin data is not accessible.

**Q: Is there a rate limit?**
The actor includes built-in rate limiting (1 second between requests) to respect WordPress.org API guidelines. For large extractions, expect approximately 1 plugin per second.

### Limitations

- WordPress.org API returns a maximum of 24 plugins per search page
- Review text is limited to what WordPress.org displays publicly
- Some older plugins may have incomplete metadata
- Plugin slugs must be exact (case-insensitive)
- Historical data (past install counts, rating trends) is not available

### Support

Open an issue on this Actor's Apify page for questions, bug reports, or feature requests. Response time typically within 48 hours.

***

*Built for WordPress professionals who need reliable, structured plugin data at scale.*

# Actor input Schema

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

Search term to find plugins on WordPress.org (e.g., 'seo', 'contact form', 'ecommerce')

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

Direct plugin slugs to scrape (e.g., \['wordpress-seo', 'contact-form-7']). If provided, searchQuery is ignored.

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

Maximum number of plugins to extract (useful for large searches)

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

Extract plugin reviews and ratings

## `includeChangelog` (type: `boolean`):

Extract plugin changelog/version history

## `includeScreenshots` (type: `boolean`):

Extract screenshot URLs

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

Proxy settings (optional - WordPress.org API usually doesn't require proxy)

## Actor input object example

```json
{
  "searchQuery": "seo",
  "pluginSlugs": [
    "wordpress-seo",
    "contact-form-7"
  ],
  "maxPlugins": 10,
  "includeReviews": true,
  "includeChangelog": true,
  "includeScreenshots": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

Complete plugin metadata, ratings, and reviews

## `stats` (type: `string`):

Execution statistics and summary

# 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 = {
    "searchQuery": "seo",
    "pluginSlugs": [
        "wordpress-seo",
        "contact-form-7"
    ],
    "maxPlugins": 10,
    "includeReviews": true,
    "includeChangelog": true,
    "includeScreenshots": true,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("klondikeking/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 = {
    "searchQuery": "seo",
    "pluginSlugs": [
        "wordpress-seo",
        "contact-form-7",
    ],
    "maxPlugins": 10,
    "includeReviews": True,
    "includeChangelog": True,
    "includeScreenshots": True,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("klondikeking/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 '{
  "searchQuery": "seo",
  "pluginSlugs": [
    "wordpress-seo",
    "contact-form-7"
  ],
  "maxPlugins": 10,
  "includeReviews": true,
  "includeChangelog": true,
  "includeScreenshots": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call klondikeking/wordpress-plugins-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,klondikeking/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/rgnhPTevWuZNN0gqd/builds/UQ774CWLZTp6ZIOuI/openapi.json