Google Maps Reviews Scraper + Reputation Intelligence
Pricing
$0.60 / 1,000 review scrapeds
Scrapes Google Maps reviews from a business name, postcode, or place URL. Returns the complete review set with a coverage audit (claimed vs collected), sentiment, complaint themes, rating trajectory, response health, and a ranked reputation attention queue.
Type anything: a business name ("Domino's Pizza Belfast BT9 6AA"), a Google Maps place URL, a share.google short link, a place ID (ChIJ...), a feature ID (0x...:0x...), or a CID. The actor auto-detects the shape and resolves it to a place before scraping reviews. For bulk runs use the advanced 'places' or 'placeUrls' lists instead.
Maximum reviews to collect per place. Set to 0 for NO LIMIT — collect every review the place has, all the way back (pagination stops naturally when Google runs out). If a positive value is lower than a place's review count, coverage status is reported as 'capped' (an honest, explained cap, never a silent truncation). Collection is always newest-first, so a low cap drops the OLDEST reviews. No limit uses the most memory and runtime.
signals (default) = full reputation intelligence on top of every field. compat = exact compass/Google-Maps-Reviews-Scraper field set for drop-in migration and raw ingestion (no intelligence layer). minimal = reviewId, text, stars, publishedAt only.
auto (default) lets the actor classify the 'input' string by shape. search forces free-text search. places uses the 'places' bulk list. placeUrls uses the 'placeUrls' bulk list (compass parity).
Bulk list of business names / queries, optionally with lat-lng to disambiguate. Each item: a plain string query, or an object {"query": "...", "lat": 54.5, "lng": -5.9}.
[]Bulk list of Google Maps place URLs, place IDs, feature IDs, CIDs, or share.google links (compass parity).
[]google = Google-native reviews only (recommended, full coverage). all = include third-party aggregated reviews (Google reports reduced hotel coverage here; the actor flags this as 'degraded' when relevant).
Pagination always uses 'newest' internally to guarantee complete coverage (Google's date-range sort silently stops scraping). Date-range filtering is applied client-side after fetch. This field only affects the order of the emitted review rows.
Two-letter UI language for the Google Maps requests (e.g. en, fr, de).
Set a name to enable managed cross-run monitoring. The actor persists per-place state in a named key-value store and returns deltas (what changed since last run), a reputation timeline, and rank movement. Use the same name on a schedule for a daily reputation feed.
Diff this run against any prior Apify dataset (an old export or a competitor's run). Returns the same delta block as watchlist mode, on your first run. If both this and watchlistName are set, watchlistName wins.
Include reviewImageUrls on review records.
Include reviewer fields (name, reviewerId, reviewerNumberOfReviews, isLocalGuide, etc.).
If any place returns a coverage status other than 'complete', fail the whole run instead of finishing with a silent gap. For trust-critical pipelines.
Emit the full coverageProof ledger (pages fetched, retries, duplicates dropped, stop condition) on every place, even when coverage is complete.
Assemble a deterministic wins / risks / changes summary per place, ready to drop into a monthly client deck. Most meaningful with a watchlist or comparison dataset.
Post the daily briefing and any escalations to your Slack. Create a Slack connector once in Apify Console (Settings > MCP connectors) and select it here. We never see your Slack token.
Channel to post to, e.g. #reputation-alerts. Leave blank to use the connector's default channel.
Post locations at or above this escalation level: 1 = notice, 2 = urgent, 3 = critical. Higher = fewer, more serious alerts.
Post the run's one-message digest (headline + what changed + coverage) in addition to per-location escalations.
Archive each run's reputation intelligence to Notion. Create a Notion connector once in Apify Console (Settings > MCP connectors) and select it here. We never see your Notion token.
Target Notion database to write rows/pages into. If blank, the connector's default destination is used.
summary = one page per run (headline + what changed). per-location = one row per location (state, level, rating, top issue, coverage).