WordPress Theme Directory Search Scraper is a BrowserAct Bot template for collecting structured public theme records from WordPress.org search results. Configure a WordPress base URL, keyword, and result count, then run the Bot to return ranked theme links and screenshot image URLs for theme discovery, market research, design inspiration, or automation workflows.
What Does BrowserAct WordPress Theme Directory Search Scraper Do?
This template opens WordPress.org Theme Directory search results, extracts public theme cards, follows pagination when needed, and returns one structured record per theme.
Key Features
- Extract public WordPress.org theme search results without requiring a login.
- Capture theme name, theme URL, screenshot image URL, rank, and search keyword.
- Preserve optional fields as empty when the search listing does not expose them.
- Configure base URL, keyword, and count.
- Continue through public pagination until the requested count is reached or results run out.
What Data Can I Extract from WordPress.org?
| Field | Description |
|---|---|
rank |
Search result position assigned by the Bot. |
theme_name |
Public theme name. |
theme_url |
WordPress.org theme page URL. |
screenshot_url |
Screenshot image URL shown on the theme card. |
short_description |
Description when visible. |
author |
Author or creator when visible. |
rating |
Rating when visible. |
review_count |
Review count when visible. |
active_installations |
Active installation count when visible. |
last_updated |
Last updated date when visible. |
theme_version |
Theme version when visible. |
tested_wp_version |
Tested WordPress version when visible. |
tags |
Tags or subject categories when visible. |
search_keyword |
Keyword used for the run. |
How to Use WordPress Theme Directory Search Scraper
- Click Run task.
- Enter the WordPress base URL.
- Enter a theme style, niche, layout, or feature keyword.
- Set how many theme records to collect.
- Run the Bot and review the structured theme 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 | blog |
Search keyword used in the theme directory. |
count |
Yes | 20 |
Maximum number of theme records to return. |
Example Output
{
"results": [
{
"rank": 1,
"theme_name": "Today Blog",
"theme_url": "https://wordpress.org/themes/today-blog/",
"screenshot_url": "https://i0.wp.com/themes.svn.wordpress.org/today-blog/1.0.1/screenshot.png?w=post-thumbnail&strip=all",
"short_description": "",
"author": "",
"rating": "",
"review_count": "",
"active_installations": "",
"last_updated": "",
"theme_version": "",
"tested_wp_version": "",
"tags": "",
"search_keyword": "blog"
}
]
}
How Does it Work?
BrowserAct opens {base_url}/themes/search/{keyword}/ for the first page of WordPress.org Theme Directory results. Each public result card contains a theme link, theme name, and screenshot image URL.
For larger counts, BrowserAct opens pagination pages in the format {base_url}/themes/search/{keyword}/page/{page_number}/. It keeps unique theme URLs, assigns continuous ranks across pages, and stops when it reaches count or when a search page returns no theme 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 Theme Directory Results?
WordPress theme directory data helps teams discover design patterns, compare public themes, collect screenshot references, monitor theme categories, and route theme metadata into research reports, databases, or agent workflows.
Who Can Use This Template?
- WordPress agencies researching theme options.
- Designers collecting public theme inspiration.
- Product teams monitoring theme categories and competitors.
- Content teams building website design research lists.
- Automation builders routing theme metadata into spreadsheets, databases, alerts, or agents.
How Many Results Can You Scrape?
Use count to control the number of theme records returned. WordPress.org typically shows 12 theme 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 theme 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

