Trustpilot Reviews Miner

Mine product reviews from Trustpilot by product or brand name — review title, star rating and body text. Renders the listing with Playwright through a residential proxy. Built for competitor analysis, sentiment mining and product research.

Unofficial tool. This Actor is not affiliated with, sponsored by, or endorsed by Trustpilot A/S. It is an independent tool that collects publicly available information.

Why Trustpilot-only

Trustpilot is the one major review portal whose protection a lightweight Playwright + residential-proxy actor can clear reliably. G2 and Capterra sit behind hard DataDome / anti-bot CAPTCHA walls that need dedicated anti-bot handling, so they are shipped as their own actors (g2-reviews-miner, capterra-reviews-miner) rather than bolted onto this one. All three share the same output schema, so their datasets union directly (see Integration below).

Features

• Trustpilot — real reviews with star ratings, via the residential proxy.
• Product / brand name input — slack, hubspot, etc. Trustpilot keys on the brand domain, so slack becomes trustpilot.com/review/slack.com.
• Rendered extraction — Playwright reads the listing in a real browser.
• Residential proxy — Trustpilot is Cloudflare-protected; enabled by default.
• Clean typed fields — source, product, title, rating, body, url, fetchedAt.
• Result cap — maxResults (1–300).

What people use it for

• Competitor analysis — compare review sentiment across portals (union with G2/Capterra actors).
• Sentiment mining — feed body text into an NLP pipeline.
• Product research — what users praise and complain about.
• Vendor evaluation — gather real-user signal before a purchase.
• Brand monitoring — track your own product's reviews.

Input

productName is required.

Field	Type	Default	What it does
productName (required)	string	slack	Product / brand to mine, e.g. slack, hubspot.
maxResults	integer	50	Cap on reviews to return (1–300).
proxyConfiguration	object	residential	Trustpilot is Cloudflare-protected; residential proxy is the default.

Input example

{
  "productName": "slack",
  "maxResults": 50
}

Output

One record per review:

source, product, title, rating, body, url, fetchedAt.

Export the dataset as JSON, CSV, Excel, XML or JSONL from the Console, or pull it programmatically through the Apify API.

Integration with G2 / Capterra actors

The three review-mining actors (trustpilot-reviews-miner, plus the upcoming g2-reviews-miner and capterra-reviews-miner) emit identical fields, only differing by the source tag. To build a unified review dataset:

1. Run each actor for the same productName.
2. Union their datasets (Apify's Combine datasets tool, or a single dataset.getItems() merge in your code).
3. Group/analyze by source — Trustpilot skews consumer/post-purchase, G2 & Capterra skew B2B.

Because every record carries its source, sentiment divergence across portals is directly comparable (all use a 1–5 star scale, so rating is comparable as-is).

If a run returns 0 records, check the run log: a Trustpilot blocked by anti-bot protection warning means the proxy IP was challenged — re-run, or switch to a different residential country/exit.

How to use it

1. Click Try for free (or Start).
2. Fill in productName (the default already produces a working run).
3. Press Start and watch the log; results stream into the dataset.
4. When the run finishes, open Output/Storage and export as JSON, CSV or Excel.

Runs can be scheduled and wired into Slack, Google Sheets, Zapier, Make, webhooks or your own backend.

Proxy configuration

Accepts a standard Apify proxy configuration object. Residential proxy is the default because the target rate-limits datacenter IPs; you can select a specific exit country or supply your own proxy URLs.

{
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Pricing

Billed on Apify's pay-per-event model: a small charge when a run starts, plus a charge per result written. A run that finds nothing costs only the start event.

FAQ

Why only Trustpilot?

G2 and Capterra are behind DataDome anti-bot CAPTCHA walls that a plain Playwright actor can't pass. They're separate actors with dedicated anti-bot handling. All three share the output schema so you can union them.

Why a residential proxy?

Trustpilot sits behind Cloudflare and blocks datacenter IPs. Residential routing returns the real review listings.

How current are the reviews?

It captures what Trustpilot displays at scrape time. For trends, schedule runs and accumulate, keyed by review URL to dedupe.

Legal and responsible use

This Actor collects only publicly available information. You are responsible for how you use the data, including compliance with the target site's Terms of Service, robots directives, copyright, and data protection law such as GDPR and CCPA. Do not use it to gather personal data without a lawful basis.

Support and feedback

Found a bug, hit a site change, or need an extra field? Open a ticket on the Issues tab. Feature requests and custom-scraper enquiries are welcome through the same channel.