# 📍 Contractor Lead Scraper — Verified Emails, No Bounces (`qualifyops/maps-leads-verified`) Actor

Google Maps leads scraper with verified emails: search any business type + city, get name, phone, website, address, and a verified deliverable email per business — no bounces. Build local business email lists (dentists, restaurants, plumbers, real estate) for cold outreach. Pay per verified lead.

- **URL**: https://apify.com/qualifyops/maps-leads-verified.md
- **Developed by:** [QualifyOps](https://apify.com/qualifyops) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 verified business leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Maps Leads (Verified) — Google Maps business leads with VERIFIED emails that don't bounce

**You give:** a search query + a location — e.g. `dentists` + `Austin TX`.
**You get:** one row per local business — name, category, address, phone, website — and, the part that actually matters, a **verified, deliverable business email**.
**You pay:** **only per verified lead — $0.02.** Businesses with no verified email are returned **free**.

No browser automation, no scraping of protected sources. Google Maps data comes from the category-standard place crawler; the email is harvested from **the business's own website** and then put through a **live SMTP deliverability check**.

***

#### Why "verified" is the whole point

The Google-Maps-leads category is huge — the leading actor does over a million paid runs a month. But the emails those tools hand you **bounce**. You import them, you send, and half of them die on the first send: your open rates crater and your sending domain reputation takes the hit.

Here, every `VERIFIED` row's email has been through:

> harvested from the business's own site → syntax → MX record → **live SMTP mailbox check** → catch-all detection → confidence score

Only an address that a real mail server **accepts**, that is **not catch-all**, at **confidence ≥ 0.80**, is returned with a `verified_email`. Everything else is `NO_EMAIL` with a reason — never a silent, billed guess.

#### How it works

1. **Source the map.** Your `query` + `location` become a Google Maps search (`dentists in Austin TX`). We delegate to the category-standard **Google Places crawler** to get up to `maxResults` businesses with their name, category, address, phone and website. That crawler's per-result cost is upstream.
2. **Find the email (free, local).** For every business that has a website, we fetch its **own** homepage, `/contact` and `/about`, harvest every published address, and pick the best **business** email — `info@`, `contact@`, `hello@`, `office@` first, then a named person on the business's domain. We drop `noreply@`, image filenames and tracking-pixel noise.
3. **Verify (one batched check).** All picked emails go to a proven Apify Store validator with real SMTP egress, in a single call per run.
4. **Emit everything, charge for verified only.** Every business is returned so you see full map coverage. **You are charged only for rows that carry a `VERIFIED` deliverable email.**

#### What each row gives you

| Column | Meaning |
|---|---|
| `action` | **VERIFIED** (deliverable email) or **NO\_EMAIL** (with reason) |
| `name` | Business name |
| `category` | Google Maps category |
| `address` | Full address |
| `phone` | Business phone |
| `website` | Business website |
| `verified_email` | The deliverable business email — **only on VERIFIED** |
| `confidence` | 0–1 deliverability confidence |
| `place_url` | Google Maps place link |
| `reason` | On NO\_EMAIL: `no_website` / `no_published_email` / `catch_all_domain` / `email_rejected` / `email_unverified` / `verifier_unavailable` |
| `best_guess_email` | On NO\_EMAIL: the address we found but could not verify, **clearly not verified** |

#### Honest by design

- We **never invent** an address and label it verified. `VERIFIED` means a live mail server accepted that specific mailbox.
- **Catch-all domains** — which accept everything and confirm nothing — are returned as `NO_EMAIL` (`catch_all_domain`) and are **not charged**.
- If the verifier is unavailable, we degrade to `NO_EMAIL` (`verifier_unavailable`) — never a fabricated "deliverable" result, never a charge.
- Businesses with no website or no published email are still in the output (free) so you keep **full map coverage** — you just don't pay for them.

#### For agents & automation

Call it via the Apify **API** or **MCP**. Pass `{query, location, maxResults}` and get back deduped business rows with verified emails — ideal as the first step in an outbound pipeline. **Schedule** it to refresh a local-market lead list into your CRM or sequencer. You pay only for the leads that are actually reachable.

***

*Input: `query` + `location` (required), optional `maxResults` (cost cap), `mapsActorId`, `verifierActorId`, `requestTimeoutSecs`.*

# Actor input Schema

## `query` (type: `string`):

What kind of business to find, e.g. "dentists", "coffee shops", "plumbers". Combined with location as a Google Maps search.

## `location` (type: `string`):

City / region to search in, e.g. "Austin TX", "Portland OR", "London UK".

## `maxResults` (type: `integer`):

Upper bound on how many Google Maps businesses to crawl. Caps upstream crawler cost. Each row is only charged if it yields a verified email.

## Actor input object example

```json
{
  "query": "coffee shops",
  "location": "Portland OR",
  "maxResults": 25
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "coffee shops",
    "location": "Portland OR"
};

// Run the Actor and wait for it to finish
const run = await client.actor("qualifyops/maps-leads-verified").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "query": "coffee shops",
    "location": "Portland OR",
}

# Run the Actor and wait for it to finish
run = client.actor("qualifyops/maps-leads-verified").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "coffee shops",
  "location": "Portland OR"
}' |
apify call qualifyops/maps-leads-verified --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=qualifyops/maps-leads-verified",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/MECFCzebRyaJa87T4/builds/slMbzwN52YyhLxTA3/openapi.json