WordPress Plugin Reviews Scraper avatar

WordPress Plugin Reviews Scraper

Pricing

Pay per event

Go to Apify Store
WordPress Plugin Reviews Scraper

WordPress Plugin Reviews Scraper

Scrape public WordPress.org plugin reviews with ratings, reviewers, replies, URLs, timestamps, and plugin rating summaries.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Scrape public WordPress.org plugin reviews, star ratings, reviewer metadata, reply counts, and plugin rating summaries from WordPress.org review pages.

What does WordPress Plugin Reviews Scraper do?

WordPress Plugin Reviews Scraper collects public review data from WordPress.org plugin support forums. Give it plugin slugs such as woocommerce, contact-form-7, or elementor, and it returns structured review rows that are ready for spreadsheets, BI tools, dashboards, and monitoring workflows.

The actor is designed for public review intelligence. It does not submit reviews, log into WordPress.org, or access private account data.

Who is it for?

  • ๐Ÿ”Œ Plugin vendors tracking their own product reputation
  • ๐Ÿงฐ WordPress agencies monitoring plugins used by clients
  • ๐Ÿ›’ WooCommerce and ecommerce teams watching support quality signals
  • ๐Ÿ“ˆ Product marketers comparing sentiment across competing plugins
  • ๐Ÿงช Due-diligence teams checking plugin reliability before adoption
  • ๐Ÿค Support managers finding fresh negative reviews that need follow-up

Why use this actor?

WordPress.org review pages are useful but hard to analyze at scale. This actor converts paginated review listings into consistent rows with review titles, star ratings, reviewers, replies, timestamps, and URLs.

You can run it on a schedule to build a review timeline, export recent low-star reviews, or compare review volume across multiple plugins.

What data can you extract?

FieldDescription
pluginSlugWordPress.org plugin slug
pluginNamePlugin display name from the review page
pluginUrlPublic plugin URL
reviewsUrlPublic reviews page URL
reviewTitleReview topic title
reviewUrlReview topic URL
ratingStar rating, when available
reviewerNamePublic reviewer display name
reviewerUsernameWordPress.org profile slug
reviewerUrlPublic reviewer profile URL
participantsNumber of thread participants
repliesNumber of replies
lastActivityTextRelative last activity text shown by WordPress.org
lastActivityUrlURL for the latest activity
lastReplyAuthorNamePublic name of the latest reply author
reviewBodyOptional review body text from the topic page
averageRatingPlugin average rating
totalReviewsPlugin total review count
fiveStarReviews5-star review bucket count
oneStarReviews1-star review bucket count
scrapedAtISO timestamp when the row was saved

How much does it cost to scrape WordPress plugin reviews?

This actor uses pay-per-event pricing. You pay a small start fee and a per-review-row fee.

Current pricing:

  • Run started: $0.005 per run
  • Review row (BRONZE): $0.000037894 per review
  • Review row (FREE): $0.000043578 per review
  • Review row (SILVER): $0.000029557 per review
  • Review row (GOLD): $0.000022736 per review
  • Review row (PLATINUM): $0.000015157 per review
  • Review row (DIAMOND): $0.000010610 per review

Typical usage examples:

  • Scrape 25 recent WooCommerce reviews for a quick check
  • Scrape 100 low-star reviews for support triage
  • Scrape multiple plugin slugs weekly for reputation monitoring

How to use it

  1. Open the actor on Apify.
  2. Add one or more WordPress.org plugin slugs.
  3. Choose the maximum number of reviews per plugin.
  4. Optionally filter by star rating.
  5. Optionally enable review body extraction.
  6. Start the run.
  7. Export the dataset as JSON, CSV, Excel, XML, or via API.

Input options

Plugin slugs

Use WordPress.org plugin slugs such as:

["woocommerce", "contact-form-7", "elementor"]

Start URLs

You can also provide public WordPress.org URLs:

[
{ "url": "https://wordpress.org/plugins/woocommerce/" },
{ "url": "https://wordpress.org/support/plugin/contact-form-7/reviews/" }
]

Maximum reviews per plugin

Use maxReviewsPerPlugin to control run size. Start small for tests, then increase the limit for historical exports.

Star rating filter

Use starFilter to collect only reviews with a specific rating. This is useful for support workflows focused on negative reviews.

Include review body

Enable includeReviewBody when you need the text of each review. This opens each review topic page, so it is slower than listing-only mode.

Example input

{
"pluginSlugs": ["woocommerce"],
"maxReviewsPerPlugin": 25,
"starFilter": "all",
"includeRatingSummary": true,
"includeReviewBody": false
}

Example output

{
"pluginSlug": "woocommerce",
"pluginName": "WooCommerce",
"pluginUrl": "https://wordpress.org/plugins/woocommerce/",
"reviewsUrl": "https://wordpress.org/support/plugin/woocommerce/reviews/",
"reviewTitle": "Outstanding eCommerce Solution for WordPress Stores",
"reviewUrl": "https://wordpress.org/support/topic/outstanding-ecommerce-solution-for-wordpress-stores/",
"rating": 5,
"reviewerName": "manishranawp",
"reviewerUsername": "manishranawp",
"participants": 1,
"replies": 0,
"lastActivityText": "1 day, 2 hours ago",
"averageRating": 4.5,
"totalReviews": 4802,
"scrapedAt": "2026-06-11T08:00:00.000Z"
}

Review monitoring workflows

  • Run daily for your own plugin and alert on new 1-star reviews.
  • Track review volume after releases.
  • Compare average rating and review velocity across competitor plugins.
  • Export review topics to a support CRM.
  • Build a dashboard of reply counts and unresolved reputation issues.

Tips for best results

  • Use plugin slugs when possible; they are the most stable input format.
  • Start with maxReviewsPerPlugin set to 25 for a quick validation run.
  • Enable includeReviewBody only when you need full review text.
  • Use starFilter: "1" or "2" for support triage.
  • Schedule recurring runs to monitor changes over time.

Integrations

Use this actor with:

  • Google Sheets or Excel exports for product teams
  • Slack or email alerts through Apify integrations
  • BI dashboards that ingest Apify datasets
  • Support queues for low-star review follow-up
  • Data warehouses via the Apify API

API usage: Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/wordpress-plugin-reviews-scraper').call({
pluginSlugs: ['woocommerce'],
maxReviewsPerPlugin: 25,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage: Python

from apify_client import ApifyClient
client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/wordpress-plugin-reviews-scraper').call(run_input={
'pluginSlugs': ['woocommerce'],
'maxReviewsPerPlugin': 25,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage: cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~wordpress-plugin-reviews-scraper/runs?token=$APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"pluginSlugs":["woocommerce"],"maxReviewsPerPlugin":25}'

MCP usage

Use this actor from MCP-compatible tools through Apify MCP Server:

https://mcp.apify.com/?tools=automation-lab/wordpress-plugin-reviews-scraper

Claude Code setup:

$claude mcp add apify-wordpress-reviews https://mcp.apify.com/?tools=automation-lab/wordpress-plugin-reviews-scraper

Claude Desktop JSON configuration:

{
"mcpServers": {
"apify-wordpress-reviews": {
"url": "https://mcp.apify.com/?tools=automation-lab/wordpress-plugin-reviews-scraper"
}
}
}

Example prompts:

  • "Scrape the latest 25 WooCommerce plugin reviews and summarize negative themes."
  • "Find 1-star reviews for contact-form-7 and group them by issue type."
  • "Compare recent review activity for three WordPress plugins."

Legality and ethics

This actor collects publicly available WordPress.org review pages. It does not bypass login, scrape private user data, or submit content. Always use the data responsibly, respect WordPress.org terms, and avoid excessive run sizes.

Troubleshooting

The actor saved fewer reviews than requested

The plugin may have fewer public reviews than your requested limit, or your star filter may narrow the available pages.

I do not see review body text

Enable includeReviewBody. Listing mode is faster and saves metadata only.

My URL was rejected

Use a WordPress.org plugin URL or support review URL, for example https://wordpress.org/plugins/woocommerce/.

Explore other automation-lab actors on Apify for ecommerce, software review, lead generation, and public directory monitoring workflows.

Changelog

  • 0.1.0 โ€” Initial version for public WordPress.org plugin review listings.

Limitations

WordPress.org shows relative timestamps such as "1 day ago" in review listings. The actor preserves those public values. Exact absolute timestamps may be available in page attributes for some rows and can be added in a future version if needed.

Support

If you need a field added, a different WordPress.org review workflow, or a monitoring integration, open an issue on the actor page.

Development notes

The actor is HTTP-only and uses WordPress.org public HTML and Markdown output. It is intentionally lightweight and runs with 256 MB memory.

FAQ

Can I scrape multiple plugins in one run?

Yes. Add multiple plugin slugs to pluginSlugs.

Can I collect only bad reviews?

Yes. Set starFilter to "1" or "2".

Does this require a WordPress.org account?

No. Reading reviews is public. Login is only required to submit or reply to reviews.

Does it use a browser?

No. The actor uses HTTP requests only, which keeps runs fast and inexpensive.

Can I schedule it?

Yes. Use Apify schedules to run it daily, weekly, or after plugin releases.