Nobody talks about this, but a Google Maps listing already has a reply voice
A reputation manager can pull every star a restaurant has earned. What they cannot pull, without reading the owner's last few replies out loud, is how that owner actually talks to a guest.
The reviews look like a queue. One star about a cold dumpling. Four stars about the wait. The owner answered three of them last month in short, specific sentences and ignored the rest. The next draft the agency writes still starts with "Thank you for your feedback."
The voice is already public
Multi-location groups and local agencies treat Google Maps as a nightly export. Place IDs in, a spreadsheet of text and stars out, a person who copies the angry ones into a doc. The doc has a template. The template does not sound like the person who runs the room.
That fails for a boring reason. The style guide is not in the brand PDF. It is the last handful of public owner responses on the listing itself. Short. A little blunt. They name the dish. They do not say "we value your patronage." A generic reply is obvious next to those, and guests can see both.
Nobody talks about this, but a Google Maps listing already has a reply voice. The reviews arrive newest first, with an exact timestamp, so a nightly run can stop when it hits last week's date instead of re-reading the whole history. The themes people argue about — wait, portion, parking — show up as quotes you can paste into a client deck, not a one-line "guests mention service."
The workaround most teams still use is the full dump. Every review, every night, then a human who writes the same three sentences under a one-star and a four-star. By Friday the sheet is current and the voice is gone. The owner who answered "sorry about the soup, come back and I'll make it again" now has a reply that could belong to any chain in the city.
Match the last replies, keep the quote
Once you treat those public responses as the sample, the job gets narrower. Take the places you already have. Walk reviews from newest to oldest and stop at a date. Group what people keep saying, and keep a sentence from the review next to each theme. For the unanswered low stars, draft a reply that could sit under the ones the owner already posted.
That is the Google Maps Reviews & AI Insights Scraper API. You give it Maps URLs or Place IDs you already store. You get one row per place: contact fields, the star histogram, and the reviews. Turn the add-ons on and the same row includes themes with evidence quotes, plus draft replies written like that listing's recent owner responses.
Three beats, then you stop:
- Point it at the Place IDs or Maps URLs you already sync.
- It returns newest reviews first and can stop at a date you set.
- You download themes you can show, and drafts you can edit before anyone posts them.
I built it because I was tired of watching teams re-download a thousand old reviews to answer the three that came in overnight.
Who this is for, and who should walk away
If you run reputation for a restaurant group, a hotel cluster, or a local agency with a fixed venue list, this is for you. If you report review velocity and owner-reply coverage every Monday, this is for you.
If you need to discover places by keyword or city, this is not that. You bring the listings. If you need a reply that posts itself to Google, this is not that either. The drafts are text. A person still sends them.
Themes can miss a joke or lump two complaints together. Read the quote before you put it in a slide. A listing with no owner replies yet has no voice to copy, so the drafts stay plain until someone has answered in public. Input, pricing, and the rest of the caveats live on the Apify Store README for Google Maps Reviews & AI Insights Scraper.
Menus on the same pins are a different record. If the job is dish prices hiding in photos, I wrote separately about reading Google Maps menus from photos. If the job is whether the gallery is even usable, that is labeling Google Maps listing photos. I also benchmarked the Google Maps Reviews & AI Insights Scraper API against five other Google Maps review APIs on the same Place IDs — see the comparison.
A template reply is not the owner's voice
The old cost is not the export. It is the guest who can tell a person did not write the answer, sitting under five answers a person did write.
If the listing is public and the owner has already replied, match that voice.
The other posts on rainminer sit next to this one when the useful record is already on the public page.