Entdeckung lokaler Unternehmen
Mit Google Maps-Endpunkten verwandelst du entdeckung lokaler unternehmen in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Lokale Unternehmens- und Standortdaten von Google Maps für Location-Intelligence-Workflows sammeln.
Standortdetails und lokale Suchergebnisse von Google Maps über dokumentierte Crawlora-API-Endpunkte abrufen.
Endpunkt-Familien
2
Dokumentierte Parameter
10
Beispiele
4
Live-Katalog-Snapshot
Aktive Endpunkte
4
Methoden
GET, POST
Pflichtparameter
8
Schema-Referenzen
4
{
"platform": "Google Maps",
"endpoint": "google-map-place",
"method": "GET",
"path": "/google/map/place/{place_id}",
"auth": "apiKey"
}Verwandte Use Cases
Kostenlose Tools
Use Cases
Standortdetails und lokale Suchergebnisse von Google Maps über dokumentierte Crawlora-API-Endpunkte abrufen.
Mit Google Maps-Endpunkten verwandelst du entdeckung lokaler unternehmen in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Google Maps-Endpunkten verwandelst du anreicherung von standortdetails in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Google Maps-Endpunkten verwandelst du location intelligence in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Google Maps-Endpunktkatalog — 4 Endpunkte, 10 dokumentierte Request-Parameter und 4 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
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.
Abdeckungskarte
Diese Karten werden aus dem aktiven Endpunktkatalog generiert, damit die Landingpage dieselbe API-Oberfläche widerspiegelt, die auch Docs und Playground nutzen.
/google/map/place/{place_id}
/google/map/search
Endpunktkatalog
/google/map/place/{place_id}Returns detailed information for a specified place_id. Rate limit is enforced at 1 request per second.
Hinweise zur Response
- `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`.
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.
Hinweise zur Response
- `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 } ] } ```
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.
Hinweise zur Response
- 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 } ] } ] } ```
MCP-Tool google_map_place_reviews
/google/map/searchReturns results from Google Maps based on search options. Rate limit is enforced at 1 request per second.
Hinweise zur Response
- `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`.
MCP-Tool google_map_search
Verwandte APIs
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.
So scrapst du Google Maps
Google Maps hat den umfangreichsten öffentlichen Datensatz zu lokalen Unternehmen, ist aber für menschliches Browsing gerendert, nicht für APIs. Crawloras Google-Maps-Endpunkte liefern Standorte, Bewertungen, Reviews und Kontaktdaten als strukturiertes JSON.
Suche mit Suchbegriff plus Ort (z. B. „Cafés in Berlin“) oder finde einen einzelnen Standort per Name oder ID.
Übergib Suchbegriff und Ort (oder die Standortreferenz) an Crawloras Google-Maps-Endpunkt — kein Headless Browser zu pflegen.
Erhalte pro Ergebnis Name, Adresse, Telefonnummer, Bewertung, Anzahl Reviews, Öffnungszeiten, Koordinaten und Website.
Dedupliziere nach Domain, reichere jede Website mit der Contact API um E-Mail und Social an, oder lass es periodisch neu laufen, um neue und geänderte Standorte zu verfolgen.
FAQ
Übergib Suchbegriff plus Ort (oder einen bestimmten Standort) an Crawloras Google-Maps-Endpunkt. Du erhältst strukturiertes JSON — Name, Adresse, Telefon, Bewertung, Reviews, Öffnungszeiten, Koordinaten und Website —, ohne eigene Browser-Automatisierung. Sammle öffentliche Daten und halte dich an Googles Bedingungen.
Ja — Crawloras Google-Maps-Endpunkt funktioniert als Google-Maps-Daten-API und liefert Standorte, Bewertungen, Reviews, Öffnungszeiten, Koordinaten und lokale Unternehmensdaten als strukturiertes JSON. Er liefert Maps-Ergebnisse, ohne die Quoten der offiziellen Places API oder einen Headless Browser verwalten zu müssen.
Google Maps listet pro Unternehmen nur Website und Telefonnummer, keine E-Mail. Kombiniere Maps-Ergebnisse mit Crawloras Contact API, um von jeder Unternehmens-Website E-Mail und Social-Profile zu extrahieren — das fehlende letzte Glied für Outreach.
Das Sammeln öffentlich sichtbarer Standort- und Unternehmensdaten ist im Rahmen von Googles Nutzungsbedingungen, robots-Direktiven, Ratenlimits und geltendem Recht in der Regel zulässig. Das gilt für öffentliche Daten, die du sammeln darfst.