WordPress Plugin Reviews Scraper

What does WordPress Plugin Reviews Scraper do?

WordPress Plugin Reviews Scraper extracts public review topics from the WordPress.org support reviews pages. It supports plugin and theme review listings as well as individual public support-topic URLs, then follows selected topics to capture the original reviewer, rating, title, body, publication text, profile URL, and reply counts.

The Actor uses server-rendered HTTPS pages and a Cheerio crawler, so it is lightweight and predictable for public support content. Requests are bounded, delayed politely, restricted to official WordPress.org paths, and reported truthfully when a page is unavailable. On Apify, you can run it by API, schedule recurring review monitoring, export datasets, connect integrations, and inspect request and diagnostic summaries.

Why use WordPress Plugin Reviews Scraper?

Use the output for public customer-feedback research, plugin comparison, product-quality monitoring, support-team analysis, sentiment preparation, and review-count inventories. Stable review IDs help deduplicate repeated runs. Dataset rows contain only source-backed review data and provenance; the key-value summary reports numeric counts without diagnostic messages or request URL lists.

How to use WordPress Plugin Reviews Scraper

1. Open the Input tab and provide one or more public review listing or topic URLs.
2. Set maxItems and maxPages to bound the crawl.
3. Enable followPagination only when you need additional pages from the same product review scope.
4. Start the Actor and review the dataset and OUTPUT_SUMMARY record.

Input

startUrls accepts plugin or theme review listings such as /support/plugin/woocommerce/reviews/ and individual /support/topic/.../ URLs. maxItems caps review records, maxPages bounds listing pagination, and followPagination follows only same-scope listing pages. requestDelayMs, maxConcurrency, and userAgent control polite public access. proxyConfiguration is optional and is used only when you have an approved Apify Proxy configuration.

{
  "startUrls": [
    { "url": "https://wordpress.org/support/plugin/woocommerce/reviews/" }
  ],
  "maxItems": 25,
  "maxPages": 1,
  "followPagination": false,
  "requestDelayMs": 600,
  "maxConcurrency": 1
}

Output

Dataset rows have stable IDs, product scope, review title/body, rating, reviewer metadata, source URLs, and extraction timestamps. Run status, request totals, and numeric diagnostic counts are kept in OUTPUT_SUMMARY. Saved review rows produce status: "SUCCEEDED"; later request or metadata issues use dataStatus: "PARTIAL". A genuine empty search is SUCCEEDED with dataStatus: "NO_RESULTS". A source failure before any review row is FAILED with dataStatus: "FAILED" and no diagnostic dataset row.

{
  "recordId": "wordpress_review_<sha256-prefix>",
  "recordType": "wordpress-review",
  "source": "WordPress.org public support reviews",
  "provenance": "wordpress_org_support_reviews_html_v1",
  "contentType": "plugin",
  "productSlug": "woocommerce",
  "title": "Great support",
  "body": "This is a helpful plugin.",
  "rating": 5,
  "reviewerName": "A public reviewer",
  "sourceUrl": "https://wordpress.org/support/topic/example/",
  "scrapedAt": "2026-09-08T00:00:00.000Z"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Field	Description
recordId, reviewId, recordType	Stable review identity and normalized row type.
contentType, productSlug, productName	Plugin or theme scope from the public listing.
title, body, rating	Review title, original topic body, and star rating.
reviewerName, reviewerUsername, reviewerProfileUrl	Public reviewer signals when exposed.
publishedAt, replyCount, participantCount	Public topic timing and conversation counts.
sourceUrl, listingUrl, provenance	Direct evidence and extraction lineage.

Pricing / Cost estimation

How much does it cost to scrape WordPress reviews?

The Actor makes one request for each listing page and at most one request per selected topic, subject to maxItems, maxPages, retries, and pagination. Keeping maxConcurrency at 1 and using the default delay makes resource use predictable and considerate. Your Apify plan determines the final cost; small runs may fit within the platform free tier.

Tips or advanced options

Use an individual topic URL for a precise review lookup. Use a listing URL with a small maxItems for a quick sample, then increase maxPages and enable same-scope pagination for an inventory. Review counts and page markup change over time, and some topics may be deleted or protected. JavaScript-only or login-gated content is reported rather than bypassed.

FAQ, disclaimers, and support

Only public WordPress.org support pages are in scope. The Actor does not log in, collect private forum content, bypass CAPTCHAs or access controls, or mutate source pages. You are responsible for complying with WordPress.org terms, applicable law, and any required permission. Use the Issues tab for feedback or request a custom parser when a different public forum needs support.

Local verification

npm ci
npm test
npm run lint
apify validate-schema
apify run --purge --input-file test/inputs/default.json
npm run validate