Google Maps Business Scraper

Extract business data from Google Maps with intelligent email discovery

---

Key Features

High-Speed Extraction
Optimized for performance with average extraction time of 2.5 seconds per business. Uses intelligent wait strategies and ARIA-based selectors for maximum reliability.

Hybrid Email Extraction
Uses a two-tier approach for email discovery. The primary method combines Impit (a stealthy HTTP client with browser-like TLS fingerprints) with Cheerio for fast HTML parsing. Playwright browser automation serves as a fallback for JavaScript-heavy websites.

Multi-Language Support
Detects and navigates contact pages in over 30 languages, including English, German, French, Spanish, Italian, Portuguese, Russian, Japanese, Chinese, Korean, and many more.

Smart Resource Management
Built-in memory pressure handling, intelligent caching, and adaptive rate limiting ensure stable operation even with large result sets.

Performance Benchmarks

Tested locally with 97 businesses in Frankfurt, Germany:

Metric	Value
Total Results	97 businesses
Total Time	6.5 minutes
Average per Result	2.5 seconds
Address Coverage	100%
Phone Coverage	98%
Website Coverage	99%
Rating Coverage	100%

Extraction Speed by Phase

Phase	Time	Details
Navigation and Setup	3 seconds	Page load, consent handling
Result Loading	25 seconds	Loads up to 100 results via scroll
Data Extraction	2.5s per result	Full business details
Email Extraction	0.3s per website	When enabled

Note: Performance may vary based on network conditions, proxy response times, and Google Maps server load.

Input Parameters

Parameter	Type	Description	Default
businessType	String	What to search for (e.g., "restaurant", "hotel", "dentist")	Required
location	String	Where to search (e.g., "Frankfurt, Germany", "Los Angeles, CA")	Required
maxResults	Integer	Number of results to extract (1-100)	3
extractEmails	Boolean	Enable deep website scanning for email addresses	false

Output Data

Each extracted business includes:

Field	Description	Coverage
01_name	Business name	100%
02_address	Street address	100%
03_rating	Google rating (1-5 stars)	100%
04_reviews	Total number of reviews	98%
05_phone	Phone number	98%
06_website	Website URL	99%
07_email	Email address (when extraction enabled)	Varies
08_search_query	Original search term	100%
09_maps_url	Direct Google Maps link	100%
10_scraped_at	Extraction timestamp (ISO 8601)	100%
11_socials	Social media profiles (LinkedIn, Facebook, Twitter, Instagram, TikTok)	When found

Usage Examples

Basic Search

{
    "businessType": "Hotel",
    "location": "Paris, France",
    "maxResults": 10
}

Search with Email Extraction

{
    "businessType": "Dentist",
    "location": "Los Angeles, CA",
    "maxResults": 25,
    "extractEmails": true
}

Cost Estimation

Configuration	Approximate Cost (per 10 results)
Basic extraction	$0.01 - $0.02
With email extraction	$0.05 - $0.10

Actual costs vary based on website complexity, proxy usage, and geographic region.

Technical Details

Dependencies

Package	Version	Purpose
apify	3.6.0	Apify SDK for actor lifecycle and dataset management
crawlee	3.16.0	Web crawling framework with PlaywrightCrawler
playwright	1.58.2	Browser automation (Chromium 145+)
cheerio	1.1.2	Fast HTML parsing for email extraction
impit	0.7.4	Stealthy HTTP client with browser TLS fingerprints
apify-client	2.21.0	Apify API client

Proxy Configuration

• Residential proxies for reliable access
• Dual-proxy architecture (DATACENTER + RESIDENTIAL fallback)
• Automatic session management
• Trust-based adaptive rate limiting
• Smart retry with exponential backoff

Why Residential Proxies?
Google Maps requires premium proxy infrastructure for reliable access. Residential proxies provide the best success rate and data quality.

Limitations

• Maximum 100 results per run
• Email extraction increases runtime by approximately 3-5x
• Some websites may block automated access
• Results depend on Google Maps data availability
• Rate limiting may apply for high-volume usage

Version

v8.2.0 — March 2026

Advanced Features

For advanced use cases including Google Search enrichment and owner data discovery, see the dedicated actor:

Unified Serper.dev ETL Processor

Support

For questions, issues, or feature requests, please open an issue on the actor page.

---

Built with care for the Apify community