When you find multiple email addresses per business, the best one to use is usually the address on the business's own website domain that is closest to the person who makes the buying decision: a named owner or manager first, then the role inbox that matches your purpose (sales@ for a partnership pitch, info@ for a general enquiry), and never an address on an unrelated domain. Keep the others as ranked backups rather than mailing all of them at once, and verify every one before it goes into a sequence.
That is the short answer. The longer one matters because the choice is rarely obvious from the spreadsheet. Enrich a few thousand business websites and a large share of rows come back with two, three or more addresses: an info@, a bookings@, a person's first name, something on a Gmail account, and occasionally an address that belongs to the agency that built the site. This guide explains where those addresses come from, how to decide which business email to use, and a repeatable ranking you can apply to a whole list in an afternoon.
Why there are multiple email addresses per business
A business website is not a contact database. It is a set of pages written by different people at different times, and every one of them can publish an address. When a crawler reads those pages, it finds all of them. The common sources are:
- Role inboxes. info@, hello@, office@, bookings@, reservations@, sales@, support@, accounts@. Each was set up for a job, and each is read by whoever does that job — sometimes one person, sometimes nobody.
- Named staff. The owner on the About page, a practice manager on the Team page, an events coordinator on a venue's private-hire page. These are usually the most valuable addresses on the site and the ones with the most compliance weight (more on that below).
- Other departments. Careers, press, accounts payable, complaints. Real addresses, wrong audience for almost any outreach.
- The web developer or agency. A footer credit with a contact link, a "site by" address, or a support address left in a template. It sits on the business's website but it is not the business.
- Other branches. A group with several locations often lists every branch's inbox on one contact page, so the row for one location carries the addresses of all of them.
- Old addresses. A footer or a PDF menu still showing an address from before a rebrand, a domain change or a staff change.
- Third-party platforms. A booking system, an online ordering service or a marketplace profile embedded in the site, each with its own domain and its own support address.
None of this is a data quality problem in the usual sense. Every address was genuinely published. The job is deciding which of them is the right contact email for what you want to say.
What the Email & Contact Scraper actually gives you
The Email & Contact Scraper visits each website you submit and returns what the business publishes there. For email, the output has three numbered columns, email_1, email_2 and email_3, plus all_emails, which holds the full collection of addresses found on the site. Alongside them you get phone_1 to phone_3 and all_phones, the contact_page URL, social profile links (facebook, twitter, instagram, youtube, linkedin), and context columns such as org_link, domain_status, website_title and website_description.
If you started from a place list, the usual route is to run the Google Maps Data Scraper with email enrichment added, so those columns are appended to the same export next to business_name, business_domain, business_phone, category and google_id. That combination is what makes ranking possible: you can compare each address against the domain the business itself lists on Maps.
Two practical points before ranking. First, treat all_emails as the source of truth and the numbered columns as a convenient view; when a site publishes more than three addresses, the extras live only in the full list. Second, the numbered order reflects where addresses were found, not which is best. email_1 is not automatically the one to use.
How to choose the right contact email for your purpose
"Best" depends on what you are sending. A pitch for bookkeeping software should reach the owner or whoever handles accounts. A partnership proposal for a venue might belong with events@. A request to update a directory listing is fine going to info@. Decide the purpose first, then apply these tests in order.
1. Match the address domain to the website domain
This is the single most useful filter. An address at @smithdental.com on smithdental.com belongs to the practice. An address at @pixelstudio.io on the same site almost certainly belongs to whoever built it. Compare the part after the @ with business_domain (or org_link) and you separate the business's own addresses from everyone else's in one step. Watch for legitimate near-misses: a business on smithdental.co.uk with addresses at smithdental.com, or a group domain shared by all branches. Treat those as matches after a quick look.
2. Drop addresses on unrelated domains
Anything on a domain that is neither the business's own nor a free mailbox provider is usually a third party: the web agency, a booking platform's support desk, a hosting company, a marketing tool. Remove those from the outreach candidates entirely. Emailing a web developer about a dental practice's patient software does not reach the dentist, and it irritates someone who never asked to hear from you.
3. Handle free mailbox addresses on their merits
A Gmail, Outlook or Yahoo address on a business website is common among sole traders and very small firms, and it is often the owner's own inbox. If it is the only address on the site, or it sits next to the owner's name on the contact page, it is a strong candidate. If the business also has addresses on its own domain, prefer those and keep the free-mailbox address as a backup.
4. Prefer what the contact page publishes
The contact_page column gives you the URL of the page the business chose as its front door. An address published there is one the business expects strangers to use; an address that only appears in a footer, a careers page or an old blog post is less likely to be monitored for new enquiries. When two candidates tie, open the contact page and see which one is on it.
5. Choose named person or role inbox by business size
In a business with one location and a handful of staff, info@ very often is the owner. There is no receptionist triaging it; the person reading it is the person who decides. In a larger organisation, a role inbox is a queue managed by someone whose job is to filter out messages like yours, and a named manager will get a relevant pitch much further. Use the size signals you already have: total_reviews, the number of locations sharing a domain, and whether the site has a Team page. A rule of thumb that works: under ten staff, a well-matched role inbox is fine; above that, look for a name.
6. Match the role to the message
Once you are among the business's own addresses, pick the inbox whose job fits what you are saying. bookings@ and reservations@ are read by people handling customers right now; a sales pitch there gets deleted or forwarded with a sigh. support@ belongs to the customers of the business, not to vendors. careers@, press@ and accounts@ are almost never right for outreach. sales@, hello@, info@, office@ and named addresses are where commercial messages land best.
A simple ranking rubric for business email addresses
To apply all of that across a list rather than row by row, give each address a score. The points below are deliberately simple; the order they create matters more than the numbers.
| Signal | Points | Why it matters |
|---|---|---|
| Domain matches the business website | +5 | It belongs to the business, not a third party |
| Looks like a named person (first name, first.last, initials) | +3 | Reaches a human, often a decision-maker |
| Commercial role inbox (sales@, hello@, info@, office@) | +2 | Monitored for new enquiries |
| Free mailbox provider and no own-domain address exists | +2 | Often the owner's personal business inbox |
| Published on the contact page | +1 | The business's chosen front door |
| Operational inbox (bookings@, reservations@, support@) | -2 | Read by staff serving customers, not buying |
| Wrong department (careers@, press@, accounts@, noreply@) | -4 | Wrong audience for outreach |
| Unrelated domain (agency, platform, host) | Exclude | Not the business at all |
Here is how it plays out on an illustrative row. Say a physiotherapy clinic on coastphysio.com returns four addresses in all_emails: info@coastphysio.com, sarah@coastphysio.com, bookings@coastphysio.com and hello@brightweb.agency. The agency address is excluded. Sarah scores 8 (domain match plus named person), info@ scores 7 or 8 depending on whether it is on the contact page, and bookings@ scores 3. Your primary is Sarah, your first backup is info@, and bookings@ is a last resort you will probably never use.
Most of the rubric is a few string checks, so it scales. Split each address at the @, compare the domain with the cleaned website domain, test the local part against a short list of role words, and look for name patterns. Anything the rules cannot classify goes to a small manual-review pile, which on a typical list is a few percent of rows.
How to rank addresses and keep backups: step by step
- Enrich the list. Run your domains through the Email & Contact Scraper, or add email enrichment to a Maps run so contacts land next to the listing data.
- Explode
all_emails. Turn each row into one row per address, carrying the business'sgoogle_id(or domain, if you started from a website list),business_domainandcontact_pagewith it. - Normalise. Lowercase every address, trim stray spaces and trailing punctuation, and drop exact duplicates within a business.
- Classify the domain. Mark each address as own-domain, free mailbox or unrelated. Exclude unrelated domains.
- Classify the local part. Tag named person, commercial role, operational role or wrong department.
- Score and sort. Apply the rubric, sort each business's addresses by score, and write the top three back as
primary_email,backup_email_1andbackup_email_2in your own working columns. - Deduplicate across the list. Make sure no address appears as the primary for more than one business (see the next section).
- Verify everything you might send to. Primary and backups, not just the primary.
- Send to one address per business. Move to the backup only after a hard bounce or a clear signal the primary is wrong — never all at once.
Deduplicate across a chain or group
Multi-location businesses create a specific mess. A dental group with eight practices often runs one website, so all eight Maps listings point at the same domain and all eight rows come back with the same set of addresses. Mail each row independently and the group's head office receives eight near-identical emails in a morning.
Group rows by domain before you send. If a domain appears on several listings, decide whether you are selling to the group or to each branch. For a group-level offer, keep one row, use the head-office or named-manager address, and attach the branch count as context. For a branch-level offer, look in all_emails for branch-specific inboxes (addresses containing a town or street name are common) and assign each one to its location; branches without their own inbox share the group address and should be contacted once, not eight times. Our guide to finding multi-location businesses on Google Maps covers how to spot these groups in the first place, and the same domain-grouping step is in the guide to cleaning and deduplicating Google Maps data.
Verify every address before you send
An address that was published on a website is not proof that the mailbox accepts mail today. Staff leave, domains get migrated, and footer addresses outlive the inbox behind them. Sending to a dead address costs you a bounce, and bounces are read by mailbox providers as a sign you do not know who you are writing to; the damage lands on your sending domain.
Run your primaries and backups through the Email Address Verifier immediately before the campaign. It checks each address at the receiving mail server and returns a status with a status_details explanation, plus flags including catch_all and role_account. A few things to know when reading it:
- Read status with status_details. An
unknownstatus often means a mail server that refuses to confirm either way, and discarding those would throw away addresses that work. - Catch-all domains cannot confirm one mailbox. If the domain accepts everything, a named address may look fine and still go nowhere. Prefer the role inbox you can see on the contact page when a domain is catch-all.
- Verification is a snapshot. Verify close to the send date. A list checked three months ago is a list you have not checked.
If your enrichment comes back with no address at all for some businesses, that is a separate problem with its own fixes; see how to find businesses missing email addresses on Google Maps.
info@ vs personal email: compliance differences
This is not legal advice, and the rules depend on where you and your recipients are. But the info@ vs personal email question has a compliance dimension you should factor into ranking, not bolt on afterwards.
Under GDPR and similar laws, an address that identifies a person, such as sarah@coastphysio.com, is personal data even though it is a work address published on a business website. Using it for marketing needs a lawful basis (for business-to-business outreach this is commonly legitimate interests, backed by a documented assessment), a clear explanation of where you got it, and an easy way to opt out. In some countries, electronic marketing rules add further restrictions on emailing individuals without consent. A generic role inbox like info@ is generally treated as less personal, but in a one-person business it may still identify the owner.
Practical habits that keep you on the right side of this:
- Record the source page and date for every address you use, so you can answer "where did you get my email?"
- Keep messages relevant to the business's role. A pitch to a practice manager about practice software is defensible; mass promotional mail to named staff is not.
- Honour opt-outs across every address you hold for that business, not just the one that replied.
- In stricter jurisdictions, lean towards role inboxes for first contact and let the business route you to a person.
- Respect each site's terms and any instruction the business publishes about unsolicited contact.
For a deeper look at the legal side of collecting the data in the first place, read our practical compliance guide to scraping Google Maps.
Putting it to work in a cold email campaign
Say you pull 3,000 independent physiotherapy clinics across three regions and enrich them. An illustrative outcome: around 2,400 rows return at least one address, and roughly half of those have more than one. After excluding unrelated domains, grouping 150 rows that share a domain with another listing, and ranking, you end up with one primary per business and a backup for most of the multi-address rows. Verification then removes the dead primaries, and the backups fill many of those gaps without another round of research.
The ranking also improves the message itself. Knowing you are writing to a named clinic owner rather than a bookings inbox changes the opener, the length and the ask. The guide to building cold email campaigns with Google Maps data covers segmentation, personalisation from listing fields and sequencing once your contact column is clean.
Whatever you send, keep the backups out of the sequence. Emailing info@ and sarah@ at the same business on the same day is the fastest way to look like a bulk sender, because that is what it is.
Conclusion
Multiple email addresses per business are normal, and the right one is rarely just the first column. Filter to the business's own domain, drop third-party addresses, pick a named decision-maker or the role inbox that fits your purpose, and remember that in a small business info@ is often the owner. Score every address, keep two backups, collapse chains to one conversation, and verify the whole set before you send. Start by enriching your list with the Email & Contact Scraper — the first 500 contacts are free on a new account — and apply the rubric to what comes back.
Related reading: How to Collect Verified Contact Information for Local Businesses, How to Build Better Cold Email Campaigns Using Google Maps Data, How to Extract Emails from Websites?.
Frequently asked questions
Why does one business have multiple email addresses?
Websites publish role inboxes like info@ and bookings@, named staff, department addresses, branch inboxes, old footer addresses and sometimes the web agency's or a booking platform's address. A crawler finds all of them.
Which business email should I use for outreach?
Use an address on the business's own website domain that is closest to the decision-maker: a named owner or manager first, then the role inbox that fits your purpose. Exclude addresses on unrelated domains.
Is info@ or a personal email better?
In a small business info@ is often read by the owner and works well. In larger organisations a named manager usually gets further, but personal addresses carry more data protection weight, so check your lawful basis. This is not legal advice.
Which columns hold the emails in the Email & Contact Scraper output?
email_1, email_2 and email_3 hold individual addresses, and all_emails holds the full list found on the site. The output also includes phones, contact_page and social profile links.
Should I email every address I find for a business?
No. Send to one primary address per business and keep the others as ranked backups, used only after a bounce or a clear sign the primary is wrong. Mailing several inboxes at once looks like bulk sending.
Do I need to verify all the addresses or just the primary?
Verify the primary and the backups immediately before sending. The Email Address Verifier checks each address at the mail server and returns a status, status details and flags such as catch_all and role_account.