Trustpilot Reviews Scraper (no login, monitor new reviews)

Read Trustpilot reviews for any business by domain or review-page URL: one flat row per review with rating, title, text, dates, verification flag, likes and the company's reply. No Trustpilot account, no login, no reviewer identity of any kind.

What you get

Real rows from the example dataset (business www.notion.so):

rating	title	isVerified	publishedAt	replyText
1	"When you move to Notion half of your life..."	false	2026-09-21	— (no reply yet)
1	"Public links blocked across my workspace with no clear support"	false	2026-09-17	— (no reply yet)
2	"Support is next to non-existent on their business accounts"	false	2026-09-14	— (no reply yet)

Full row (review): id, url, rowType, businessDomain, businessName, rating, title, text, language, publishedAt, experiencedAt, isVerified, verificationSource, likes, replyText, replyPublishedAt, query, scrapedAt. With includeBusinessSummary: true, one extra rowType: business row per business adds trustScore, stars, numberOfReviews, categories, website, claimed.

Not collected, ever: the reviewer's name, id, avatar, country or their review count.

Use cases

• Pull every review of your own business (or a competitor's) as structured rows for a spreadsheet or a dashboard, without a reviewer name in sight.
• Watch a business in monitor mode and get an alert the moment a new review lands, so you can reply fast.
• Read the company's own replies across many reviews at once to audit response coverage and turnaround.

Try it in 10 seconds

Hit Start/Try it — the input already works: businesses: ["www.notion.so"], maxReviewsPerBusiness: 100, sort: "recency", maxItems: 100, nothing required.

To get alerted the moment a new review lands: save the task, set Mode to monitor, and put it on a schedule (Apify → Schedules → cron 0 */4 * * * every 4 hours). Each run then returns only reviews new or changed since the previous check, ready for a webhook or Telegram alert.

How it works

1. Each domain or URL you give resolves to a Trustpilot business (trustpilot.com/review/<domain>).
2. The actor reads that business's review pages (?page=N&sort=...&languages=...) 20 reviews at a time until it reaches maxReviewsPerBusiness, the last page (fewer than 20 reviews), or a page whose reviews were already seen.
3. A domain Trustpilot has no page for comes back as a legitimate "not found" - nothing is pushed for it, and no result event is charged.
4. Trustpilot's structured page state loads only through Apify Web Unblocker; every other proxy tier gets a verification wall on this site, so the actor uses Unblocker from the first request.

Input

Field	Meaning	Default
businesses	Trustpilot domains or review-page URLs	["www.notion.so"]
maxReviewsPerBusiness	Stop scanning a business after this many reviews	100
sort	recency or relevance	recency
language	all or a Trustpilot language code	all
minRating	Drop reviews rated below this (1-5)	1
includeBusinessSummary	Also push one summary row per business	false
maxItems	Stop after this many rows overall	100
mode	scrape or monitor (only new/changed reviews since last run)	scrape
monitorStateId, webhookUrl, telegramBotToken, telegramChatId	Monitor-mode state key and alert targets	empty

Pricing

Event	Price
result	$0.002 per row ($2 per 1,000)
monitor-check	$0.006 per monitor run
change	$0.002 per new/changed review

Charged only for rows actually pushed. Trustpilot is read through Apify Web Unblocker (roughly $0.0015 per page of 20 reviews); this platform usage is billed to you on top of the actor's own events, same as any other Unblocker-based actor.

Why this actor

• No reviewer identity in the output at all - not a name, not an avatar, not a country. Just what the business itself needs: the review content and its own reply.
• Monitor mode with webhook and Telegram alerts the moment a new review is posted.
• A business Trustpilot has no page for is reported as "not found", never as a silent empty run.

Limits

• Reviews come from Trustpilot's own public review pages; a business with reviews hidden behind a paywall or removed by Trustpilot will not appear.
• minRating is applied after fetching, so a business with mostly low ratings may need more maxReviewsPerBusiness to surface enough high-rated reviews.
• One business summary row per business, from the same page as its first batch of reviews.

FAQ

Does it need a Trustpilot login? No. Every page is read as a logged-out visitor.

Is the reviewer's name in the output? No, never. Only the review content, rating, dates, verification flag and the company's reply.

What happens for a business Trustpilot doesn't have? No rows are pushed for it and no result events are charged for it; other businesses in the same run are unaffected.

Changelog

• 0.1: initial release - review rows with no reviewer identity, business summary row, monitor mode.

---

If this actor saved you time, a short review on its Store page genuinely helps other people find it. Found a bug or need a field that is missing? Open a ticket on the Issues tab.