Use Email Scraper
Maxime Dupré
Scrape email addresses from two submitted public website seeds and linked pages on the same sites. Save up to 20 accepted, normalized email rows, one per unique address, with the first source page URL and submitted seed URL. The Actor can also include public phone numbers and social profile links when available. Only accepted rows are charged.
Input
Output fields
Sign up on Apify or log in
The Website Email & Contact Scraper Actor is ready to run with the inputs already set for "Use Email Scraper". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Use Email Scraper" task
The Website Email & Contact Scraper Actor will start running based on the input automatically. You can also change all the input fields, like website urls and maximum emails, to match your specific use case.
Receive the "Use Email Scraper" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as email address, source url, seed url, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Use Email Scraper" task via API.

The Use Email Scraper task checks the public pages of each submitted website and the pages they link to. You can replace the example URL with your own website. It saves only public emails it finds.
The Use Email Scraper task returns one row for each unique, normalized email, with the page where it was first found, the page title, and the submitted seed URL.
The Use Email Scraper task checks www.w3.org and www.ietf.org and linked pages on the same sites. You can change these URLs before you run it.
The Use Email Scraper task saves up to 20 emails for the whole run. You can raise the limit, or leave it empty or use 0 to return all available results.
The Use Email Scraper task uses pay-per-event pricing. It charges one event for each accepted, unique email saved to the dataset. The mail server check is off, so no domain check events are added.
The Use Email Scraper task can add public phone or fax numbers found on the source page in E.164 format, with phone checks, when available. Rows from the same page share the same phone list.
The Use Email Scraper task can run through the Apify API. You can read its default dataset with the API or export it from the Apify Console.
The Use Email Scraper task can run on an Apify schedule like other Actor tasks. Each run checks the same websites again and saves each unique email once in that run.
The Use Email Scraper task does not verify mailbox delivery. You can turn on Check mail servers to see if MX records exist for each email domain. Each check has a small extra charge.
The Use Email Scraper task saves only the first match of a normalized email. Later matches do not create another row or charge.