Google Maps Lead Scraper avatar

Google Maps Lead Scraper

Pricing

from $0.01 / 1,000 dataset items

Go to Apify Store
Google Maps Lead Scraper

Google Maps Lead Scraper

Build a qualified lead file from Google Maps. The run accepts Google Maps page URLs and keeps names, titles, addresses, phone numbers, and email addresses together for matching and research.

Pricing

from $0.01 / 1,000 dataset items

Rating

0.0

(0)

Developer

ReapX

ReapX

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

an hour ago

Last modified

Share

Build a qualified lead file from Google Maps. The run accepts Google Maps page URLs and keeps names, titles, addresses, phone numbers, and email addresses together for matching and research.

Google Maps Lead Scraper interface

The record

The dataset schema names every field before the run. The first working set is name, title, url, address, phone, website, domain, email, emails, socials, category, and rating. Dataset views keep related fields together without changing the underlying row.

Captured row

{
"cid": "0x8644c90a16f876a5:0x791c022b855d1ac9",
"placeId": "ChIJpXb4FgrJRIYRyRpdhSsCHHk",
"rating": 4.8
}

Input

Google Maps Lead Scraper accepts source URLs. Run controls stay in the same form.

FieldWhat it controlsStarting value
startUrlsEnter Google Maps search terms or identifiers, one per line.["dentists in austin"]
maxItemsStop after this many dataset rows.20
maxSecondsStop after this many seconds and keep completed rows.180

Example input

{
"startUrls": [
"dentists in austin"
],
"maxItems": 3,
"maxSeconds": 180
}

Price

$0.00001 per dataset item. Other Apify plans use the rates shown in the Pricing tab.

Google Maps Lead Scraper input and result demonstration

Console, API, schedules, and exports

Runs can begin in Apify Console, from a saved task, or through the Actor API. A schedule can reuse the same input. Completed rows remain in the run dataset for API retrieval and Apify dataset exports.

POST https://api.apify.com/v2/acts/3aQIyGeUX5SV3HZzS/runs
GET https://api.apify.com/v2/datasets/{datasetId}/items

Saved tasks

Twenty task pages cover distinct research, comparison, operations, automation, and export jobs. The opening set is:

  • Google Maps lead exact lookup: Review one Google Maps record around name, title, category, and address. The saved task uses startUrls, maxItems, and maxSeconds and opens the overview view. Configured in Google Maps Lead Scraper.
  • Google Maps lead account comparison: Compare Google Maps leads using rating, reviewsCount, name, and title. The stats view keeps the differences close together. Configured in Google Maps Lead Scraper.
  • Google Maps lead source list: Process a saved Google Maps input queue with startUrls, maxItems, and maxSeconds. Source and identifier fields remain visible in the identity view. Configured in Google Maps Lead Scraper.
  • Google Maps lead identity index: Index Google Maps leads by name, title, route, and domain. The saved input keeps the same matching keys from run to run. Configured in Google Maps Lead Scraper.
  • Google Maps lead contact coverage: Assemble a Google Maps register centered on phone, website, domain, and email. The task keeps startUrls, maxItems, and maxSeconds visible for later review. Configured in Google Maps Lead Scraper.
  • Google Maps lead audience benchmark: Compare numeric and status fields across Google Maps leads, led by rating, reviewsCount, latitude, and longitude. Results open as the location table. Configured in Google Maps Lead Scraper.

Support

Include the Actor ID, run ID, saved task name, and affected input when reporting an issue. That is enough to locate the run and its dataset.