Google Maps Lead & Competitor Intelligence

Turn Google Maps searches into sales-ready local-business intelligence instead of a raw place dump.

What it returns

Each business_lead row can include:

• business name, category, address, phone, website, rating, review count, price level, coordinates, and Maps URL
• public emails, website phones, and public social-profile links when website enrichment is enabled
• leadScore and leadTier
• contactabilityScore
• reputationRiskScore
• opportunitySignals such as no_website, reputation_improvement, review_generation, and verified enrichment signals such as weak_social_presence
• salesAngles such as website_build, reputation_management, review_growth, social_presence, and local_seo
• monitoring fields for new/changed businesses when monitoring is enabled

Every search also returns a free search_summary with market coverage, rating, category, lead-tier, and sales-angle aggregates. summaryScope states whether the summary covers all returned rows or only returned changes.

Why this Actor exists

Google Maps lead generation is one of the largest proven demand categories on Apify. Raw extraction is already highly competitive, so this Actor focuses on the next step: identifying which businesses are worth contacting and why.

Typical users:

• web-design and local-SEO agencies
• B2B lead-generation teams
• reputation-management agencies
• territory and market researchers
• sales teams looking for local businesses with identifiable digital gaps

Input example

{
  "searchQueries": ["dentists in Athens Greece"],
  "maxPlacesPerQuery": 25,
  "enrichWebsites": true,
  "monitorChanges": false
}

You can also supply Google Maps search/place URLs in startUrls. At least one query or Maps URL is required at runtime.

Source and reliability

Google Maps is a dynamic browser source. This Actor uses Playwright because Google Maps is a dynamic browser-rendered source and static HTML parsing alone can be unreliable.

Network policy:

1. direct browser session first
2. detect blocking/challenge/timeout signals
3. bounded retry/backoff
4. only then use the configured proxy and rotate sessions up to maxProxyRotations
5. open a circuit after persistent blocking or a likely source-structure break instead of burning requests across every query
6. never attempt CAPTCHA solving
7. emit a diagnostic record rather than silently returning fake success

For production use, keep browser concurrency low and leave Apify Proxy available as fallback. Default memory is 4096 MB because browser-rendered Google Maps is resource intensive; concurrency is capped at 2.

Website enrichment

When enabled, the Actor visits only the public business website plus a small number of likely contact/about pages. It extracts public, displayed contact information. It does not guess emails and does not log proxy credentials.

Website enrichment rejects localhost, private/reserved IP targets, credential-bearing URLs, and unsafe redirects before fetching them. When enrichment is disabled, email/social absence is treated as unknown rather than as a negative sales signal.

Monitoring

monitorChanges=true creates a baseline scoped to the exact search/filter configuration. The first run does not label every result as falsely new. Later runs detect changes in rating, review count, address, phone, website, and closure status.

onlyChanges=true returns the full baseline on the first monitoring run and only new/changed leads afterward.

missingBusinessesSinceLastRun means a previously observed business is missing from the current sampled search result set. It does not claim that the business has permanently closed or disappeared from Google Maps.

Pricing

This Actor uses Pay Per Event pricing:

• lead-returned: $0.0035 per useful, deduplicated business lead
• equivalent price: $3.50 per 1,000 returned leads
• Actor start: $0.00005

The lead-returned event is the primary billable event.

Search summaries, diagnostics, retries, proxy rotations, cache operations, and duplicate rows are not billed as lead events.

Limits

• Google Maps can change its UI and anti-bot behavior.
• Browser scraping has higher platform cost than API/feed-based Actors.
• Website contact enrichment is best-effort and only reports public information actually found.
• A successful run is not considered valid if Google returns a CAPTCHA/challenge/hollow shell; the Actor reports a diagnostic instead.
• Google Maps result ranking can change between runs, so monitoring counts are scoped to the sampled result window configured by the user.