Descubrimiento de negocios locales
Usa los endpoints de Google Maps para convertir descubrimiento de negocios locales en solicitudes API repetibles con inputs documentados y respuestas JSON.
Recopila datos de negocios locales y lugares de Google Maps para workflows de inteligencia de ubicación.
Obtén detalles de lugares y resultados de búsqueda local de Google Maps mediante endpoints documentados de la API de Crawlora.
Familias de endpoints
2
Parámetros documentados
10
Ejemplos
4
Snapshot en vivo del catálogo
Endpoints activos
4
Métodos
GET, POST
Parámetros obligatorios
8
Referencias de esquema
4
{
"platform": "Google Maps",
"endpoint": "google-map-place",
"method": "GET",
"path": "/google/map/place/{place_id}",
"auth": "apiKey"
}Casos de uso relacionados
Herramientas gratuitas
Casos de uso
Obtén detalles de lugares y resultados de búsqueda local de Google Maps mediante endpoints documentados de la API de Crawlora.
Usa los endpoints de Google Maps para convertir descubrimiento de negocios locales en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Google Maps para convertir enriquecimiento de detalles de lugares en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Google Maps para convertir inteligencia de ubicación en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Google Maps — 4 endpoints, 10 parámetros de solicitud documentados y 4 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
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.
Mapa de cobertura
Estas tarjetas se generan a partir del catálogo de endpoints activo, así que la landing page refleja la misma superficie de API que usan Docs y Playground.
/google/map/place/{place_id}
/google/map/search
Catálogo de endpoints
/google/map/place/{place_id}Returns detailed information for a specified place_id. Rate limit is enforced at 1 request per second.
Notas de la respuesta
- `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`.
Herramienta MCP 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.
Notas de la respuesta
- `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. Example response: ```json { "code": 200, "msg": "ok", "data": [ { "url": "https://lh3.googleusercontent.com/gps-cs-s/AHRPTWlbepbs69mWZVN7SNi4FYseIr1JvRCpGHgpFfN5wOf02mKO=w203-h100-k-no", "width": 203, "height": 100 }, { "url": "https://lh3.googleusercontent.com/gps-cs-s/AHRPTWntpDTSCFVQdK1TmGSIhUaUWhoH45c1klBfg6se1L-m4xSO=w408-h306-k-no", "width": 408, "height": 306 } ] } ```
Herramienta MCP 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.
Notas de la respuesta
- 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. Example response: ```json { "code": 200, "msg": "ok", "data": [ { "id": "Ci9DQUlRQUNvZENodHljRjlvT201dFRHSk1aRU54T0U5cmRFVjNlbGRmU1RJNFkzYxAB", "rating": 5, "text": "I never knew pork could taste this good. We tried the special loin and it was worth the queue.", "relative_time": "6 months ago", "published_at": "2026-01-01T14:39:25Z", "author_name": "Supisara Darnchaloemwong", "author_id": "112997636113922766481", "author_url": "https://www.google.com/maps/contrib/112997636113922766481", "author_photo": "https://lh3.googleusercontent.com/a-/ALV-UjWc6XFX9IKHJiQ4vZoY7o_EVCYkjMbWjGfdPZrLEw", "author_review_count": 23, "source": "Google", "photos": [ { "url": "https://lh3.googleusercontent.com/grass-cs/ACvplmM2ICW60UtuEQbkJLN-ot5vq3pCknhfn=w1207-h1262-k-no", "width": 1207, "height": 1262 } ] } ] } ```
Herramienta MCP google_map_place_reviews
/google/map/searchReturns results from Google Maps based on search options. Rate limit is enforced at 1 request per second.
Notas de la respuesta
- `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`.
Herramienta MCP google_map_search
APIs relacionadas
Maps & Local Data
Search ready-made scraped datasets for local business research with filters, facets, geo queries, and repeatable API output.
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.
Cómo hacer scraping de Google Maps
Google Maps tiene el conjunto de datos públicos de negocios locales más completo, pero está renderizado para navegación humana, no para una API. Los endpoints de Google Maps de Crawlora devuelven lugares, calificaciones, reseñas e información de contacto como JSON estructurado.
Busca con una consulta más una ubicación (por ejemplo, «cafeterías en Madrid»), o encuentra un lugar individual por nombre o ID.
Pasa la consulta y la ubicación (o la referencia del lugar) al endpoint de Google Maps de Crawlora — sin necesidad de mantener un navegador headless.
Obtén, por cada resultado, nombre del negocio, dirección, teléfono, calificación, número de reseñas, horario, coordenadas y sitio web.
Deduplica por dominio, enriquece cada sitio web con la Contact API para obtener email y redes sociales, o vuelve a ejecutarlo periódicamente para seguir negocios nuevos o modificados.
Preguntas frecuentes
Pasa una consulta más una ubicación (o un lugar específico) al endpoint de Google Maps de Crawlora. Obtienes JSON estructurado — nombre del negocio, dirección, teléfono, calificación, reseñas, horario, coordenadas y sitio web — sin mantener tu propia automatización de navegador. Recopila datos públicos y respeta los términos de Google.
Sí — el endpoint de Google Maps de Crawlora funciona como una API de datos de Google Maps y ofrece lugares, calificaciones, reseñas, horarios, coordenadas y datos de negocios locales como JSON estructurado. Devuelve resultados de Maps sin necesidad de gestionar las cuotas de la Places API oficial ni un navegador headless.
Google Maps solo lista el sitio web y el teléfono de cada negocio, no incluye email. Combinar los resultados de Maps con la Contact API de Crawlora permite extraer email y perfiles sociales del sitio web de cada negocio — la pieza que faltaba para el outreach.
Recopilar datos públicamente visibles de lugares y negocios suele ser aceptable si se respetan los términos de uso de Google, las directivas de robots, los límites de tasa y la ley aplicable. Esto aplica a datos públicos que tienes derecho a recopilar.