An email column can look complete while answering very little. Where was the address found? Does it belong to this business? Is it intended for general enquiries or bookings? Has anyone checked whether it can receive mail?
These are separate questions. Discovering an address on a website establishes a source observation. It does not establish mailbox deliverability, the owner's identity, or whether that channel fits your task.
For a team researching local restaurant businesses, the useful handoff is a contact worksheet with evidence and review decisions. This guide explains how G Maps Crawl finds available email addresses, which fields preserve their context, and how to evaluate the result before moving it into another workflow.
The email usually comes from the business website
Google Maps listing data supplies details such as a business name, phone number, address, and website. Email enrichment is a separate step. When enrichment runs, G Maps Crawl visits the listed website and a limited set of likely contact pages to discover available business emails and social links.
That is why an email returned with a Google Maps business record should not automatically be described as an email published on Google Maps. The website page is the relevant source, and its context matters.
An address on a restaurant's contact page may be a general enquiries inbox. An address elsewhere on that site might be reserved for event bookings, careers, or a supplier. A number of addresses in one record is not a number of decision-makers reached.
Keep the source evidence with each contact instead of reducing everything to an email cell. The business-field guide explains the structured fields used for these findings.
Request enrichment deliberately
For the Search API and MCP server, extra defaults to false. Set extra: true when the task requires available emails and social links. This requests enrichment; it cannot guarantee that a website publishes an address or can be read successfully.
The synchronous search returns up to 20 businesses per page. Each successfully completed live search page uses one API request unit, including an empty page. Accepted work reserves a unit; failed searches release the reservation. Test responses use zero units, and enabling extra does not change the one-unit live page cost. Enrichment can take longer. A changed request needs a new request identifier; a retry of the identical request reuses its original identifier.
If you first collected listings without enrichment, a later enriched search is additional work. Match the returned businesses by their identifiers rather than assuming the same business occupies the same position in both responses.
The Online scraper includes contact enrichment on eligible paid Online plans. Its exports and allowances are separate from the API product. Review the available fields and your plan before choosing a collection workflow.
Read contact evidence, not just the email array
The convenient place.emails array gives you discovered addresses. The richer place.contacts entries preserve the contact value, its sourceUrl, its original observedAt, and a method describing the source path. Keep those fields when preparing a review worksheet.
Also retain place.contactsCheckedAt, place.enrichmentState, and relevant place.fieldStates. They help explain whether enrichment produced a finding, found nothing, failed, or was not completed. They are collection states, not email-deliverability verdicts.
This abridged contact is fictional. The reserved example domain and timestamp placeholder demonstrate the fields; this is not a live result or a complete response object.
{
"kind": "email",
"value": "[email protected]",
"sourceUrl": "https://restaurant-a.example/contact",
"observedAt": "<original observation timestamp>",
"method": "website"
}
One business may have several contact entries. The same address may also appear for several branches. Preserve the relationship between contact and location rather than merging distinct businesses merely because they share an inbox.
Interpret an empty email field correctly
An empty array can mean different things. If enrichment is pending, you do not yet have a completed contact check. If it failed, the site could not be read successfully. If it is not applicable, the record may lack a website to inspect.
When enrichmentState is returned, inspect the actual contact kinds. A returned social link does not mean an email address was found. When no contact is found, that describes the pages checked, not every possible public source for the business.
Use the individual email field state alongside the overall enrichment state. This prevents the common mistake of combining “not requested,” “not found,” and “failed” into one misleading zero-coverage number.
If the business is important to your task, inspect its official website manually and record what you find. Do not fill the blank by guessing an email pattern from a person's name or a domain.
Review each address through four questions
Is it still published? Open the contact's source page and check whether the address remains visible in the relevant context. Record your review date separately. A missing page or changed address is a reason to hold the old value for review.
Does the source match the business? Compare the website, name, phone, location, and contact context. A site may mention a partner or outside booking provider. An address using a different domain can still be legitimate, but it needs relationship evidence rather than an automatic assumption either way.
What is this channel for? Preserve labels such as general enquiries, bookings, press, or careers when the source provides them. A generic inbox can be the right business contact. A named address should not be labeled “owner” unless the evidence establishes that role.
What technical checks have actually happened? Syntax checks, domain checks, and mailbox-deliverability checks answer different questions. G Maps Crawl's source extraction does not certify deliverability. If another tool performs verification, store its result, provider, and check date separately from the extraction evidence.
Build a worksheet someone else can review
Use one row per business-contact relationship. Include the business identifier, Maps URL, address value, source page, source observation date, collection state, manual review date, channel context, and review decision.
The following rows and findings are fictional. They illustrate a quality review, not live results or tested mailbox outcomes.
| Illustrative finding | Source context | Decision |
|---|---|---|
| [email protected] | Matching restaurant contact page labels it general enquiries. | Source and business relationship checked; deliverability remains unchecked. |
| [email protected] | Matching restaurant page labels it private event bookings. | Preserve the channel label; review whether it fits the intended task. |
| Contact previously returned; source page now unavailable | Current publication could not be confirmed. | Hold pending another check; do not count as currently verified. |
Use specific decisions such as “source checked,” “relationship unresolved,” or “verification pending.” A single “verified” flag hides which question was answered and makes later handoffs harder to trust.
Report quality with dates and denominators
Summarize how many distinct businesses were collected, how many had enrichment completed, how many returned at least one email, and how many source pages your team reviewed. Keep failed and pending checks visible. Count distinct addresses separately from businesses, because a shared branch inbox can otherwise inflate the apparent reach.
Website contacts have a separate seven-day freshness budget. Complete Maps details can be reused for up to 730 days, while query responses normally remain cached for 24 hours. Those windows describe data reuse; they do not guarantee a mailbox is active or every observation was made today.
Preserve each contact's original timestamp even when you receive it in a later search. If a reviewer confirms publication again, add that review date without rewriting the original source observation.
The finished worksheet should let a teammate follow an address back to its business and page, understand what was checked, and see the remaining question. Inspect a structured sample before choosing which contact fields to preserve in your next export or API workflow.
