Google Maps Reviews Scraper

Google Maps Reviews Scraper: every review for a place, no API key

Paste a Maps link, a place ID, a CID or just the business name, and get the reviews back as rows. Star rating, the full text, the exact date, who wrote it, whether the owner replied, and any photos attached. It keeps paging rather than stopping at the first screen.

Google itself is the limit, not the actor. A very large place hands out several thousand reviews and then stops issuing pages, so nobody can pull the complete history of a busy restaurant.

🔍 What Google Maps Reviews Scraper does

It takes whatever form of a place you happen to have and resolves it to the same place. A copied address-bar URL, a maps.app.goo.gl short link, a ChIJ… place ID, a numeric CID, or the plain name of the business. Then it reads the review list, paging until it has what you asked for or Google stops handing out pages.

You can point it at up to 50 places in one run and set a total row budget. That budget is split evenly between the places, so a chain audit gives you a comparable sample from every branch rather than all of it from the busiest one.

Reviews only. Opening hours, phone number, address, category and the overall star average are not part of this actor's output. The Google Maps Scraper linked below covers place details.

📥 What you give it

{
  "placeUrls": ["https://maps.app.goo.gl/abc123"],
  "maxReviews": 300,
  "maxReviewsPerPlace": 100,
  "sort": "newest",
  "language": "en"
}

reviewsSince only understands two formats: a number of days like 30 days or 30d, or a real date like 2026-01-15. Anything else, including 2 weeks and 1 month, is ignored without complaint, and the run then pulls and bills the full history up to your caps. Use days or a date.

reviewsSince stops paging early only when sort is newest. On any other order the cutoff still filters rows, but the run reads further to find them.

📤 What you get back

A real row from a recent run, trimmed where the URLs run long:

{
  "ok": true,
  "charged": true,
  "recordType": "review",
  "placeName": "Starbucks Reserve Roastery",
  "placeUrl": "https://www.google.com/maps?cid=7899526995152106350",
  "placeId": "ChIJsU30zM1qkFQRbnOm1_LBoG0",
  "cid": "7899526995152106350",
  "reviewId": "Ci9DQUlRQUNvZENodHljRjlvT21GRFdtSnpUV2xQYjFvM1kxbFRZMHhWVlRSMFRWRRAB",
  "rating": 5,
  "text": "It's gone ):",
  "originalText": null,
  "language": "en",
  "publishedAt": "2025-09-26T17:40:32.007Z",
  "relativeDate": "11 months ago",
  "reviewerName": "Daniel J",
  "reviewerUrl": "https://www.google.com/maps/contrib/103952951038275342964/reviews?hl=en-US",
  "reviewerReviewsCount": 142,
  "reviewerPhotosCount": 625,
  "isLocalGuide": true,
  "ownerReply": "Hi there! We're so glad you had a wonderful experience. Thanks for sharing it with us!",
  "ownerReplyRelativeDate": "11 months ago",
  "reviewPhotosCount": 1,
  "reviewPhotoUrls": ["https://lh3.googleusercontent.com/grass-cs/..."],
  "scrapedAt": "2026-09-21T01:45:28.154Z"
}

🧾 Reading the output

Three kinds of row can land in your dataset.

Filter on _sample and _diagnostic being absent, not on recordType. The free sample row also carries recordType: "review", so a filter on that alone keeps it.

The errorCode on a diagnostic row tells you which target had the problem:

One bad target never stops the others, and a diagnostic row never fails the run.

▶️ How to run it

1. Open Google Maps Reviews Scraper and click Try for free. 2. Paste one or more links into Place links or IDs, or type names into Business names. 3. Set Maximum reviews. Start around 20 to see the output shape. 4. Pick a Review order and a Language if the defaults do not suit you, then click Start. 5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$0.27 per 1,000 reviews. Flat on every Apify plan, no volume tiers.

You pay per review row delivered. Reviews dropped by reviewsSince or onlyWithText, duplicates, sample rows and diagnostic rows are all free, and a place with no reviews costs you nothing.

💡 What people use it for

• Watching what changed in a place's reviews since last month, on a schedule, using reviewsSince.
• Auditing every branch of a chain on the same terms, with a per-place cap so one busy site does not

eat the budget.

• Pulling the text of everything below three stars to find the complaint that keeps repeating.
• Checking which reviews the owner replied to, and how fast, across a set of competitors' locations.

🚧 What it does not do

• Reviews only. No opening hours, phone number, address, category, star average or total review

count.

• Not the full history. Google stops issuing pages after a few thousand on large places, and the

hard ceiling here is 5,000 per run regardless.

• Sorting is Google's, applied before paging. Asking for 20 sorted "highest" gives you the 20

highest Google serves first, not a true sort of the whole history.

• Star-only ratings have no text, so text is null on those unless you switch on **Skip

star-only ratings**.

• Translation is Google's, and its quality is not something this actor controls.
• Photo links are Google CDN URLs. Stable for a long time, but not archival.
• A name matching several places resolves to Google's top match, and a name with no city in it

can land on the wrong branch. For a specific place, use its link or place ID.

• Rows are a snapshot. A review can be edited or deleted later, and scrapedAt records when it

was read.

• The row budget splits evenly between your places. A place with fewer reviews than its share

returns fewer rows, and the leftover is not handed to the others.

🧭 Which Google scraper do you need?

❓ Questions people ask

Do I need a Google API key? No. Nothing to apply for, no quota to manage.

Can I monitor a place over time? Yes. Schedule it with reviewsSince set to something like 7 days and sort on newest, and each run picks up only what is new. reviewId makes deduping across runs straightforward.

Why did I get fewer reviews than I asked for? Either the place does not have that many, or Google stopped issuing pages. You are charged for what arrived.

Why is my date cutoff being ignored? Almost always the format. reviewsSince takes 30 days, 30d or a date like 2026-01-15. Wordings like 2 weeks are dropped silently.

Can I audit every branch of a chain? Feed the list of place IDs, set maxReviewsPerPlace, and you get a comparable sample from each branch in one run.

Is scraping Google reviews legal? These are public reviews on public place pages. They contain personal data all the same, which GDPR and similar laws cover, so have a reason for collecting it. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the place link and the run ID. The errorCode on the diagnostic row usually names the problem on its own.