WordPress Plugin Reviews Scraper

Export WordPress.org plugin reviews into a spreadsheet or JSON for product feedback reports, support reviews and plugin comparisons. This WordPress plugin reviews scraper collects review text, star ratings, original publication dates and optional public replies.

Private preview: access is limited to authorized users while publication review is in progress.

Export plugin reviews in three steps

1. Paste a WordPress.org plugin link, such as https://wordpress.org/plugins/akismet/.
2. Choose the maximum number of reviews. Turn on Include replies if you need reply context.
3. Start the Actor and open Reviews. To download, select Export, choose CSV, Excel or JSON, then Download.

No WordPress login, API key or proxy configuration is needed. Leave Optional filters closed for a first run.

Inputs

Input	What to enter
Plugin links	One or more WordPress.org plugin page links, one per line. Up to 10 links. Plugin review-list links work too.
Maximum reviews	A total across all supplied plugins, from 1 to 200. The default is 5. This is a ceiling; source availability and safety limits can return fewer.
Include replies	Off by default. When on, includes up to 10 public replies from each review’s first page. Replies may come from any public forum participant.

For example:

{
  "startUrls": ["https://wordpress.org/plugins/akismet/"],
  "maxItems": 5,
  "includeReplies": false
}

In Optional filters, choose a star rating from 1 to 5 or enter publication dates as YYYY-MM-DD. Dates are inclusive and refer to the original review, rather than later replies. Leave filters empty to collect any rating and date.

Results and downloads

Each review is one dataset record. The Reviews table shows the plugin, stars, title, review text, original publication date, thread reply count, source link, stable review ID and collection timestamp.

• CSV and Excel: select Export and choose a format. Use the Reviews view for the nine review fields shown in the table. Exported field names match the JSON keys, including reviewId and extractedAt.
• Replies (first page) shows included replies separately from the original review. It is empty when replies are off or no replies were included.
• Complete JSON: choose All fields, then export as JSON to preserve nested replies, source dates and coverage information. A JSON export of a selected view contains only that view’s fields.
• Run summary explains how many reviews were saved and why collection stopped.

A genuine example, showing selected fields:

{
  "reviewId": "18979055",
  "pluginSlug": "akismet",
  "rating": 5,
  "title": "A reliable plugin",
  "reviewText": "Akismet does what it’s supposed to do — blocks spams effectively. Overall, it’s a reliable plugin that gets the job done.",
  "publishedDate": "2026-07-30",
  "sourceUrl": "https://wordpress.org/support/topic/a-reliable-plugin-2/"
}

Missing values remain unknown. In particular, a direct review link can have a null thread reply count even when some replies are visible. The source timestamps do not identify a timezone, so sourceTimezone remains null. Public author handles are omitted by default.

Use cases

• Export feedback on a plugin you maintain for product and support reporting.
• Compare public reviews of several plugins in your own spreadsheet.
• Revisit stable review IDs across exports to identify content changes in your own workflow.

The Actor extracts structured content. It does not assign sentiment, verify reviewer claims or identify developers across platforms.

WordPress plugin reviews API example

Use an Apify token authorized to access the private Actor:

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("TmegNF3u5NHdDP20M").call(run_input={
    "startUrls": ["https://wordpress.org/plugins/akismet/"],
    "maxItems": 5,
    "includeReplies": False,
})
for review in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(review["rating"], review["title"], review["sourceUrl"])

Existing integrations using plugin slugs, direct review URLs or explicit scan limits remain supported. They are not needed for the normal form workflow.

Limits and FAQ

Does it collect every review or a complete thread?

No. Collection is bounded by your maximum and internal safety limits. Optional replies come from the first topic page only. No complete-history or exact incremental-checkpoint guarantee is made.

Why are fewer reviews returned than I requested?

The plugin may have fewer matching reviews, filters may exclude records, or a source or safety limit may stop the scan. The run summary gives the reason. The review maximum is shared across plugins; earlier links can use the available total before later links are visited.

Are results sorted by review publication date?

They follow the source forum’s page order. A later reply can bring an older review forward, so the Actor does not promise publication-date sorting.

What happens if a page fails?

Already saved reviews remain available. Access restrictions, persistent rate limits or incomplete pages stop collection. The Actor respects source robots directives and does not solve access challenges.

Can I reuse the review text commercially?

Reviews are third-party user content. Public readability does not establish redistribution rights. Use the data only for an authorized purpose; commercial publication of this Actor remains subject to the outstanding reuse review.

What does a run cost?

The introductory Actor price is $1.50 per 1,000 saved original reviews ($0.0015 each), plus $0.00005 per run start at the supported memory settings. Optional first-page replies are included in the review price. A five-review run costs $0.00755 in Actor events; a 100-review run costs $0.15005 if it returns all 100.

There is no subscription or extra Actor charge for opening or downloading results. Apify can charge separately for post-run storage and dataset access. Set a maximum run charge in Apify Console to control spending; the Actor stops when that budget cannot cover another review. Collection can also stop earlier at a source or safety limit. Runs with no reviews incur only the start event. Start with the five-review example to check whether the output fits your task.

For a problem with a run, provide its Apify run ID, plugin link and the result you expected. Do not share your API token.