
Google Maps Scraper
Pricing
Pay per event

Google Maps Scraper
Extract data from thousands of Google Maps locations and businesses. Get Google Maps data including reviews, reviewer details, images, contact info, opening hours, location, prices & more. Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools.
4.2 (90)
Pricing
Pay per event
1479
Total users
119K
Monthly users
17K
Runs succeeded
97%
Issues response
3.8 days
Last modified
18 hours ago
Unwanted fields despite disabled settings
Closed
I'm experiencing an issue with the Google Maps Scraper Actor where my exported data contains numerous fields I explicitly disabled in my input settings :
{"customGeolocation":"GEOJSON-DATA","includeWebResults":false,"language":"fr","maxCrawledPlacesPerSearch":20,"maxImages":0,"maximumLeadsEnrichmentRecords":0,"scrapeContacts":true,"scrapeDirectories":false,"scrapeImageAuthors":false,"scrapePlaceDetailPage":true,"scrapeReviewsPersonalData":false,"scrapeTableReservationProvider":false,"searchStringsArray":["apiculteur"],"skipClosedPlaces":true,"searchMatching":"all","placeMinimumStars":"","website":"allPlaces","maxQuestions":0,"maxReviews":0,"reviewsSort":"newest","reviewsFilterString":"","reviewsOrigin":"all","allPlacesNoSearchAction":""}
My output JSON still contains many unwanted fields such as:
- peopleAlsoSearch
- reviewsDistribution
- totalScore
- reviewsCount
- imagesCount
- imageCategories
And many other hotel/restaurant-related fields
This appears to be a known issue with the Actor where fields may still appear in the output structure even when the corresponding features are disabled. This potentially increases costs since the Actor's pricing is structured around specific events (base charge per place plus additional charges for details, reviews, images, etc.).
Could you please advise on:
- Whether this affects my billing despite disabling these features
- If there's a way to prevent these fields from appearing in the output
- Whether using the API would allow more precise control over which fields are included
Thank you.

Ondrej Klinovský (ondrejklinovsky)
Hey,
thanks for reaching out. Most of the fields that you listed cannot be disabled, they will always be present in the actor's output. The actor's input would be too complicated if we allowed enabling/disabling scraping of individual fields, so we decided to scrape everything that we get in Google's data. Some fields (such as reviewsDistribution
and some hotel/restaurant related data) are scraped only if we go to place's detail page - this can be disabled with "scrapePlaceDetailPage":true
.
Whether this affects my billing despite disabling these features
Only the input options marked with $
in actor's input (detail pages, contacts, leads enrichment, reviews, images) affect your billing. You don't pay an extra for the fields. Well, technically you pay for storage where this data is stored, but it's very cheap: $1.00 per 1,000 GB-hours.
If there's a way to prevent these fields from appearing in the output
They will always be present in the output. However, in Export options, you can select what fields you want to export (see attachment)
Whether using the API would allow more precise control over which fields are included
Same as in UI, you can specify what fields are exported using API (https://docs.apify.com/api/v2/dataset-items-get) with fields
or omit
parameters.
I hope this helps. Let me know if you have any more questions.