Google Maps Restaurant Scraper

Google Maps Restaurant Scraper is an Apify Actor for collecting restaurant leads from Google Maps. It searches by cuisine or keyword, opens each place page, and returns a clean dataset with restaurant identity data, contact details, menu signals, and website targets for downstream enrichment.

This actor is designed for restaurant lead generation, local market research, directory building, and menu-enrichment workflows. It is especially useful when you need a Google Maps restaurant scraper that produces structured output instead of raw HTML.

What this actor extracts

For each restaurant, the dataset can include:

• Restaurant name
• Cuisine or category
• Google Maps rating
• Review count
• Price level
• Address
• Phone number
• Website URL
• External menu URL linked from Google Maps, when available
• Google Maps menu item count
• Website targets for downstream scraping
• Google Maps place URL
• Search location context
• Optional debug-only Google Maps menu preview

What this actor is best for

• Restaurant lead generation from Google Maps
• Local SEO and competitor research
• Building restaurant directories and prospect lists
• Preparing handoff URLs for a second-stage menu scraper
• Mapping which restaurants expose menu data directly in Google Maps

Input

• cuisine: Search keyword such as restaurant, pizza, sushi, vegan cafe, or brunch
• location: City, region, or neighborhood to search
• maxResults: Maximum number of place pages to process
• minimumMenuItemsFromMaps: Threshold used to mark a record for downstream website enrichment
• resultsLanguage: Two-letter Google Maps UI language code, such as en
• resultsCountryCode: Two-letter Google Maps country hint, such as us
• proxyConfiguration: Optional Apify Proxy configuration for harder runs
• includeDebugFields: Adds Google Maps menu preview fields and detection flags

Output

The default dataset is optimized for Apify Store users and downstream automations. Key fields include:

• restaurantId
• name
• cuisine
• website
• primaryWebsiteTarget
• mapsMenuUrl
• googleMapsUrl
• location
• rating
• reviewsCount
• mapsMenuItemCount
• needsWebsiteEnrichment
• websiteTargets
• scrapedAt

The dataset schema also defines two Apify views:

• overview: High-level restaurant table for browsing and export
• enrichmentQueue: Queue-style view focused on URLs to pass into a website or menu scraper

Example output

{
    "restaurantId": "7c4a8d09ca3762af",
    "name": "Example Pizza",
    "cuisine": "Pizza restaurant",
    "website": "https://examplepizza.com/",
    "primaryWebsiteTarget": "https://examplepizza.com/menu",
    "mapsMenuUrl": "https://examplepizza.com/menu",
    "googleMapsUrl": "https://www.google.com/maps/place/...",
    "location": "New York",
    "address": "123 Example St, New York, NY",
    "rating": 4.4,
    "reviewsCount": 1287,
    "priceLevel": "$$",
    "phone": "+1 212-555-0100",
    "mapsMenuItemCount": 14,
    "needsWebsiteEnrichment": true,
    "websiteTargets": ["https://examplepizza.com/menu", "https://examplepizza.com/"],
    "scrapedAt": "2026-03-14T12:00:00.000Z"
}

Notes

• This actor focuses on Google Maps discovery and handoff targets. It does not crawl full restaurant websites by itself.
• Google Maps markup changes over time, so selectors are built with fallbacks but may still require maintenance.
• For larger or more protected runs, Apify Proxy usually improves success rates.
• Use this actor in compliance with Google Maps terms, local laws, and the target site's policies.