Enrich existing local-business lead rows with public website, contact, social, and health fields

Google Maps Lead Enrichment Scraper appends public website, contact, social, health, and business-signal fields to Google Maps exports, place lists, or local business lead rows you already have. It does not scrape Google Maps itself. Contact-page channel inventory and HTTP status QA on a known URL list belong on Contact Page Audit & Business Channel Extractor and Bulk URL Status Checker.

$25.00 per 1,000 lead_profile_enriched events; $10.00 per 1,000 lead_partial events

Open Google Maps Lead Enrichment Scraper on Apify

Lead-row enrichment, not Google Maps search and not a contact-page audit

Use this page when the job is enriching existing Maps/local-business lead rows with website, emails, phones, contact pages, social links, lightweight website signals, and optional HTTP health. Use Contact Page Audit & Business Channel Extractor when the job is a public business-channel inventory from contact, about, or support pages. Use Bulk URL Status Checker when the job is HTTP status, redirect chains, and timing on a known URL list.

This Actor Contact Page Audit & Business Channel Extractor Bulk URL Status Checker
Intent Enrich existing Maps/local-business lead rows Inventory public business contact channels HTTP status, redirect-chain, timing, and broken-URL QA
Input Lead objects in leads or an Apify dataset in sourceDatasetId (maxLeads 1–1000) Contact, about, support, or company URLs in urls (max 100) Known page URLs in urls (max 1000)
What it reads User-provided lead rows or an existing Apify dataset; public websites/contact pages when contact, signal, or health flags are on Public contact / about / support / policy / company pages Live HTTP(S) responses; it does not crawl pages
Primary output Website, domain, public emails/phones, contact page, social links, website signals, optional HTTP health, status/chargedEvent public_contact_channel rows: support path, phone, social URLs, source context Status code, final URL, redirect chain, response time, severity
Google Maps scrape / search No — it does not scrape Google Maps itself No No

The live Store description is: Enrich existing Google Maps or local business leads with websites, emails, phones, contact pages, social links, website content signals, health checks, confidence, PPE charged events, and no-charge invalid rows. This actor does not scrape Google Maps itself.

Use cases

Those three bullets are the published README use cases. This Actor classifies rows as enriched, partially enriched, invalid, not found, or errored for downstream billing auditability. It is not a Maps search, place-discovery, or Maps listing scraper.

How is Google Maps Lead Enrichment Scraper different from Contact Page Audit & Business Channel Extractor and Bulk URL Status Checker?

This Actor enriches existing Google Maps exports, place lists, or local business lead rows you already have. It does not scrape Google Maps itself. Live inputs are leads (existing Google Maps/local business lead objects) and optional sourceDatasetId (an Apify dataset of lead rows to read). Contact Page Audit & Business Channel Extractor inventories public business contact channels from contact, about, support, policy, and company pages you supply. Required input is urls (maximum 100). Person-level email candidates are suppressed. Bulk URL Status Checker checks a known URL list for HTTP status, redirect chains, response timing, and broken URL findings. Required input is urls (maximum 1000). It does not crawl pages. Use this Actor to append website, contact, social, health, and business-signal fields to lead rows. Use Contact Page Audit when the job is a contact-page channel inventory. Use Bulk URL Status Checker when the job is HTTP status on URLs you already have.

What input is required?

The live OpenAPI input schema has no required array. The README says use leads for direct rows or sourceDatasetId to read an existing Apify dataset. Live fields are leads (array; Existing Google Maps/local business leads; each item can include businessName/name/title, address, website/url/domain, phone, email, placeUrl, and sourceUrl; default/prefill is Example Cafe at 1 Market St, San Francisco, CA), sourceDatasetId (string, default empty; Optional Apify dataset ID containing lead rows to enrich. The actor reads this dataset; it does not scrape Google Maps.), includeContacts (boolean, default true; Fetch public website/contact pages to find public emails, phones, and social profile links.), includeWebsiteContent (boolean, default true; Capture lightweight website title, meta description, and business signal keywords.), includeHealth (boolean, default true; Record HTTP status and response time for the public website.), maxLeads (integer, default 50, minimum 1, maximum 1000; Maximum lead rows to enrich.), delivery (string enum dataset or dataset_and_webhook, default dataset), webhookUrl (string, default empty; Optional HTTPS endpoint when delivery is dataset_and_webhook.), and dryRun (boolean, default false; Validate input and produce preview rows without fetching websites, pushing dataset rows, charging PPE events, or sending webhooks.).

Field Type Default Notes
leads array schema default/prefill: Example Cafe Existing Google Maps/local business leads. Each item can include businessName/name/title, address, website/url/domain, phone, email, placeUrl, and sourceUrl.
sourceDatasetId string empty Optional Apify dataset ID containing lead rows to enrich. The actor reads this dataset; it does not scrape Google Maps.
includeContacts boolean true Fetch public website/contact pages to find public emails, phones, and social profile links.
includeWebsiteContent boolean true Capture lightweight website title, meta description, and business signal keywords.
includeHealth boolean true Record HTTP status and response time for the public website.
maxLeads integer 50 Maximum lead rows to enrich (minimum 1, maximum 1000)
delivery string dataset dataset or dataset_and_webhook
webhookUrl string empty Optional HTTPS endpoint when delivery is dataset_and_webhook
dryRun boolean false Preview rows without fetching websites, dataset writes, PPE charges, or webhooks

Published README / live schema input-object example:

{
  "leads": [
    {
      "businessName": "Example Cafe",
      "address": "1 Market St, San Francisco, CA",
      "website": "https://example.com",
      "phone": "+1 415 555 0100",
      "sourceUrl": "https://example.com"
    }
  ],
  "sourceDatasetId": "",
  "includeContacts": true,
  "includeWebsiteContent": true,
  "includeHealth": true,
  "maxLeads": 50,
  "delivery": "dataset",
  "webhookUrl": "",
  "dryRun": false
}

Run Google Maps Lead Enrichment Scraper on Apify

What does a result row contain?

The published README What it returns list is business name, address, website, normalized domain; public emails, phones, contact page, and social links; lightweight website signals and optional HTTP health status; and status, chargedEvent, sourceUrls, and errors for billing auditability. The Store description also names confidence, PPE charged events, and no-charge invalid rows. There is no published output JSON schema sample object on the Store README. That field list is the published README inventory, not a live coverage guarantee for every input row.

README charged-event keys for useful rows are lead_profile_enriched and lead_partial. Downstream classification also names invalid, not found, and errored rows. This is not a full-page markdown extract and not a contact-page public_contact_channel inventory — those jobs belong on Website Content Extractor and Contact Page Audit & Business Channel Extractor.

Does it scrape Google Maps or search for local businesses?

No. The live Store description states this actor does not scrape Google Maps itself. The README states it does not scrape Google Maps itself and works on user-provided rows or an Apify dataset you already have. The live sourceDatasetId description repeats: The actor reads this dataset; it does not scrape Google Maps. It does not run Maps search, place discovery, or Maps listing scrape. Supply existing Google Maps exports, place lists, or local business lead rows.

Public emails, phones, and social profile links come from public website/contact pages when includeContacts is true. Lightweight title, meta description, and business-signal keywords come from includeWebsiteContent. HTTP status and response time for the public website come from includeHealth. All three flags default to true.

How is Google Maps Lead Enrichment Scraper priced?

Billing is pay per event. Live Store events are Lead profile enriched at $0.025 ($25.00 / 1,000): a business lead was enriched with a website/domain plus meaningful public contact, page, social, health, or business signal data; Partial lead enrichment at $0.01 ($10.00 / 1,000): a lead produced partial but useful enrichment data, such as a verified website/domain or limited public contact/signal data; and Actor Start at $0.00005, charged when the Actor starts running (number of events depends on Actor memory, one event per GB, minimum one event). Platform usage is listed as Included on the pricing page. The Store README pricing section states you are not charged for Apify platform usage, only a fixed price for specific events.

README charged event keys are lead_profile_enriched (useful enriched lead) and lead_partial (useful partial lead). invalid, not_found, error, and dry-run rows are no-charge.

$25.00 / 1,000 lead_profile_enriched; $10.00 / 1,000 lead_partial; Actor Start $0.00005

See Google Maps Lead Enrichment Scraper pricing on Apify

How do dataset delivery, webhooks, and dry runs work?

delivery defaults to dataset (write enriched leads only to the dataset). Set delivery to dataset_and_webhook and provide webhookUrl (HTTPS) to also send the final rows after the run. dryRun true validates input and produces preview rows without fetching websites, pushing dataset rows, charging PPE events, or sending webhooks. Live schema delivery values are dataset and dataset_and_webhook; webhook alone is not a live enum value.

Open Google Maps Lead Enrichment Scraper on Apify

Limits to keep in mind

Open Google Maps Lead Enrichment Scraper on Apify

Related pages