Google Maps Scraper (Minimal)

A fast, minimal Google Maps scraping actor built for clean, reliable place data. Give it search terms or URLs, set an optional location or custom area, and get a simple, consistent dataset with the fields you actually need.

Why this actor

Most Maps scrapers return bloated, noisy payloads. This actor focuses on the essentials: title, address, country code, rating, review count, and optional phone/website. It is designed for scale, speed, and predictable output.

What it does

• Searches Google Maps by keywords, URLs, or Place IDs
• Optionally focuses on a specific location or custom GeoJSON area
• Extracts place details with a minimal schema
• Handles retries, backoff, and session rotation for stability

Key features

• Minimal, production-friendly output
• Supports multiple search terms in one run
• [NEW] Auto-Geolocation via Nominatim: Bypasses the 60-result limit of Google Maps by fetching coordinate boundaries automatically.
• Custom GeoJSON area support (customGeolocation) for precision crawling.
• Proxy and session pool support

Automatic Geolocation (Nominatim API)

When you provide a locationQuery (e.g., "Istanbul, Taksim"), this scraper automatically contacts the OpenStreetMap Nominatim API, retrieves the exact geographical polygon of that location, and generates a grid of coordinates.

Instead of performing just 1 search (which Google limits to ~60 results), the scraper automatically splits the map into dozens of smaller viewport segments and crawls each one. This ensures deep, comprehensive scraping!

Example Input (Auto-Geolocation)

{
  "searchStringsArray": ["restaurant", "cafe"],
  "locationQuery": "New York, USA",
  "maxCrawledPlacesPerSearch": 50,
  "language": "en"
}

Output schema (minimal)

Each place record contains only the following fields:

• title
• totalScore
• reviewsCount
• address
• countryCode
• phone (when available)
• website (when available)
• url

Typical use cases

• Local lead generation
• Location-aware market research
• Store and venue directories
• Competitive intelligence
• Light-weight data enrichment

Custom GeoJSON Grid (Advanced)

If you don't want to use the automatic Nominatim API, you can provide an explicit customGeolocation object. The scraper will parse your GeoJSON (Feature, Polygon, or MultiPolygon), split it into coordinate segments, and perform hyper-localized searches.

{
  "searchStringsArray": ["restaurant"],
  "customGeolocation": {
    "type": "Polygon",
    "coordinates": [
      [
        [28.98, 41.035],
        [28.99, 41.035],
        [28.99, 41.045],
        [28.98, 41.045],
        [28.98, 41.035]
      ]
    ]
  }
}

Notes

• Auto-Grid Limits: Depending on the size of the city/town provided in locationQuery, the scraper might generate anywhere from 4 to 100+ precision grid searches automatically.
• Use proxies for better reliability and higher throughput.
• Increase navigationTimeoutSecs or lower maxConcurrency if you see timeouts.