How to Scrape a Google Maps Reviewer's Full Review History with One API

Most Google Maps reviews scrapers answer one question: what do people say about this place? The Google Maps Contributor Reviews API flips the axis and answers the harder one: what else has this person reviewed? This walkthrough turns a single contributor ID into that reviewer's entire public review history as structured JSON.

Why the reviewer axis, not the place axis?

A place-reviews scraper tells you how a business is rated. It cannot tell you whether the five-star burst came from real locals or from one account rating forty unrelated places in a week. Fake-review patterns live on the reviewer axis, and almost nothing exposes it, because Google's own Places API returns a small sample of reviews per place and has no per-reviewer endpoint at all.

What the scraper returns

One row per review, each carrying the rating, the review text, the date, likes, and the place reviewed with its GPS coordinates, plus the reviewer's Local Guide profile: level, points, and total contributions. Because every row carries coordinates, geography becomes computable. String them together and a "local favorites" list that spans four continents in a month tells you something.

Run the Google Maps reviews scraper

Grab the long number from a reviewer profile URL, pass it as the contributorId, and cap the spend with maxResultsPerContributor. Over REST it is a single POST:

POST /v2/acts/johnvc~google-maps-contributor-reviews-api/runs?token=YOUR_APIFY_TOKEN
{ "contributorId": "107022004965696773221", "maxResultsPerContributor": 50 }

Start from a saved task instead: Get a reviewer's full review history or Vet a reviewer for fake-review signals. Export the result as JSON, CSV, or Excel.

Ask an AI agent to vet a reviewer

Over the Model Context Protocol the Actor becomes a tool Claude, Claude Code, or Cursor can call, so "pull this contributor's history and flag anything odd" happens in one conversation with real rows behind it.

Where this scraper fits

Pair it with the Google Maps Reviewer Geo Profile API to automate the home-region estimate, and the Google Maps Places API to surface the businesses and contributor IDs to feed in.

FAQ

How is this different from a Google Maps place reviews scraper?

A place-reviews scraper collects every review left on one business. This scraper collects every review left by one person, across every place. For fraud and vetting work the reviewer axis is the one that matters.

What does the reviewer scraper cost?

A small start fee plus a per-review charge, and you only pay for reviews actually returned. maxResultsPerContributor caps the spend, so fifty reviews cost a few cents.

Can I run the scraper over MCP?

Yes. Connect the Apify MCP server and the Actor appears as a callable tool in Claude, Claude Code, and Cursor, which turns reviewer vetting into a prompt.

What will the scraper never return?

Anything Google does not show publicly: private or removed reviews, precise timestamps, and histories beyond the 200 most recent reviews per contributor.