Review Scraping Benchmark: Bright Data, Oxylabs & Decodo

We tested 5 web scraping providers across 5 major review platforms and 6 providers across 2 app stores, for a total of 24,500 requests, and measured success rate, completion time, and metadata fields.

Review scraping benchmark

You can read benchmark methodology section for more details on the testing process.

Review scraping performance by domain

Google Play & Apple App Store scraping benchmark

We also benchmarked the Google Play Store and the Apple App Store scraping providers:

Only providers with a success rate above 90% were included in the final results. 

Domain coverage by provider

• ✓ = supported, returns HTML
• ✅ = supported, returns structured data

Available metadata fields for providers with structured JSON responses

Review scraping providers pricing

Review scraping providers free trial

Review scraping providers & benchmark results

Bright Data achieved the highest average success rate at 78% across all five review platforms and was the only provider to return structured JSON on four of them: Amazon, Google Maps, Trustpilot, and Yelp. It led on Amazon (96%) and Trustpilot (98%), delivering up to 39 metadata fields per review including verification status, reviewer location, and owner responses. Google Maps was its weakest domain at 39%, though most providers also failed on this domain due to JavaScript-rendered review content.

Bright Data also covers both app stores with dedicated Collect by URL scraper APIs for app pages and reviews, plus pre-built app and review datasets in its Dataset Marketplace. The app page APIs returned the most structured fields in the test, 36 on the Apple App Store and 26 on Google Play, at 100% success with completion times of 4s and 8s.

Oxylabs was the fastest provider in the benchmark at 5s average completion time, significantly ahead of the next closest at 13s. It posted high results on Trustpilot (98%) and Tripadvisor (91%), and matched the top tier on Amazon (92%) with 10 structured JSON fields. It did not return results on Google Maps or Yelp, where it lacked dedicated scraping configurations for these platforms.

It has no dedicated app store scraper either. Its Web Scraper API returned rendered HTML on the Apple App Store at 100% success in 12s.

Decodo scored 93% on Trustpilot and 76% on Tripadvisor using its unblocker proxy, demonstrating solid performance on server-rendered review pages. However, it recorded 0% on both Google Maps and Yelp, and only 11% on Amazon despite using a structured API endpoint. Its coverage is limited to two of the five tested platforms, making it the narrowest option in the benchmark for review scraping. Its Web Scraper API returned rendered HTML on the Apple App Store at 100% success in 11s.

SerpApi offers separate dedicated APIs for each major review platform rather than a single general-purpose scraping endpoint. It provides individual APIs for Google Maps Reviews, Yelp Reviews, Tripadvisor, each returning structured JSON with platform-specific fields such as topic mentions and sub-ratings on Google Maps, elite status and language breakdowns on Yelp, or location details on Tripadvisor by query.

The same approach extends to the app stores: separate Google Play endpoints for search, product pages, and the games, movies, and books sections, and Apple App Store endpoints for product pages, reviews, and search, with no pre-built datasets. In the benchmark, the Google Play Product and Apple App Store Product Page APIs returned parsed JSON with 16 and 29 metadata fields and posted the fastest completion times of any provider, under 1s on Google Play and 2s on the App Store.

Zyte was one of only two providers to return results on all five platforms, finishing with a 65% average success rate. It performed best on Tripadvisor (86%) and Yelp (57%), maintaining steady extraction across domains. Google Maps was a relative bright spot at 41%, one of the higher scores on a domain where most providers failed. All extraction was HTML-based with CSS selector parsing, so no structured metadata fields were returned beyond the five standard review fields. On the app stores, the same Zyte API with browserHtml returned rendered HTML at 100% success on Google Play (4s) and 99% on the Apple App Store (11s), again with no structured fields.

Nimble reached 92% on Amazon and 66% on Trustpilot, showing it can handle structured review pages effectively. However, performance dropped to 1% on Google Maps and 31% on Yelp, where JavaScript-heavy rendering limited its HTML-based extraction. Its 52% overall average reflects this uneven platform support, with completion times averaging 20s. On both app stores it used its general Extract API with stealth rendering and returned HTML at 100% success in 9s, with no dedicated endpoint and no parsed fields.

Review scraping benchmark methodology

We selected the top 5 review-focused domains from the Tranco top sites list: Amazon, Google Maps, Tripadvisor, Trustpilot, and Yelp. The five scraping providers were chosen from web data scraping companies with at least 100 employees. Each provider received the same set of 2,500 URLs (500 per platform), and we measured three metrics: success rate, completion time, and available metadata fields.

We ran two additional benchmarks on app stores with the same setup: 1,000 Apple App Store and 1,000 Google Play product page URLs, each sent to six providers (plus SerpApi), for 6,000 requests per store. The same three metrics were measured. On Google Play, only providers with a success rate above 90% appear in the results.

Providers and integration types

Providers were integrated using two approaches depending on the platform:

• JSON structured API: The provider returns parsed review data in JSON format with named fields (e.g., reviewer_name, rating, review_text). Bright Data and Oxylabs offered this for select platforms.
• HTML response: The provider returns rendered HTML, which we parsed using CSS selectors to extract review fields. Decodo, Nimble, and Zyte primarily used this approach.

Note: Decodo returned a JSON structured response for Amazon, but none of the responses contained successful review data. Its 11% success rate on Amazon came entirely from correct 404 detection, so no metadata fields are reported for that combination.

On the app stores, Bright Data and SerpApi returned structured JSON. Oxylabs, Decodo, Nimble, and Zyte returned rendered HTML, which we parsed with CSS selectors for title, rating, and developer.

Reviews scraping benchmark validation rules

Each response went through a three-step validation:

1. Submission: HTTP status code between 200-399 or 404 was required to pass.
2. Execution: For async providers, the scraping job had to complete without timeout or error.
3. Validation: The response had to contain usable review data.
   • For JSON responses: at least one review with a valid review_text (string) or rating (integer).
   • For HTML responses: at least one CSS selector match returning review content.

App store responses went through the same three steps. The data check required at least one of title, rating, developer, or number_of_reviews to be populated in JSON responses, or at least one CSS selector match in HTML responses.

Before running the full benchmark, we tested each provider with intentionally broken URLs, confirmed 404 pages, and live pages with zero reviews to map how each provider signals these edge cases. Providers returned different indicators depending on their implementation, including explicit error codes, HTTP 404 status, or empty response bodies.

When a provider correctly identified a page as not found or returned an appropriate response for a page with no reviews, the result was counted as valid. We then applied a cross-provider verification step: if a provider returned empty results on a URL where at least one other provider extracted review data, that empty result was reclassified as a failure. This separated extraction failures from pages that simply had no reviews to return.

Completion time

Completion time was measured end-to-end from the initial API request to receiving the final response. For async providers (e.g., Bright Data dataset API), this includes the polling/wait time until results were ready.

Available metadata fields

For providers returning structured JSON, we counted the total number of unique fields returned across all reviews. For HTML-based responses, the metadata count reflects the fixed set of CSS selector fields used for extraction (5 fields: reviewer_name, review_text, rating, review_date, review_title).

Reviews scraping benchmark dataset

The 2,500 test URLs were collected from publicly accessible review pages across the five Tranco top-ranked review platforms. URLs were cleaned to remove locale parameters, invalid formats, and duplicates before testing. The app store URL sets, 1,000 per store, were collected through keyword searches across categories such as games, social, productivity, finance, fitness, and photo & video, then deduplicated. They span a broad range of popularity tiers and app types.

Shared configuration

All providers received identical URLs from the same dataset and were tested under the same conditions:

• Sequential execution: one request at a time, no parallel requests
• Delay between requests: 2 seconds
• Rate limit handling: 30-second wait with up to 3 retries on HTTP 429
• Submission timeout: 300 seconds
• Execution timeout: 600 seconds
• Each URL was tested once per provider

Provider configurations

Bright Data

Bright Data used two integration methods depending on the domain. For Amazon, Google Maps, Trustpilot, and Yelp, we used the Dataset API, which returns structured JSON with parsed fields. For Tripadvisor, we used a web unblocker that returns rendered HTML, which we parsed locally with CSS selectors.

The Dataset API was polled via the /progress/{snapshot_id} endpoint at 1-second intervals until the status reached ‘ready’. Results were then fetched from the /snapshot/{snapshot_id} endpoint.

For the app stores, we used the Google Play Store and Apple App Store Collect by URL APIs, polled the same way.

Decodo

Decodo used the Universal Scraper API for Amazon. For Google Maps, Tripadvisor, Trustpilot, and Yelp, we used the web unblocker with the X-SU-Headless: HTML header for JavaScript rendering. All requests included a desktop User-Agent header.

App store pages went through the Web Scraper API v2 with headless browser rendering, returning HTML.

Oxylabs

Oxylabs used a dedicated source API for Amazon (source: amazon_reviews) with structured JSON output. For Google Maps, Tripadvisor, Trustpilot, and Yelp, we used the Web Unblocker proxy. Unblocker requests included a desktop User-Agent header.

App store pages went through the Web Scraper API universal source, returning rendered HTML.

Nimble

Nimble used the Web API for all domains with render: true for JavaScript rendering. All requests returned rendered HTML, which we parsed with CSS selectors. No domain-specific configuration was applied.

App store pages used the Extract API with render: true and the vx10 stealth browser driver.

Zyte

Zyte used the Extract API for all domains with browserHtml: true, which returns JavaScript-rendered HTML via a headless browser. No domain-specific configuration was applied.

App store pages used the same Zyte API with browserHtml: true.

SerpApi

SerpApi was tested on the app stores only. We used the Google Play Product API (engine: google_play_product) and the Apple App Store Product Page API (engine: apple_product), both of which take a product_id and return parsed JSON.

Don’t miss our benchmarks and data-driven insights. The button opens Google; selecting AIMultiple confirms that you wish to see AIMultiple more often in Google search results.

Add as preferred source

FAQs

Cite this research

Pick the format that matches where you're publishing. Pasting the link version into your CMS preserves the backlink.

@misc{sipi2026,
  author = {Şipi, Nazlı},
  title  = {{Review Scraping Benchmark: Bright Data, Oxylabs & Decodo}},
  year   = {2026},
  month  = sep,
  howpublished    = {\url{https://aimultiple.com/review-scraping}},
  note   = {AIMultiple. Retrieved September 29, 2026}
}

Changelog

4 updates

All4General3Methodology1

20262025

1. Apr 17

   Added SerpAPI's dedicated Google Maps, Yelp and Tripadvisor review APIs to the providers section.

2. Apr 17

   Added a provider selection criterion to the benchmark methodology: scraping companies with at least 100 employees.

3. Apr 15

   Replaced the Python scraping tutorials with a five-provider benchmark across five review platforms.

Nazlı Şipi

AI Researcher

Follow On

Nazlı is a data analyst at AIMultiple. She has prior experience in data analysis across various industries, where she worked on transforming complex datasets into actionable insights.

View Full Profile

Be the first to comment

Your email address will not be published. All fields are required. Comments are left in their original language.

Name

Email Address

Comment

0/450

Post Comment