Google Maps Reviews Scraper avatar

Google Maps Reviews Scraper

Pricing

from $0.20 / 1,000 review scrapeds

Go to Apify Store
Google Maps Reviews Scraper

Google Maps Reviews Scraper

Scrape Google Maps reviews by URL, data ID, Place ID, CID, or business name. Get rating, text, date, owner response, photos, and privacy-safe reviewer hashes. MCP/API-ready.

Pricing

from $0.20 / 1,000 review scrapeds

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

1

Bookmarked

39

Total users

1

Monthly active users

5 days ago

Last modified

Features

Limited permissions

Share

What is Google Maps Reviews Scraper — $0.30 per 1K Reviews?

Google Maps Reviews Scraper is an Apify Actor for extracting reviews from a single Google Maps place target at a time. It accepts a Google Maps place URL, Place ID, Google Maps data ID or CID, or a business name plus location. Each dataset record represents one review and can include the rating, review text, publish date, owner response, photos, place metadata, and a privacy-safe reviewer hash. The Actor is available through Apify API and through Apify MCP.

What's new

  • Faster. Up to 4 places are read at the same time, with bigger pages and no idle waiting. A 1,000-review run now takes a fraction of the old time.
  • Filters that really scan. Keep only reviews in a date window, a star range, with text, or with an owner reply. Reviews that do not match are never billed.
  • Per-place cap. maxReviewsPerPlace stops each place at its own limit so one big place cannot eat the whole run.
  • New fields. isEdited, editedAtText, hasOwnerResponse, and optional textTranslated / translatedTo.
  • Place summary. includePlaceSummary saves name, address, rating, total review count and stop reason for each place (not billed).
  • Honest results. OUTPUT says why a run stopped, whether it was cut short (truncated), and gives a one-line agentSummary for AI agents.

Best fit and connected workflows

This Actor fits workflows that need review data for a specific place, such as reputation monitoring, sentiment analysis, and competitive review research. It is a focused review-extraction workflow, which makes it a clean fit when you already have a place URL, Place ID, CID, data ID, or a precise business name with a location hint.

When your workflow starts with business discovery or contact enrichment, a separate step can handle that before or after review scraping. For business contact data, use khadinakbar/google-maps-leads-scraper. This Actor stays centered on review records, review text, owner replies, and the place-level context around those reviews.

Practical scenario

Maya manages a neighborhood cafe and wants to review the newest customer feedback from Google Maps. She starts with the cafe's place URL, sets maxReviews to a moderate number, and chooses reviewsSort: "newest". The returned records include rating, text, publishedAtText, ownerResponse, reviewUrl, and sentimentHint. Maya uses sentimentHint to separate the newest positive and negative feedback, opens the reviewUrl for one recent review, and then prepares a response plan for the owner.

Input fields

FieldTypePurpose
startUrlsarrayGoogle Maps URLs for a single place, including place URLs, search URLs, CID URLs, and shortened Maps links.
placeIdsarrayGoogle Place IDs resolved to a place page and its reviews.
dataIdsarrayExact Google Maps internal 0x...:0x... data IDs. Decimal CIDs use a Maps ?cid= URL in startUrls.
searchQuerystringBusiness name used with location to resolve one place.
locationstringCity, region, or country used to disambiguate searchQuery.
maxReviewsintegerMaximum reviews saved across all place targets in the run.
maxReviewsPerPlaceintegerMaximum reviews saved per place. 0 = no per-place limit.
reviewsNewerThan / reviewsOlderThanstringDate window. Accepts YYYY-MM-DD or phrases like 30 days.
minStars / maxStarsintegerKeep only reviews inside this star range (1-5).
onlyWithTextbooleanSkip star-only reviews with no text.
onlyWithOwnerReplybooleanKeep only reviews the owner answered.
translateTostringLanguage code. Adds textTranslated when Google offers a translation.
includePlaceSummarybooleanSaves one summary per place under the PLACES key. Not billed.
reviewsSortstringReview order: newest, mostRelevant, highestRanking, or lowestRanking.
reviewSearchQuerystringOptional keyword filter inside reviews, such as parking.
languagestringGoogle Maps UI language and review translation context.
countryCodestringTwo-letter Google region hint, such as US or GB.
includePersonalDatabooleanReturns reviewer name, profile URL, and photo URL when enabled.
proxyConfigurationobjectProxy settings for Google Maps requests.

Focused JSON input example

{
"startUrls": [
{
"url": "https://www.google.com/maps/place/?q=place_id:ChIJLU7jZClu5kcR4PcOOO_ouTY"
}
],
"maxReviews": 50,
"reviewsSort": "newest",
"reviewSearchQuery": "parking",
"language": "en",
"countryCode": "US",
"includePersonalData": false
}

Filter example: last 30 days, 1-2 stars, with text

{
"dataIds": ["0x89c259ab3c1ef289:0x3b67a41175949f55"],
"maxReviews": 200,
"reviewsSort": "newest",
"reviewsNewerThan": "30 days",
"maxStars": 2,
"onlyWithText": true,
"includePlaceSummary": true
}

Sorting newest with a date window, or lowestRanking with maxStars, lets the run stop as soon as the window ends, so you pay only for matching reviews and wait less.

Output fields

Each dataset item is one review.

FieldTypePurpose
reviewIdstringStable Google review identifier.
placeNamestringGoogle Maps business name.
placeUrlstringCanonical Google Maps place URL.
placeDataIdstring or nullGoogle Maps internal data ID.
placeAddressstring or nullPostal address shown on the place panel.
placeRatingnumber or nullPlace-level average rating.
placeReviewCountinteger or nullTotal review count reported by Google.
reviewerNamestring or nullReviewer display name when personal data is enabled.
reviewerUrlstring or nullReviewer profile URL when personal data is enabled.
reviewerPhotoUrlstring or nullReviewer profile photo URL when personal data is enabled.
reviewerHashstring or nullStable privacy-safe reviewer hash when source identity is available; otherwise null.
reviewerReviewCountinteger or nullLifetime review count if Google reports it.
ratinginteger or nullReview rating from 1 to 5.
textstring or nullReview body text.
languagestring or nullDetected review language code.
publishedAtTextstring or nullRelative date label as Google renders it.
publishedAtstring or nullApproximate ISO-8601 timestamp derived from the relative date.
ownerResponsestring or nullOwner reply text if present.
ownerResponseAtstring or nullApproximate timestamp for the owner reply.
likesCountinteger or nullNumber of likes if surfaced by Google.
photosarrayPhoto URLs attached to the review.
sentimentHintstringRating-based bucket: positive, neutral, or negative.
reviewUrlstring or nullPermalink to the review on Google Maps.
scrapedAtstringISO-8601 UTC timestamp when the record was scraped.
extractionSourcestring or nullInternal extraction route, currently boq.

Illustrative output record

{
"reviewId": "ChZDSUhNMG9nS0VJQ0FnSURwLVlPajJBRRAB",
"placeName": "Joe's Pizza",
"placeUrl": "https://www.google.com/maps/place/...",
"placeDataId": "0x89c259a9b3117469:0xd134e199a405a163",
"placeAddress": "7 Carmine St, New York, NY 10014",
"placeRating": 4.6,
"placeReviewCount": 12847,
"reviewerHash": "b7c2f4e0c9d1...",
"rating": 5,
"text": "The classic slice was excellent.",
"language": "en",
"publishedAtText": "a month ago",
"publishedAt": "2026-03-25T13:24:00.000Z",
"ownerResponse": "Thanks for visiting!",
"ownerResponseAt": "2026-03-26T10:11:00.000Z",
"likesCount": 3,
"photos": [
"https://lh3.googleusercontent.com/..."
],
"sentimentHint": "positive",
"reviewUrl": "https://www.google.com/maps/...review...",
"scrapedAt": "2026-03-27T08:00:00.000Z",
"extractionSource": "boq"
}

How it works (speed)

Places are read up to 4 at a time. Requests try the fast route first and switch to a stronger route on a block. The OUTPUT summary shows route and routeSwitches.

How it works

The Actor resolves each input into a Google Maps place target and then extracts reviews through browser-free Google Maps review RPC paths. The implementation uses Chrome TLS impersonation, BOQ fallback, data ID resolution, soft validation, and safe dataset pushes. The dataset stores one record per review, and the run summary is written to the OUTPUT key.

Pricing

This Actor uses Pay per event plus Apify platform usage. The primary event is Review scraped, and there is also an Actor Start event. Review scraping is billed per review scraped, while the Apify platform usage covers the run itself and the resources you allocate for execution.

ReviewsReview fees at $0.0003Plus start event
100$0.03$0.00005
1,000$0.30$0.00005
5,000$1.50$0.00005

Filtered-out reviews are never billed. Platform usage is shown on the Pricing tab. For planning, imagine scraping one hundred reviews. That execution produces one hundred review events, plus the start event that applies when the Actor begins. Open the live Pricing tab on Apify for the current event breakdown and the exact pricing shown for this Actor.

Use with AI agents (MCP)

This Actor is available through Apify MCP as an Apify Actor tool for review extraction. The exact Actor identity is khadinakbar/google-maps-reviews-scraper.

Tool description: provide a Google Maps place target and receive structured review records with rating, text, owner response, photos, review metadata, and privacy-safe reviewer hashing. It is built for one place at a time, which makes it useful when an agent needs review data for a specific business and wants one record per review.

Extract reviews for this Google Maps place URL. Return the newesta bounded number of reviews, include the review text, rating, owner response, review URL, and a privacy-safe reviewer hash. Keep reviewer personal data disabled unless I explicitly request it.

Output interpretation:

  • sentimentHint is a rating-derived bucket, not a model-generated sentiment score.
  • publishedAtText is Google's relative date label.
  • publishedAt is an approximate ISO-8601 timestamp derived from that label.
  • reviewerHash remains available when reviewer personal data is hidden.
  • reviewUrl points to the specific review on Google Maps.
  • extractionSource shows the internal review path used for the record.

Provenance and scope:

  • Each record comes from one Google Maps place.
  • The Actor is designed for review extraction, not business contact data.
  • For business lead or contact enrichment, route that step to khadinakbar/google-maps-leads-scraper.

Pagination and cost guidance:

  • maxReviews controls how many reviews are requested per place.
  • Billing follows the number of scraped review events.
  • Use a lower maxReviews for testing and increase it only when you need a deeper review sample.

Apify API example

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({
token: process.env.APIFY_TOKEN,
});
const run = await client.actor('khadinakbar/google-maps-reviews-scraper').call({
startUrls: [
{
url: 'https://www.google.com/maps/place/?q=place_id:ChIJLU7jZClu5kcR4PcOOO_ouTY',
},
],
maxReviews: 25,
reviewsSort: 'newest',
includePersonalData: false,
});
const dataset = await client.dataset(run.defaultDatasetId).listItems({ clean: true });
console.log(dataset.items);

Best results and outcome guidance

For review monitoring, start with reviewsSort: "newest" so the returned sample reflects the latest feedback first. Use a direct Google Maps place URL, Place ID, or data ID when you already know the target place. Use reviewSearchQuery when you want reviews mentioning a specific topic such as a service issue or product feature. Keep includePersonalData disabled when you only need a privacy-safe review stream, and enable it only when your use case and legal basis require reviewer profile fields.

Continue the workflow

Design note

I found that reviewId is always returned regardless of the includePersonalData setting, while reviewer name, profile URL, and profile photo URL are nulled when personal data is disabled.

FAQ

Can I start from a Google Maps URL, a Place ID, or a CID?
Yes. The Actor accepts Google Maps URLs, Place IDs, and Google Maps data IDs or CIDs. It also supports a business name plus location.

When should I use searchQuery instead of startUrls?
Use searchQuery when you know the business name and want the Actor to resolve the place with a location hint. Use startUrls when you already have the exact Maps URL.

How do I focus on a specific review topic?
Set reviewSearchQuery to a keyword such as parking or refund to narrow extraction toward matching reviews.

What if I need reviewer personal fields?
Set includePersonalData to true when your use case has a legitimate basis for those fields. The dataset will then include reviewer name, profile URL, and profile photo URL when available.

Which output field identifies the extraction route?
Use extractionSource, which is boq.

Can an AI agent use this Actor?
Yes. Pass one place and a small maxReviews; read agentSummary and truncated in OUTPUT to know whether the result is complete.

Will I pay for reviews my filters drop?
No. Only saved reviews are billed.

Does it list every reviewer's other reviews or count all reviews of a place?
Not yet. Total review count per place is in the optional place summary when Google shows it.

Responsible use

Use this Actor only for publicly available Google Maps reviews and for lawful purposes. Review the applicable Google Maps terms and your privacy obligations before using reviewer data. When working with personal data, keep the data handling scope aligned with your documented purpose and legal basis.

Source and limits

The Actor reads Google Maps' own public endpoints only. It resolves each target itself: data IDs and place URLs are read directly, Place IDs through the Google Maps place page (accepted only when the page names exactly one place), CID links through the CID, share links (maps.app.goo.gl and similar) by following their redirects, and a name plus location (or a Maps search URL) through Google Maps search, taking the top-ranked place. Reviews come from Google's review endpoints. Proxy and platform usage follow the current pricing settings; there are no other per-run costs.

A Place ID or data ID is the best target input. Name searches take Google's first result and may be ambiguous; use a precise business name and location. If no target can be resolved or read, the run fails with no review charges; a search with no matching place is reported as not found. A review keyword (reviewSearchQuery) is matched against review text on the Actor's side across a bounded window of up to 50 review pages in the chosen order; a keyword with no match in that window returns no reviews. Up to ten distinct targets are accepted. maxReviews is one shared saved-review cap for the run. The Actor does not promise complete Google history, exact relative-label timestamps, or an official Google ranking.

OUTPUT and RUN_SUMMARY report actual saved rows, accepted named charges, Google request counts and truthful COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT or UPSTREAM_FAILED outcomes. An unresolved write/charge checkpoint stops delivery and is never retried blindly. Missing or malformed source records do not qualify as genuine empty results. Reviewer names and profile/photo URLs remain absent unless includePersonalData is true.