Compare · Last benchmarked 2026-09-09

Google Maps Reviews API compared: 5 providers benchmarked

We build Apify Actors and may earn affiliate fees on Store links. Measured numbers on this page come from live API runs on 2026-09-09. Cells marked * are list-price references for vendors we did not benchmark this run.

TL;DR {#tldr}

  • Benchmarked this run: Apify, DataForSEO, Bright Data
  • Lowest normalized cost (measured): DataForSEO
  • Fastest 10-review median: DataForSEO
  • Deepest review field coverage: Apify
  • Incremental sync / date cutoff: only Apify exposed stop-at-date in this matrix

On this page

Cost {#cost}

Normalized $/1K reviews uses measured spend when available, otherwise list price as of 2026-09-09. Compare list prices to measured spend before committing — especially for async APIs where queue tier affects wall clock, not just unit cost.

Speed {#speed}

Medians from 1 timed runs on the primary fixture (10- and 100-review caps). Async vendors include queue wait.

Field coverage {#field-coverage}

Field coverage reflects our normalizer on real API responses for the primary fixture — not vendor marketing pages.

FieldApifyOutscraperDataForSEOSerpApiBright Data
reviewIdYesNoYesNoNo
textYesNoYesNoNo
starsYesNoYesNoNo
publishedAtYesNoYesNoNo
ownerReplyYesNoYesNoNo
reviewerNameYesNoYesNoNo
reviewerUrlYesNoYesNoNo
likesYesNoNoNoNo
photosYesNoNoNoNo
responseDateYesNoYesNoNo

Reviews overlap {#item-overlap}

On the primary fixture, Apify returned 77 reviews and DataForSEO returned 100. 77 review IDs appeared in both sets — 100% of Apify's IDs and 77% of DataForSEO's. The count gap usually reflects date-window or pagination defaults, not necessarily missing listings on one side. Every Apify review in our sample was also returned by DataForSEO; DataForSEO additionally surfaced 23 reviews outside Apify's set.

On the primary fixture, Apify returned 77 reviews and Bright Data returned 0. 0 review IDs appeared in both sets. The count gap usually reflects date-window or pagination defaults, not necessarily missing listings on one side.

Full comparison matrix {#full-comparison-matrix}

Full matrix below. Asterisks (*) = list price or not live-measured this run.

MetricApifyOutscraperDataForSEOSerpApiBright Data
List / measured $/1K reviews$0.290$3.000*$0.075$12.000*n/a
Median speed — 10 reviews11.3snot measured*5.1snot measured*n/a
Median speed — 100 reviews12.3snot measured*15.2snot measured*n/a
Reviews returned (primary fixture)77not measured*100not measured*0
Exact ISO review datesYesNoYesNoNo
Owner reply textYesNoYesNoNo
Date cutoff / incremental syncYesNoNoNoNo
Async task APINoNoYesNoNo

Head-to-head {#head-to-head}

The pairwise notes below spell out trade-offs vendor by vendor. Rows marked with * in the matrix were not live-measured this run.

Apify vs Outscraper {#rainminer-vs-outscraper}

Cost and speed winners on this pair: Apify on price, see matrix on 10-review latency. Compare field counts (10 vs 0) against your pipeline needs.

Apify vs DataForSEO {#rainminer-vs-dataforseo}

Cost and speed winners on this pair: DataForSEO on price, DataForSEO on 10-review latency. Compare field counts (10 vs 8) against your pipeline needs.

Apify vs SerpApi {#rainminer-vs-serpapi}

Cost and speed winners on this pair: Apify on price, see matrix on 10-review latency. Compare field counts (10 vs 0) against your pipeline needs.

Apify vs Bright Data {#rainminer-vs-brightdata}

Cost and speed winners on this pair: tie on price, see matrix on 10-review latency. Compare field counts (10 vs 0) against your pipeline needs.

Outscraper vs DataForSEO {#outscraper-vs-dataforseo}

Cost and speed winners on this pair: DataForSEO on price, see matrix on 10-review latency. Compare field counts (0 vs 8) against your pipeline needs.

Outscraper vs SerpApi {#outscraper-vs-serpapi}

Cost and speed winners on this pair: Outscraper on price, see matrix on 10-review latency. Compare field counts (0 vs 0) against your pipeline needs.

Outscraper vs Bright Data {#outscraper-vs-brightdata}

Cost and speed winners on this pair: tie on price, see matrix on 10-review latency. Compare field counts (0 vs 0) against your pipeline needs.

DataForSEO vs SerpApi {#dataforseo-vs-serpapi}

Cost and speed winners on this pair: DataForSEO on price, see matrix on 10-review latency. Compare field counts (8 vs 0) against your pipeline needs.

DataForSEO vs Bright Data {#dataforseo-vs-brightdata}

Cost and speed winners on this pair: tie on price, see matrix on 10-review latency. Compare field counts (8 vs 0) against your pipeline needs.

SerpApi vs Bright Data {#serpapi-vs-brightdata}

Cost and speed winners on this pair: tie on price, see matrix on 10-review latency. Compare field counts (0 vs 0) against your pipeline needs.

Methodology {#methodology}

Fixtures live in scripts/scraper-comparison/topics/google-maps-reviews-scraper/fixture.json. Params: 100 reviews on the primary place id.

Reproduce:

bun scripts/scraper-comparison/pipeline.ts google-maps-reviews-scraper

Raw artifacts: site/content/compare/google-maps-reviews-scraper/benchmark.json.

FAQ {#faq}

Which Google Maps reviews API is cheapest?

Among live-measured vendors on 2026-09-09, DataForSEO had the lowest normalized $/1K on the primary fixture. List prices for unmeasured vendors are in the matrix — verify before buying.

Which Apify Actor should I use for Google Maps reviews?

Use Google Maps Place Reviews Scraper on Apify when you already have Place IDs and need newest-first reviews with optional date cutoffs. For city/keyword discovery, Compass Google Maps Scraper is the mainstream Apify pick.

How fresh is this comparison?

Last benchmarked 2026-09-09. Re-run the benchmark pipeline to reproduce.

Try Apify

Run Google Maps scraper on Apify — or read the actor overview first.