WordPress Plugin Directory Search Scraper is a BrowserAct Bot template for collecting structured public plugin records from WordPress.org search results. Configure a WordPress base URL, keyword, and result count, then run the Bot to return ranked plugin metadata for WordPress ecosystem research, SEO tooling analysis, app discovery, or automation workflows.
What Does BrowserAct WordPress Plugin Directory Search Scraper Do?
This template opens WordPress.org Plugin Directory search results, extracts public plugin cards, follows pagination when needed, and returns one structured record per plugin.
Key Features
- Extract public WordPress.org plugin results without requiring a login.
- Capture plugin name, URL, description, author, rating, review count, active installations, tested WordPress version, and search keyword.
- Configure base URL, keyword, and count.
- Continue through plugin directory pagination until the requested count is reached.
- Preserve optional fields as empty when the search listing does not expose them.
What Data Can I Extract from WordPress.org?
| Field | Description |
|---|---|
rank |
Search result position assigned by the Bot. |
plugin_name |
Public plugin name. |
plugin_url |
WordPress.org plugin page URL. |
short_description |
Plugin description shown on the search card. |
author |
Author or contributor shown on the listing. |
rating |
Rating score shown on the plugin card. |
review_count |
Number of reviews shown beside the rating. |
active_installations |
Active installation count shown by WordPress.org. |
last_updated |
Last updated date when visible. |
tested_wp_version |
Tested WordPress version shown on the card. |
plugin_version |
Plugin version when visible. |
tags |
Tags or categories when visible. |
search_keyword |
Keyword used for the run. |
How to Use WordPress Plugin Directory Search Scraper
- Click Run task.
- Enter the WordPress base URL.
- Enter a plugin, category, feature, or ecosystem keyword.
- Set how many plugin records to collect.
- Run the Bot and review the structured plugin results.
- Reuse the Bot with another keyword or connect the output to your workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
base_url |
Yes | https://wordpress.org |
WordPress.org base URL without a trailing slash. |
keyword |
Yes | seo |
Search keyword used in the plugin directory. |
count |
Yes | 20 |
Maximum number of plugin records to return. |
Example Output
{
"results": [
{
"rank": 1,
"plugin_name": "Rank Math SEO - AI SEO Tools to Dominate SEO Rankings",
"plugin_url": "https://wordpress.org/plugins/seo-by-rank-math/",
"short_description": "Grow your organic traffic and AI visibility with powerful SEO tools, XML sitemaps, Schema automation, and built-in AI SEO, all in one place.",
"author": "Rank Math SEO",
"rating": "5",
"review_count": "7491",
"active_installations": "4+ million",
"last_updated": "",
"tested_wp_version": "7.0.4",
"plugin_version": "",
"tags": "",
"search_keyword": "seo"
}
]
}
How Does it Work?
BrowserAct opens {base_url}/plugins/search/{keyword}/ for the first page of WordPress.org Plugin Directory results. Each search page contains public plugin cards with stable fields for name, URL, description, author, rating, review count, active installations, and tested WordPress version.
For larger counts, BrowserAct opens the next public pagination page in the format {base_url}/plugins/search/{keyword}/page/{page_number}/. It keeps collecting unique plugin URLs, assigns continuous ranks, and stops when it reaches count or when the directory has no more result cards.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the Data You Need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.
Step 2: Let BrowserAct Build and Test the Bot
BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.
Step 3: Run the Bot and Review the Result
When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.
Why Scrape WordPress Plugin Directory Results?
WordPress plugin search data helps teams compare plugin categories, monitor ecosystem trends, identify popular tools, evaluate competitors, and route plugin metadata into research reports, dashboards, lead lists, or agent workflows.
Who Can Use This Template?
- WordPress agencies researching plugin options.
- SEO teams comparing WordPress SEO tools.
- Product teams monitoring plugin categories and competitors.
- Developer relations teams tracking ecosystem adoption.
- Automation builders routing plugin metadata into spreadsheets, databases, alerts, or agents.
How Many Results Can You Scrape?
Use count to control the number of plugin records returned. WordPress.org typically shows 20 plugin cards per page, and BrowserAct follows pagination until the requested count is reached or public results run out.
Automation and Export
BrowserAct returns structured WordPress plugin records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com
