WordPress Plugin Directory Scraper
Pricing
from $0.60 / 1,000 plugin records
WordPress Plugin Directory Scraper
Scrape WordPress.org plugin metadata, ratings, installs, authors, tags, versions, and update signals from public searches and slugs.
Pricing
from $0.60 / 1,000 plugin records
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
2
Monthly active users
23 days ago
Last modified
Categories
Features
Share
Collect public WordPress.org plugin directory metadata by keyword or known slug, including available versions, compatibility labels, install estimates, ratings, updates, vendor links and optional full sections. Retain query context and source links for your own ecosystem research. Directory metadata does not install, execute, security-audit or independently endorse a plugin.
Quick start
Use a focused query or a few known slugs with a small shared record cap. The existing input combines SEO and security searches with WooCommerce and Contact Form 7 lookups:
{"queries": ["seo", "security"],"slugs": ["woocommerce", "contact-form-7"],"maxItems": 50,"perPage": 50,"includeTags": true,"includeRatingsBreakdown": true,"includeSections": false,"locale": "en_US"}
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Existing public Store examples:
- Top WordPress SEO plugins
- Monitor known WordPress plugin slugs
- Security plugin details with sections
What you get
One saved plugin record keyed by slug, with sourceType, query and observed per-query rank for search results, or direct-slug context. Fields include exposed compatibility, directory counts, update dates, author and project references. Optional tags, rating breakdowns and full HTML sections add source detail without verifying plugin behavior or code safety.
Who is it for?
- Plugin product teams reviewing source-linked competitor and category samples.
- WordPress agencies collecting metadata before their own stack or compatibility review.
- Ecosystem analysts comparing directory estimates, ratings and update context.
- Partnership researchers retaining public author and project references for manual review.
How you can use the data
- Inspect an SEO or security category sample. Use the existing keyword queries and retain query, rank, slug and directory counts. Search rank is the observed query result order rather than a ranking by installs, safety or product quality.
- Review known competitors directly. Run the existing woocommerce, contact-form-7 or wordpress-seo slugs without search queries when those targets matter most. Searches run first when both modes are supplied, so the shared cap can be consumed before later direct slugs.
- Prepare a compatibility review. Compare requires, tested, requires_php, version and last_updated for your selected plugins. These are published directory labels rather than proof that a plugin works on your site or is free of vulnerabilities.
- Keep your own market observations. Store slug, active_installs, downloaded, rating, support counts and source dates in your destination before comparing snapshots. Install counts are estimates, downloads are not active users, and repeat reports or alerts are downstream work.
Input settings
Search queries
Use queries to discover plugins by keyword. Submit up to 100 terms of at most 500 characters each. The Actor uses direct public access without a proxy option.
Example queries:
seosecuritywoocommerceformsanalyticspage builderbackup
Plugin slugs
Use slugs when you already know the plugin.
Examples:
woocommercecontact-form-7seo-by-rank-mathwordpress-seoelementor
You can also paste public WordPress.org plugin detail URLs. Submit up to 100 slugs or URLs of at most 500 characters each.
Maximum plugin records
Use maxItems to cap the number of dataset rows.
Start small, inspect the output, then increase the limit for larger research jobs.
Search page size
Use perPage to control how many plugins the WordPress.org search API returns per page. The maximum is 100. Smaller values are useful for quick tests.
Optional fields
Enable optional fields when you need more detail:
includeTagsadds plugin tagsincludeRatingsBreakdownadds rating counts by star levelincludeSectionsadds larger full-text HTML sectionslocalerequests a WordPress.org locale when supported
With no queries or slugs, the source uses seo. When both are supplied, queries are processed first and direct slugs use remaining shared capacity. Direct-slug rank is null, and duplicate slugs are saved once inside a run. A known slug does not guarantee a saved row when the source is unavailable or the cap is already consumed.
Output data
The existing illustrative directory row contains historical example values rather than current plugin measurements:
{"sourceType": "query","query": "seo","rank": 1,"slug": "seo-by-rank-math","name": "Rank Math SEO – AI SEO Tools to Dominate SEO Rankings","version": "1.0.273","author": "Rank Math SEO","author_profile": "https://profiles.wordpress.org/rankmath/","homepage": "https://rankmath.com/","requires": "6.7","tested": "7.0","requires_php": "7.4","rating": 96,"ratings_count": 7453,"active_installs": 4000000,"downloaded": 185207621,"last_updated": "2026-06-30 11:48am GMT","added": "2018-11-19","plugin_url": "https://wordpress.org/plugins/seo-by-rank-math/"}
| Field | Description |
|---|---|
sourceType | Whether the row came from a search query or direct slug lookup |
query | Search query that produced the plugin, when applicable |
rank | Plugin rank within that query |
slug | WordPress.org plugin slug |
name | Plugin name |
version | Current plugin version |
author | Plugin author name or organization |
author_profile | WordPress.org author profile URL |
homepage | Vendor or project homepage when available |
requires | Required WordPress version |
tested | WordPress version tested up to |
requires_php | Required PHP version |
rating | Aggregate rating score |
ratings_count | Number of ratings |
ratings_breakdown | Optional 1-star through 5-star rating counts |
active_installs | Active install estimate |
downloaded | Total downloads |
last_updated | Last updated timestamp from WordPress.org |
added | Date the plugin was added |
tags | Optional WordPress.org plugin tags |
short_description | Short plugin summary |
description_html | Optional full description HTML |
sections | Optional full plugin sections |
screenshots | Screenshot metadata when available (omitted when unavailable) |
support_url | WordPress.org support URL when available |
commercial_support_url | Commercial support URL when available |
support_threads | Recent support thread count |
support_threads_resolved | Recent resolved support thread count |
download_link | Plugin ZIP download link |
plugin_url | Public WordPress.org plugin URL |
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
A run has a start event when valid extraction begins. A completed empty search or missing-slug run can still retain its start charge.
An item event applies to each saved plugin record. Duplicate or missing direct-slug targets do not create extra records. Extraction stops when the remaining charge limit cannot cover another item.
Keep the shared record cap modest and request full sections only when useful. Platform usage can also apply. See the live Pricing tab for current rates and tiers.
Tips for best results
- Choose discovery or direct targets deliberately. Use only slugs when known plugins must get the available cap first.
- Keep query context with rank. Observed search order does not measure install popularity or code quality.
- Request full sections only when needed. Long descriptions and changelogs can increase dataset size.
- Keep counts in context. Active installs are estimates, while ratings and support figures reflect the directory's exposed values.
- Review compatibility separately. Directory requirements and tested versions do not replace your own site checks or a security audit.
- Retain slugs across observations. Your own scheduled exports and comparison logic support longitudinal research.
Limits and caveats
- The actor returns public directory metadata.
- It does not log in to WordPress.org.
- It does not install, audit, or execute plugin code.
- Active install counts are directory estimates.
- Some plugin fields may be missing when WordPress.org does not provide them.
- Full sections can be large and may increase dataset size.
The Actor fetches public directory metadata over HTTP without a WordPress login. It does not scrape individual review text, install plugin ZIPs or execute plugin code. Vendor homepages and author-profile links are references rather than verified contacts or permission to send outreach.
The shared record cap and changing query results bound observed coverage. A missing or unavailable direct slug can finish without a row, and an empty search is recorded in RUN-SUMMARY. Source request, dataset or billing errors can fail a run after earlier records were saved.
Runs default to 256 MiB memory and support existing 512 MiB settings, with a finite timeout of at most five minutes. Processing stops before that deadline or when item capacity is exhausted, retaining useful rows and reporting pending inputs in RUN-SUMMARY. This report is not an automatic continuation input. Start a new run rather than resurrecting a run that already began extraction. Summary storage is optional and can fail without removing saved rows.
An individual source response is limited to 8 MiB. If full sections exceed that limit, reduce the page size or turn full sections off.
This actor extracts publicly available plugin directory metadata. You are responsible for using the data lawfully and respecting WordPress.org terms, privacy rules, and applicable regulations.
Do not use exported data for spam, abusive automation, or misleading outreach.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~wordpress-plugin-directory-scraper/runs?token=YOUR_APIFY_TOKEN' \-H 'Content-Type: application/json' \-d '{"queries":["seo"],"maxItems":25}'
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/wordpress-plugin-directory-scraper').call({queries: ['seo'],slugs: ['woocommerce'],maxItems: 25,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
from apify_client import ApifyClientimport osclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/wordpress-plugin-directory-scraper').call(run_input={'queries': ['security'],'maxItems': 25,})items = client.dataset(run['defaultDatasetId']).list_items().itemsprint(items)
MCP and AI agents
You can ask your AI assistant to collect data with WordPress Plugin Directory Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's WordPress Plugin Directory Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/wordpress-plugin-directory-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use WordPress Plugin Directory Scraper by Fetch Cat, or give it the identifier fetch_cat/wordpress-plugin-directory-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s WordPress Plugin Directory Scraper to collect up to 5 SEO plugin records with tags and rating breakdowns on and full sections off. Keep query rank and install estimates without treating them as a security or quality verdict.”
- “Retrieve the known woocommerce and contact-form-7 plugin slugs with no search queries, a two-record cap and full sections off. Keep published compatibility and update fields without installing or running code.”
- “Collect up to 5 security plugin directory records with full sections on. Keep author, source URL and available support context without claiming that the listed plugins are safe or collecting individual review text.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Why did I get fewer records than the cap?
The source can have fewer results, duplicate plugins can be skipped, or the time budget can leave pending work. Queries use the cap before later direct slugs when both modes are supplied.
Why is an optional field empty?
The directory does not provide every field for every plugin. A homepage, PHP requirement, screenshot list or support statistic can be absent.
Should I enable full sections?
Only when you need long descriptions, changelogs, installation notes or FAQ content. Keep them off for a compact metadata scan.
Does this check plugin security or collect reviews?
No. This collects directory metadata. It does not audit or run code and does not collect individual review text.
Related Actors
- GitHub Repositories Search Scraper — Discover public GitHub repositories and available project metadata for open-source software research.
- Hacker News Search Scraper — Find public Hacker News stories and comments when researching developer discussions around tools.
- Arxiv Paper Search Scraper — Retrieve research paper metadata and abstracts for technical literature discovery.
- Website Contact Finder — Find publicly listed contact details on websites for your own manual business review.
- npm Packages Search Scraper — Collect public npm package metadata, repository links and available download counts when researching JavaScript tools used alongside WordPress.
Release history
28 Jul 2026
- Feature: Added ready-to-run Apify Store example tasks.
- Feature: Launched WordPress Plugin Directory Scraper publicly on Apify Store.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥