Website Email & Contact Finder

Pain points

• A lead list of company websites is useless for outreach without the email.
• Emails are scattered across contact/about/team pages and often obfuscated.
• Naive scrapers return junk — template placeholders, tracking noise, franchise addresses.
• Doing it by hand across hundreds of sites is a day of copy-paste.

What we solve

• Turn any list of website URLs into contact emails, in one run.
• Crawls the homepage plus contact/about/team pages and de-obfuscates common tricks.
• Filters template junk so you don't pay for garbage, and classifies each email.
• Flags franchise/corporate addresses so you know which is the local business.

Summary

Turn a list of website URLs into contact emails. For each site the actor crawls the homepage and its contact/about/team pages, de-obfuscates the usual tricks ([at]/(dot)/HTML entities), pulls out the emails, throws away template placeholders and tracking noise, and classifies each address as generic, role, or personal. It also compares the email's domain to the site's, so a franchise/corporate address is flagged rather than passed off as the local business. Feed it a chamber list, a CRM export, a spreadsheet, or another scraper's output — platform-agnostic.

Who it's for

• B2B sales and lead-gen teams enriching a list of company websites
• Agencies preparing outreach lists
• Recruiters and researchers who have URLs but need contacts
• Anyone with a spreadsheet of websites and no emails

How to use

Set the input, run the actor, and collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API). Example input:

{
  "urls": [
    "https://basecamp.com",
    "https://www.gitlab.com"
  ],
  "maxPagesPerSite": 6
}

See Inputs below for every available field.

What you get

One row per record:

Field	Description
website	The site crawled (after redirects)
emails	Emails found: {email, source_url, type (generic/role/personal), confidence (high/medium)}
email_domain_matches_website	False = a franchise/corporate email, not this site's business
status	found
source_url	The input website

Sample:

{
  "website": "https://acme-consulting.com",
  "emails": [
    {
      "email": "info@acme-consulting.com",
      "source_url": "https://acme-consulting.com/contact",
      "type": "generic",
      "confidence": "high"
    },
    {
      "email": "jane@acme-consulting.com",
      "source_url": "https://acme-consulting.com/team",
      "type": "personal",
      "confidence": "high"
    }
  ],
  "email_domain_matches_website": true,
  "status": "found",
  "source_url": "https://acme-consulting.com"
}

Inputs

Field	Required	Type	Default	Description
urls	no	array	["https://www.apify.com"]	The websites to crawl for contact emails, e.g. ['https://acmeplumbing.com']. A bare domain is fine — 'http://' is assumed.
startUrls	no	array	[]	Standard Apify URL list — an alternative to 'urls' (e.g. from a linked dataset or Google Sheet).
maxPagesPerSite	no	integer	6	How many pages to crawl per site (homepage plus contact/about/team pages). More pages = higher hit rate, more compute.
proxyConfiguration	no	object	{"useApifyProxy": false}	Optional. Enable a proxy (e.g. residential) if target sites block the datacenter IP.

Pricing (Pay Per Event)

You pay per result (contact-found) — no charge for empty runs. Example: 200 websites with an email at $0.005/result ≈ $1.00.

One charge per website that yields at least one real email — sites with no email (or that are unreachable) are free. Illustrative — the final per-site price is set at publish time. Apify platform compute is billed separately per your plan.

Use cases

• Lead enrichment — turn a list of company websites into contactable emails.
• Chamber/directory follow-up — feed member sites, get outreach emails.
• CRM hygiene — backfill missing contact emails for accounts you already track.
• Prospecting — extract role and personal contacts from a target account list.

Why this actor

• Platform-agnostic — any list of URLs from anywhere, one clean run.
• No garbage — template placeholders and tracking noise filtered out before you pay.
• Franchise-aware — off-domain corporate addresses are flagged, not passed off as the local business.

Limitations & updates

Extracts emails published on a website's own public pages (homepage + contact/about/team). It does not brute-force or guess addresses, verify deliverability, or crawl login-walled platforms like Facebook/Instagram. Hit rate depends on whether the business lists an email at all (~50-65% of typical small-business sites).

FAQ

What do I give it?

A list of website URLs (urls), or a standard Apify start-URL list. A bare domain is fine — 'http://' is assumed.

How many pages does it crawl per site?

The homepage plus its contact/about/team pages, up to maxPagesPerSite (default 6). More pages = higher hit rate, more compute.

How am I charged?

One charge per website that yields at least one real email. Sites with no email — or that are unreachable — are free.

What's the franchise flag?

If the only email found is on a different domain than the site (e.g. a corporate customercare@brand.com on a franchisee's page), email_domain_matches_website is false so you can tell it apart from the local business.

Does it work on Facebook/Instagram pages?

No — social platforms wall their content behind login/JS challenges. Give it real business websites; social profile URLs are not an email source.

Which actor to choose

Pairs with the chamber directory scraper:

• Website Email & Contact Finder (this actor) — You already have a list of business websites and just want the contact emails.
• Chamber of Commerce Member Directory & Business Leads Scraper — You want the businesses too — every member of a local chamber, with website and email.

Guides & use cases

Written up on scrapebench.dev — the bench that runs and verifies this actor against the live source every night:

• How-to: How to run Website Email & Contact Finder
• Use case: Find contact emails for a list of company websites

More actors, coverage and nightly verification results: scrapebench.dev