Google Maps Email Extractor – Every Address Verified

Search a category and a city, and get back businesses whose email address has actually been checked — not guessed, not scraped and hoped for.

For each business found on the map, this Actor opens the business's own website, reads the email addresses published there, and then holds a real SMTP conversation with each mailbox's mail server before the row is delivered. Addresses the server rejects never reach you.

What you pay for — and why it is cheaper than it looks

One charge per lead delivered, and a lead is only delivered when its address passed. Everything else is free:

Outcome	Delivered?	Charged?
Address confirmed by the mail server	yes	yes
Business has no website	no	no
Website published no address	no	no
Every address found was rejected	no	no
Business asked us to remove it	no	no

So a run over 500 businesses that yields 90 checked addresses costs you 90 rows, not 500.

That is the whole difference. The usual model on this platform bills you per business read — then adds a charge for finding the contact details, and another for verifying the address, and in at least one popular case a further charge for every filter you apply. You pay for the businesses that had no address, and for the ones whose address turned out to be dead.

Here you do not. Filters are free, misses are free, and unverifiable addresses are free. You are charged once for a lead you can actually write to.

An unchecked list is also cheap to produce and expensive to send to: the bounces are charged against your sending reputation, not ours.

Why the checking is real

Most scrapers cannot do this. Asking a mail server whether a mailbox exists needs outbound port 25, which this platform blocks — so an Actor with no machine of its own can only check spelling and whether the domain has a mail server at all. This one runs the mailbox conversation on Locomint's own server, which is why a verdict here means the server answered.

If that server is ever unreachable, the run says so in the log in plain words and falls back to domain-level checks — and with the default setting you then get no rows, rather than unchecked addresses quietly sold as checked.

Input

Field	What it does
searchStringsArray	Categories to search, one per line, as you would type them into a map
locationQuery	City and country — "Porto, Portugal", not "Porto"
maxCrawledPlacesPerSearch	How many businesses to read, not how many rows you get
deliver	verified (default), verified_and_risky, or any
maxEmailsPerPlace	How many addresses to test per business (default 3)
websiteFilter	Skips businesses with no website by default — they cannot yield an address
includeDetails	Off by default; adds opening hours and photos at ~20% more run time

placeMinimumStars, skipClosedPlaces and categoryFilterWords are free filters applied to the search result before anything is fetched, so anything they exclude costs nothing.

What the verdicts mean

• deliverable — the mail server was asked about this exact mailbox and said yes. This is what verified delivers, and the only status that means the mailbox itself was tested.
• risky — a catch-all domain: the server accepts every address, so nobody can prove this one either way. Held back by default; ask for verified_and_risky if you want them.
• valid — syntax and a real mail server on the domain, and nothing more. It is not a mailbox check, so it is never delivered as verified.
• undeliverable / invalid / disposable / unknown — only delivered if you ask for any, and then charged.

Output

One row per business: name, address, phone in E.164, website, rating, review count, category and coordinates — plus email, email_status, email_score, email_is_named (true when the delivered address names a member of staff, false for a company mailbox), the mail server that answered, and emails_verified, which lists every address tested on that site with its own verdict, so you can see what was rejected rather than wonder where it went. The row also carries named_emails and named_profiles: every named address and personal profile link found on the site.

Opening hours, photos and the description need a second fetch per business and are off by default, because a lead row does not use them and they cost you run time for every business looked at, not just the ones that become leads. Turn on includeDetails if you want them.

Limits, stated plainly

• Addresses the business publishes on its own site. Company mailboxes such as info@ and bookings@ come first, often with a business's own generic mailbox on a free provider. Addresses that name a member of staff are tested too, and the lead's email is the address with the strongest verdict among those tested, which can be a named one; email_is_named says which it is. A named address on another company's domain, such as the web designer credited in the footer, is never returned.
• Expect far fewer rows than businesses read, and budget for that. Most small businesses publish no address on their site at all. Measured on a real run — dentists in Porto, 12 businesses read — one produced a confirmed address. One in eight is a fair expectation for a tight local category; a category where businesses are more web-native does better. You are charged per lead precisely because of this ratio, so the misses cost you nothing.
• Only pages the business publishes. No logins, no accounts, no pages behind a challenge. A site that blocks us is skipped, not worked around.
• Verification is a point in time. A mailbox that answered today can be closed tomorrow. email_checked_at records when the server answered.
• A catch-all cannot be resolved. No verifier can, including the ones that claim otherwise.

Sending to these addresses

These are addresses the business chose to publish on its own website. A named work address is personal data in the EU and the UK. Whether you may write to any of them, and to a named person in particular, is your responsibility and depends on where you and they are: GDPR, PECR, CAN-SPAM and their local equivalents all apply to you, not to the data. Nothing here is consent to be contacted.

Data removal

A business that wants its details left out of future runs, or a person who wants their own address or profile link left out, can write to info@locomint.io. A suppressed business is dropped from every run before anything is delivered or charged, a suppressed address or profile link is removed from every row, and removals are honoured in every Locomint listing.

Questions and bug reports belong in the Issues tab of this Actor.