Google Maps Reviews Scraper

Yes, sorted by stars, newest first within a star. Google's own rating sort stops after a sample: for one garage with 1,085 reviews it gave 145, only 76 of its 1,014 five-star reviews. Highest rating is quick. Lowest rating can take a few minutes on places with thousands of reviews, because their 1-star reviews are spread across all of them. You pay only for the reviews you get.

It finds your words as each reviewer wrote them, so parking finds reviews written in English and poulet finds reviews written in French. Google's translations aren't searched: on a Paris restaurant, chicken found 108 reviews written in English, and Thorough search found 169, adding the French reviews Google translates as "chicken". Turn on Thorough search for hotels and tourist spots, where many reviews are in other languages. Type words with their accents (délicieux): they're also found without them.

Yes. In Stars, pick 1 and 2 for the negative reviews, or 4 and 5 for the good ones. To find complaints about something, add words to Reviews mentioning, such as parking, wait or rude. You can also leave out reviews that have no text, or keep only reviews with photos. Reviews you filter out are free.

Yes. Turn off Reviewer names and profiles and the rows have no reviewer name, contributor ID, profile link or picture, for example for GDPR work. The rating, text, dates and the reviewer's review count and Local Guide badge stay.

Yes. Google translates them into the language you choose, English by default. When a review was translated, you also get the text as the reviewer wrote it, and every review comes with the language it was written in.

No. You get Google reviews only: the review feed Google serves to visitors who are not logged in doesn't include reviews from partner sites.

The run's status message says why, and the log names each input that failed. If a mistake in the input stops the run before anything is scraped, the run ends without results and its status message says what to change. Either way the Actor sends us a short error report, so we can fix the cause even if you never open an issue: the Actor's build, the reason, the counts from the end-of-run summary, whether your Apify plan is free or paid and, for an unexpected error, where in our code it happened. Web addresses and @usernames are blanked out first. The report never includes your input, your account, the pages you scraped or your results. Every run, failed or not, also sends one usage line as it ends, so we can see which options people use, what runs cost us and how well the data is filled: how many of each charged event it used (for example 120 full details) and the price your plan paid for them; the run's platform cost by item and its resources (time, memory, proxy traffic); whether it stopped at your maximum cost or maximum items; how it was started (Console, API, schedule, saved task, and for API runs the kind of tool, such as Make, Zapier or the Apify client, never the tool's full identity); our scraper's own retry and timing counts; and for each output field, how many results had it filled (counts only, never the values). That never includes your input, your account, your IP address, the pages you scraped or your results either. If you need help with a run, open an issue on the Issues tab and attach the run, or email support@kekliktech.com with the run's link; the run's log ends with both.

$0.45 per 1,000 reviews on Apify's free plan, down to $0.22 on the Business plan. Use the calculator above for your numbers.

Yes. The scraper runs in your Apify account and Apify bills you per result. A free Apify account is enough to try it.

Yes. We can run it on a schedule, clean up the results and send them to your sheet, CRM or database. Ask for a quote and we reply within one business day.