Local business discovery
Use Google Maps endpoints to turn local business discovery into repeatable API requests with documented inputs and JSON responses.
Collect local business and place data from Google Maps for location intelligence workflows.
Fetch Google Maps place details and local search results through documented Crawlora API endpoints.
Endpoint families
2
Documented params
10
Examples
4
Live catalog snapshot
Active endpoints
4
Methods
GET, POST
Required params
8
Schema refs
4
{
"platform": "Google Maps",
"endpoint": "google-map-place",
"method": "GET",
"path": "/google/map/place/{place_id}",
"auth": "apiKey"
}Related use cases
Free tools
Use cases
Fetch Google Maps place details and local search results through documented Crawlora API endpoints.
Use Google Maps endpoints to turn local business discovery into repeatable API requests with documented inputs and JSON responses.
Use Google Maps endpoints to turn place detail enrichment into repeatable API requests with documented inputs and JSON responses.
Use Google Maps endpoints to turn location intelligence into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Google Maps endpoint catalog — 4 endpoints, 10 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
4 documented Google Maps endpoints, grouped into 2 request families — Place and Search.
10 request parameters are documented across those Google Maps endpoints, 8 of them required — the full input contract is public before you write any integration code.
4 of the 4 Google Maps endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Google Maps endpoints document their error responses (400, 429 and 500) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
4 hosted MCP tools back the Google Maps endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/google/map/place/{place_id}
/google/map/search
Endpoint catalog
/google/map/place/{place_id}Returns the Google Maps details of one place by its Google `place_id`: name, categories, address, coordinates, phone, website, description, image, amenities, rating and review count. `rating` is `null` when the place has no aggregate rating on Google.
Response notes
- `rating` is the aggregate Google rating (`1.0`–`5.0`), or `null` when the place has no aggregate rating on Google (too few reviews, or a place type Google does not rate) — never a literal `0`. Read it together with `review_count`.
Sampled 14 Oct 2026: 14 of 15 fields returned with a value. rating: 4.1; name: “Googleplex”.
MCP tool google_map_place
/google/map/place/{place_id}/photosReturns the photos Google publishes for a specified place_id — the imagery shown on the place's Google Maps page, typically dozens of images for a well-covered business. Each entry carries the image URL as served plus its pixel dimensions when reported; swap the trailing size suffix on the URL (e.g. `=w203-h100-k-no`) to request other dimensions. Contributor avatars and review-attached photos are excluded. This is the place page's image set, not a paginated archive feed. Rate limit is enforced at 1 request per second.
Response notes
- `url` is Google's image URL exactly as served, including its trailing size suffix (for example `=w203-h100-k-no`). Swap that suffix to request other dimensions. - `width` and `height` are the pixel dimensions of that URL when Google reports them. `0` means the dimension was not captured, not that the image is empty. - Contributor avatars and review-attached photos are excluded; this endpoint returns place imagery only. Photos attached to individual reviews belong to the review that carries them. - Each distinct image appears exactly once, at the largest size Google offers for it. Google's payload carries the same photo at several sizes; those variants are collapsed rather than returned as separate entries. - This is the place page's image set, **not** a paginated archive feed. There is no cursor to walk, so the response is the full set this endpoint can return for the place. - A place with no published photos returns an empty `data` array, not an error.
MCP tool google_map_place_photos
/google/map/place/{place_id}/reviewsReturns the reviews Google shows on a specified place_id's Google Maps page — typically the 8 most relevant, each with its rating, text, reviewer, timestamp, and any photos the reviewer attached. Photo-only reviews return an empty `text`. This is the place page's first page of reviews, not the full review archive. Rate limit is enforced at 1 request per second.
Response notes
- This is the place page's **first page** of reviews, not the full review archive. There is no cursor to page through, so the response is the complete set this endpoint can return for the place. Use `review_count` on `/google/map/place/{place_id}` for the place's total review tally. - `text` is empty for a photo-only review — Google allows a review with photos and a rating but no written body. That is not a parse failure. - `published_at` is RFC3339 UTC. It is empty when Google did not report a timestamp. - `relative_time` is Google's own wording ("6 months ago") in the requested language, so it is a display string rather than something to parse — use `published_at` for date logic. - `photos` are the images attached to that specific review. They never overlap with `/google/map/place/{place_id}/photos`, which returns the place's own gallery; a review's photos belong to the review. - `author_url` is normalized to drop Google's `?hl=` suffix, so the same reviewer yields the same URL regardless of the request language. - `author_review_count` is how many reviews that contributor has written overall. `0` means Google did not report it, which is normal for a syndicated review. - `source` names the site the review came from. Google's place pages syndicate reviews from partner sites — common on hotels — so this is `Google` for a native Google review and the partner's name (for example `Tripadvisor`, `TrustYou`) otherwise. Syndicated reviews still carry a rating, text, author name, and timestamp, but have no Google contributor id, so `author_id` is empty and `author_url` points at the partner site rather than a Google contributor page. - A place nobody has reviewed returns an empty `data` array, not an error.
Sampled 14 Oct 2026: 5 items, 11 fields filled in every item, 1 not. published_at: 2026-07-05 to 2026-08-19; rating: 1 to 5, median 1.
MCP tool google_map_place_reviews
/google/map/searchSearches Google Maps with a request body of `keyword`, `language` and `country` (an ISO-2 code such as `us`), all required. Each place has its name, place id, categories, address, coordinates, phone, website, rating and review count. `rating` is `null` when Google has no aggregate rating.
Response notes
- `rating` is the aggregate Google rating (`1.0`–`5.0`), or `null` when the place has no aggregate rating on Google (too few reviews, or a place type Google does not rate) — never a literal `0`. Read it together with `review_count`.
Sampled 14 Oct 2026: 3 items, 11 fields filled in every item, 4 not. rating: 3 to 4.4, median 3.3; name: “OpenAI Inc.” and 2 other values.
MCP tool google_map_search
Related APIs
Maps & Local Data
Search stored local-business datasets with filters, facets, geo queries, and repeatable API output; Apple Maps results depend on its index being populated.
Maps & Local Data
Normalize location search, coordinate lookup, and OSM identifier enrichment through API-key protected geocoding endpoints.
Maps & Local Data
Compare cities and countries with normalized Numbeo cost-of-living and quality indices. Retrieve city or country detail and current or historical rankings for location research, relocation products, market analysis, and local-data enrichment.
How to scrape Google Maps
Google Maps holds the richest public local-business dataset, but it's rendered for humans, not APIs. Crawlora's Google Maps endpoints return places, ratings, reviews, and contact details as structured JSON. A pull on 2026-10-27 of the Google routes showed 10 suggestions for web scraping, 10 news results for ai, and an age field given as relative text.
/google/map/place/ChIJj61dQgK6j4AR4GeTYWZsKWw returned Googleplex with an address, latitude 37.4220541, longitude -122.0853, rating 4.2, review_count 9,602 and a website on 2026-10-30.
/google/map/place/{place_id}/reviews?limit=20 returned review rows, while /photos?limit=20 returned an empty data value for the same place, so handle an empty photo result as a normal outcome.
Dedupe by domain, enrich each website with the Contact API for emails and socials, or re-run on a schedule to track new and changed listings.
google-news for ai returned 10 results where the first, In China, the AI bubble has already burst (Reuters), had an age of 17 hours ago. Convert relative text to a timestamp using the retrieval time.
google-suggest for web scraping returned 10 suggestions with a position and a source field (web). The same Reuters story led Bing's news results on the same day, so compare engines by position as well as by presence.
Client libraries
Install the dedicated Google client for your language. Each package covers the Google endpoints on this page and calls Crawlora's hosted API with your API key.
npm install @crawlora-org/googlenpmpip install crawlora-googlePyPIgo get github.com/Crawlora-org/crawlora-googlepkg.go.devgem install crawlora-googleRubyGemsnet.crawlora:crawlora-googleMaven Centralcomposer require crawlora/googlePackagistcargo add crawlora-googlecrates.ioAgent skills
Install a Crawlora agent skill and your agent can pull Google Maps data as JSON through the documented API, without writing a scraper. These skills cover Google Maps:
Retrieve Google Finance quote, company, chart, financial, news, related-instrument, and market snapshots using Crawlora. Use for source-attributed…
npx skills add github.com/Crawlora-org/crawlora-skills --skill google-finance-researchCompare search interest, regional patterns, seasonality, and rising queries through Crawlora's Google Trends endpoints. Use for topic-demand briefs…
npx skills add github.com/Crawlora-org/crawlora-skills --skill google-trends-researchSearch Google Maps businesses and places, retrieve place details, and inspect review samples or photos through the Crawlora REST API. Use for…
npx skills add github.com/Crawlora-org/crawlora-skills --skill google-maps-researchFAQ
Pass a search query plus location (or a specific place) to Crawlora's Google Maps endpoint. You get structured JSON — business name, address, phone, rating, reviews, hours, coordinates, and website — without maintaining browser automation. Collect public data and respect Google's terms.
Yes — Crawlora's Google Maps endpoints are a Google Maps data API for places, ratings, reviews, hours, coordinates, and local business data as structured JSON. It returns Maps results without managing the official Places API quota or a headless browser.
Google Maps lists each business's website and phone, not its email. Pair the Maps results with Crawlora's Contact API to pull emails and social profiles from each business's website — the missing piece for outreach.
Scraping publicly visible place and business data is generally permissible if you respect Google's terms of use, robots directives, rate limits, and applicable law. This is for public data you're authorized to collect.
Not in this route. The 2026-10-27 results had an age such as 17 hours ago.