Turn URL lists into contact-email rows without manual digging

✉️ Website Emails Scraper shallow-crawls each site, filters false positives, and returns one row per unique email tied back to the source URL.

Fastest way to try it

Submit 3 to 5 seed URLs, leave proxy settings on the default, and inspect the first output rows in the Output tab before scaling up to a larger list.

Why people use it

• 📬 Start from a curated list of websites instead of hunting through contact pages by hand.
• ✉️ Get one deduplicated email row per source URL, which keeps CRM syncs, QA, and audits simpler.
• 🌐 Search the seed page plus a limited set of internal pages instead of trying to spider an entire site.
• ⏭️ Skip duplicate seed URLs and dead-end HTTP pages like 403 and 404 before they turn into noisy output.
• 🌐 Keep the default Apify proxy setup or switch to direct mode when you explicitly pass null.

How to use in 3 simple steps

1. Open the Input tab and paste a small list of seed URLs to test, for example 3 to 5 websites.
2. Leave proxy settings on the default unless you have a reason to change them.
3. Run the actor, then use the Output tab or API to collect one row per discovered email.

Inputs, defaults, and behavior

• 🌐 urls is required. Every urls[*].url is validated before the crawl starts.
• 🔢 Start with 3 to 5 seed URLs on the first run so you can verify the emitted rows quickly.
• ⏭️ Duplicate input URLs are normalized and deduplicated, so the same site is not crawled twice.
• 🌐 The actor shallow-crawls each seed URL plus a limited set of internal pages instead of trying to spider the whole site.
• ✉️ Each output row includes url, seedUrl, and email, so every email stays tied to the source website.
• 🔁 Extracted emails are lowercased and deduplicated per source URL.
• 🫥 The scan ignores scripts, styles, templates, and other non-user-visible page content before searching for emails.
• ⚠️ 403 and 404 pages are skipped for extraction purposes instead of polluting the dataset with dead-end rows.
• 🌐 Supports Apify proxy configuration, including direct mode when you explicitly pass null.
• Top-level concurrency is tuned internally for reliability and cost control, so there is no public concurrency input to manage.

Input example

{
  "urls": [
    { "url": "https://acme.dev" },
    { "url": "https://beta.example" },
    { "url": "https://gamma.test" }
  ]
}

Input screenshot

What data can Website Emails Scraper extract?

See the full Output tab for the complete schema.

Field	What you get	Why it matters
seedUrl	The input URL whose crawl produced the row	Trace every email back to the original seed
email	One discovered email address	Use each row directly in enrichment or contact workflows
url	The same source URL kept for backward compatibility	Keep older consumers working while preserving source context

Output example

[
  {
    "url": "https://acme.dev/",
    "seedUrl": "https://acme.dev/",
    "email": "hello@acme.dev"
  },
  {
    "url": "https://acme.dev/",
    "seedUrl": "https://acme.dev/",
    "email": "sales@acme.dev"
  }
]

Output screenshot

How much does website email scraping cost?

This actor is billed per emitted email row, not per input URL. At the current repo-configured rate, 10 emitted emails is about $0.05 and 100 emitted emails is about $0.50. If you submit 20 sites and only 8 unique emails are found, you are billed only for the 8 result rows that were pushed to the dataset. A small curated URL list is the easiest first run, and the live Pricing tab is the source of truth for the current per-email rate.

Billed item	When it triggers	Repo-configured price
Email result	When one discovered email row is pushed to the dataset	$0.005

Why run Website Emails Scraper on Apify?

• Run it from the Console or call it from the Apify API when email discovery is one step inside a larger pipeline.
• Schedule repeat runs for saved URL lists instead of checking the same sites manually.
• Keep datasets and run logs together when you want to inspect which sites produced emails and which ones failed.
• Connect finished runs to webhooks, integrations, or downstream jobs without building a separate execution layer.

FAQ

What does "shallow crawl" mean here?

The actor checks the seed URL and a limited set of internal pages. It is meant to find contact emails without crawling an entire site tree.

Why do I get multiple rows for one URL?

The actor emits one row per unique email found for that source URL.

What happens when a site returns 403 or 404?

Those pages are skipped for extraction purposes. The actor does not emit dataset rows for them and continues with the rest of the run.

Can I submit the same URL twice?

Yes, but duplicates are normalized and deduplicated before crawling, so the same site is only checked once.

What should I try if emails are missing or a run fails?

First verify that the seed URL resolves, that the actor can find the email on the seed page or a limited set of internal pages, and that the site is not only exposing the email in blocked or non-user-visible content. Re-test with 3 to 5 seed URLs, then check the run log before opening an issue.

Where do I report a missed email pattern or site-specific failure?

Open the Issues page with the seed URL, the page where the email appears, and the output you expected. I use that queue for fixes and feature requests.

Explore the rest of the collection

• Product Hunt Scraper - daily Product Hunt leaderboard scraping with cache and live-crawl options, maker links, and optional email enrichment
• Uneed Scraper - daily Uneed ladder scraping with promoted-listing filtering, maker links, and optional email enrichment
• TinySeed Scraper - TinySeed portfolio scraping with company descriptions and optional website emails
• Tiny Startups Scraper - Tiny Startups homepage scraping with promoted-card filtering and email enrichment

Missing a feature or data?

Create a ticket and I'll add it within 24h.