Google Maps places and reviews,
ready for your code and AI.
Search Google Maps for businesses by keyword and location, read any place in full with its hours and attributes, collect emails and social profiles from each business’s website, and fetch its public reviews, all as structured JSON for your product, research, monitoring, or AI workflow.
Trusted by developers shipping real products.
17,025 served today
Request
$ curl -X POST https://api.fetchlayer.dev/google-maps/reviews \ -H "Authorization: Bearer ss-your-key" \ -H "Content-Type: application/json" \ -d '{"placeIdOrUrl":"ChIJLU7jZClu5kcR4PcOOO6p3I0","pages":1,"maxReviews":20,"reviewsPerPage":20,"sortBy":"mostRelevant"}'
Response
{
"reviews": [{
"reviewer": "Jordan P.",
"rating": 2,
"text": "Waited 40 minutes past our...",
"relativeDate": "3 days ago",
"likes": 4
}]
} Built for feedback workflows
Fetch the public signal. Use it wherever your team works.
Public place reviews
Retrieve publicly visible Google Maps reviews for any business or place — no Google Business Profile login required.
Place ID or URL input
Pass a hex place ID, a ChIJ place ID, or a full Google Maps place URL — FetchLayer resolves it and fetches the review set.
Sort by relevance or rating
Choose newest, most relevant, highest rating, or lowest rating to surface the feedback that matters for your workflow.
Run on your schedule
Call the API from a cron job or automation to keep a feed of new reviews in your own database or alerting workflow.
AI-ready JSON
Pass structured review text, ratings, reviewer names, and dates to an LLM to group recurring praise, complaints, and service issues.
Any business, any location
Pull reviews for your own listings or public competitor locations — restaurants, retail, services, and more.
Analyze Google Maps reviews with AI—then export the results to CSV.
Prefer not to write code? Give FetchLayer Research Chat a business, ask what customers love or dislike, and turn the review set into a structured file you can use in a spreadsheet, report, or operations workflow.
- ✓Ask questions in plain English
- ✓Analyze themes, sentiment, and pain points
- ✓Download the structured results as CSV or JSON
No code or setup required · Uses your FetchLayer credits
Analyze Google Maps reviews for a business. Group recurring praise, complaints, and service issues, then export the review-level findings as CSV.
I grouped the reviews into five themes and flagged the service issue mentioned most often in the last 90 days. The full review-level analysis is ready to download.
google-maps-review-analysis.csv
142 reviews · 7 columns · ready to download
Solutions
Build the workflow around the feedback.
From raw feedback to action
One request is the start of the workflow.
Store the structured response, run it on a schedule, pass it to an LLM, or feed it into the system your team already uses. FetchLayer handles retrieval so you can focus on the outcome.
- 01
Resolve a place
Use a place ID, ChIJ ID, or a Google Maps place URL from the public listing.
- 02
Fetch the review pages you need
Set pages, maxReviews, reviewsPerPage, and sortBy to control how much feedback you retrieve.
- 03
Turn feedback into action
Store the JSON, trigger an alert, compare locations, or ask an AI agent to summarize the recurring themes.
MCP & agents
Your AI already knows
how to use this.
Use the Google Maps endpoint directly from your MCP-compatible agent. Ask it to retrieve public feedback, identify patterns, and turn the result into a useful brief without writing integration glue.
Pick your editor and we hand you the config with your key already in it — no JSON to hand-edit, no wrapper code.
Get your free API keyFree tier · no credit card · any MCP host
Fetch the most recent one- and two-star Google Maps reviews for this business and summarize the three most repeated complaints.
Fetched the public review pages and grouped the feedback. The leading issues are long wait times, order accuracy, and phone support being unreachable.
Works with every MCP-compatible tool
Use cases
What businesses build with Google Maps review data.
Same API, endless applications. Here is what teams ship with public place review data.
Multi-location intelligence
Compare review scores and recurring complaints across every branch or franchise location in one dataset.
AI agent context
Give Claude, Codex, or your MCP agent structured place reviews with ratings and dates attached.
Reputation monitoring
Poll new reviews on a schedule and alert the right team when a complaint cluster starts to grow.
Competitor benchmarking
Pull public reviews for nearby competitors to see how your rating and service issues compare.
Service feedback
Turn recurring praise, complaints, and service issues into a clean operations dataset or CSV export.
Market research
Study public reviews across a category or region to understand what customers value before entering a market.
Compare approaches
Spend time on the insight, not the collection layer.
| What you need | FetchLayer | Official API | Build it yourself |
|---|---|---|---|
| Public review access for any place | ✓ | Owner listings only | You build it |
| Bearer auth from one account | ✓ | Google Cloud setup | You manage it |
| Structured JSON | ✓ | ✓ | You parse it |
| Ready for AI and MCP workflows | ✓ | Your integration | Your integration |
FetchLayer provides access to publicly available data. It is not affiliated with, endorsed by, or sponsored by the platform.
Pricing
Start free. Scale when ready.
Pay per request with no commitment, or lock in a flat monthly rate with built-in savings.
Free plan — 30 requests
Verify responses, inspect the API, no credit card required.
Pay as you go
$1.99
per 1,000 requests
$0.00199 per request · credits never expire
How credits work — no multipliers
One credit = one API call, on every endpoint and platform. No matter how many results come back, you pay for the call, not the output size. Most scraping APIs charge multipliers of 5x, 25x, even 75x per call depending on the target — here it's always 1.
- No multipliers — 1 request = 1 credit
- No monthly commitment
- Credits never expire
- Same API & MCP access as subscribers
- ∞ req/min, ∞ API keys
∞
Expiry
Credits stay until you use them. No monthly reset, no pressure to hit a quota.
0
Commitments
No subscription, no contract, no minimums. Start, pause, or scale whenever.
100%
Access
Every endpoint and MCP included. Not a limited tier — same data as any subscriber.
API reference
Every parameter, documented.
All requests are POST with a JSON body and Bearer auth header.
POST /google-maps/place-search Search Google Maps for places by keyword and location or coordinates, with address, phone, website, rating, hours and business status.
query* string What to search for, e.g. "coffee shops" location string Area as text, e.g. "Denver, CO". Or pass coordinates { latitude, longitude, radiusMeters }. limit number Places to return, 1-100. Defaults to 20. POST /google-maps/place-details One place in full from its place ID or Maps URL: address, plus code, phone, website, rating, hours, description and attributes.
placeIdOrUrl* string ChIJ place ID, hex feature ID, Google Maps place URL, CID URL, or short link POST /google-maps/place-contacts Emails, phone numbers and social profiles read from businesses’ own websites, for up to 20 places or websites per call. Pass the website values from a search to skip the lookup.
places string[] Place IDs or Maps URLs. Required unless websites is given. websites string[] Business websites, e.g. from /place-search. At most 20 items combined. POST /google-maps/reviews Fetch public reviews for a place using a ChIJ place ID, hex place ID, Google Maps place URL, CID URL, or Maps short link.
placeIdOrUrl* string ChIJ place ID, hex place ID, Google Maps place URL, CID URL, or maps.app.goo.gl / goo.gl/maps short link pages* number Number of pages to scrape. Default 10. maxReviews* number Maximum number of reviews. Default 10000. reviewsPerPage* number Reviews per page (max 20). Default 20. A ceiling: Google limits signed-out access, so a page can return fewer. sortBy* string 'newest' | 'mostRelevant' | 'highestRating' | 'lowestRating'. Default mostRelevant. Fields marked * are required. Full API reference →
FAQ
Common questions.
Can I fetch reviews for a business I do not own?
Yes. FetchLayer retrieves publicly available Google Maps reviews by place ID or Maps URL. You use your FetchLayer API key, not a Google Business Profile login.
What place identifiers are supported?
A hex place ID, a ChIJ place ID, or a full Google Maps place URL. FetchLayer resolves any of the three and fetches the review set.
Can I sort or limit the reviews I retrieve?
Yes. Choose newest, most relevant, highest rating, or lowest rating, and control pagination with pages, maxReviews, and reviewsPerPage.
Can I use the data with an AI model?
Yes. The API returns structured JSON that you can store, send to an LLM, or access through FetchLayer’s MCP server to find recurring praise, complaints, and service issues.
Can I analyze and export Google Maps reviews without code?
Yes. FetchLayer Research Chat can retrieve public reviews for a business, analyze recurring themes with AI, and export the structured results as a downloadable CSV or JSON file.
Can I find businesses, not only their reviews?
Yes. /place-search searches Google Maps by keyword and location (or coordinates and a radius) and returns each place with its address, phone, website, rating, hours and business status. /place-details reads a single place in full, including its description and attributes. For contact details, pass the places or their website values to /place-contacts: it reads each business’s own website for email addresses, phone numbers and social profiles.
How does billing work?
Every request is billed like any other FetchLayer endpoint: a reviews call or place details costs one request, and a place search costs one request per Google result page it reads. /place-contacts costs one request per website that answered, plus one per place whose website had to be looked up first; passing the website values from a search skips that lookup.
Start pulling Google Maps reviews today.
Get a free API key, make your first request, and put public feedback to work in your own product or research workflow.
Used by developers at
Individual developers or teams — not official partnerships