Review Scraper – Google, Yelp, TripAdvisor & Trustpilot avatar

Review Scraper – Google, Yelp, TripAdvisor & Trustpilot

Pricing

from $4.00 / 1,000 keyword serp checkeds

Go to Apify Store
Review Scraper – Google, Yelp, TripAdvisor & Trustpilot

Review Scraper – Google, Yelp, TripAdvisor & Trustpilot

Scrapes customer reviews from Google Maps, Yelp, TripAdvisor, Trustpilot, and Facebook for any business URL. Returns reviews with rating, text, reviewer, date, and auto-calculated sentiment. $0.002 per review.

Pricing

from $4.00 / 1,000 keyword serp checkeds

Rating

0.0

(0)

Developer

joseph fadero

joseph fadero

Maintained by Community

Actor stats

0

Bookmarked

12

Total users

2

Monthly active users

18 days ago

Last modified

Share

Multi-Platform Review Scraper – Google, Yelp, TripAdvisor, Trustpilot, Facebook & Bol.com

Monitor all your business reviews in one place. Works with n8n, Make, and Zapier. $0.002 per review — 500 reviews costs $1.10.

Platforms Supported

  • Google Maps — via compass/google-maps-reviews-scraper
  • Yelp — via tri_angle/yelp-review-scraper
  • TripAdvisor — via maxcopell/tripadvisor-reviews
  • Trustpilot — via memo23/trustpilot-scraper-ppe
  • Facebook — via apify/facebook-reviews-scraper
  • Bol.com — direct scraping (JSON-LD + Bazaarvoice parsing); see known limitation below

This actor had never actually been run live before this addendum. Live verification during the Bol.com build caught real pre-existing bugs across every platform: every sub-actor call was missing its auth token, and two sub-actor slugs (nikita.rol/trustpilot-reviews-scraper, tri_angle/yelp-reviews-scraper) no longer exist on the Apify Store. All fixed and live-verified — see git history / addendum notes for specifics.

Pricing

EventPrice
run-started$0.10 flat
review-scraped$0.002
review-negative surcharge (rating ≤ 2)+$0.001

Input

FieldRequiredDescription
businessesArray of business profile URLs (mix platforms freely) — required unless bolComConfig is set
bolComConfig{ productUrls?: string[], searchKeyword?: string, maxReviewsPerProduct?: number } — Bol.com's bulk/search shape doesn't fit the flat businesses list, so it's its own field
maxReviewsPerBusinessMax reviews per URL — default 50
dateFromISO date string — only reviews on/after this date
minRatingMinimum star rating filter — default 1
maxRatingMaximum star rating filter — default 5, set to 2 for negatives only
includeSentimentAuto-classify positive/neutral/negative — default true
sortBynewest / rating_asc / rating_desc / most_relevant

Output Fields

  • businessUrl, platform, businessName
  • platformReviewId, reviewerName, reviewerProfileUrl
  • rating, title, body, publishedAt
  • sentiment, isNegative
  • ownerResponse, ownerRespondedAt
  • pros[], cons[], language, priceAtReview — Bol.com only, []/null for every other platform
  • scrapedAt, chargedEvent

Bol.com — known limitation (read before relying on this source)

Bol.com is protected by Akamai's TLS-fingerprint-level bot detection (JA3/JA4) — a layer below the browser that Crawlee's fingerprint spoofing cannot touch. Every request currently receives an immediate 403 with no challenge page. Two real proxy configurations were tried live on the deployed platform (this Apify plan disables local proxy testing entirely): an explicit RESIDENTIAL group (0 available sessions on this account, still 403) and automatic/default selection (still 403). This was confirmed first on the sibling actor Competitor Review Intelligence (Actor 10), which shares this account's proxy access, then reproduced live here.

What this means in practice: Bol.com scraping is built and wired in end-to-end (bulk product URLs, keyword search, JSON-LD + Bazaarvoice review parsing, NL/FR language detection, price extraction) and runs cleanly with zero errors — but currently returns 0 reviews, because Bol.com's page HTML is never actually reachable on this account. This is real, correct extraction logic (built from Bol.com's confirmed real schema.org JSON-LD and Bazaarvoice CSS conventions), not a fake or partial feature — it will work the moment page access is available (a RESIDENTIAL proxy allocation, the correct PROXY_UNBLOCKER group name, or Bol.com's official partner API) without further code changes.

Existing Google, Yelp, TripAdvisor, Trustpilot, and Facebook scraping is unaffected by this.

Use Cases

  • Reputation monitoring for agencies managing multiple client locations
  • Local SEO reporting (weekly review digest)
  • Sentiment analysis pipelines
  • Negative review alert workflows (pipe to Slack/email via n8n)
  • Competitive benchmarking across platforms