Google Maps Scraper
Pricing
$1.50 / 1,000 places
Google Maps Scraper
Scrape Google Maps places and reviews from publicly available pages: search results with name, rating, review count, address, and coordinates, plus full place details with guest-visible reviews.
Pricing
$1.50 / 1,000 places
Rating
0.0
(0)
Developer
Cravl
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
16 hours ago
Last modified
Categories
Share
Google Maps Scraper
Scrape Google Maps places and reviews from publicly available pages.
Two modes
- Search (
/maps/search/QUERY): scrolls the results feed and emits every place card: name, rating, review count, category, address, coordinates, place ID, URL (budget:scrolls, default 20; Google's own cap is ~120 results per search) - Place detail (
/maps/place/...): full detail (rating, review count, category, price level, address, phone, website, plus code, opening hours, coordinates) plus guest-visible reviews (reviewer name, profile URL, Local Guide level, rating, date, text, owner response) and photo URLs
Input
| Field | Type | Description |
|---|---|---|
directUrls | array | Search URLs or place URLs |
scrolls | integer | Search feed scroll rounds (1–120, default 20) |
reviews | string/number | Review target per place: a number, or all to keep scrolling until Google stops serving |
proxyConfiguration | object | Apify proxy settings |
Output
- Search records:
query,count,places[](name, rating, reviewCount, category, address, coordinates, placeId, url) - Place records:
title,rating,reviewCountText,category,address,phone,website,plusCode,hours,coordinates,placeId,reviews[],photos[],error
Use cases
- Local SEO and competitor location analysis
- Review mining with owner responses
- Lead generation from place data
Migrating from other Apify Actors
Cravl Actors accept Apify-style inputs and emit familiar field names alongside Cravl-specific fields, so most pipelines migrate with minimal changes.
Input compatibility
startUrls(array of URLs, or objects with aurlkey) is accepted as an alias fordirectUrls.
Output compatibility
Search URLs emit one item per place (record place) with searchString and searchUrl context. Place URLs emit one item with added aliases: totalScore, reviewsCount (numeric when parseable), categoryName, inputUrl. Reviews remain nested.