Website Contacts Scraper — Emails, Phones, Social Profiles

Turn a list of domains into contactable rows. Paste stripe.com, https://example.com or a thousand domains from your CRM and get emails, phone numbers and social profiles — read from the homepage and from the site's own Contact, About, Team and Impressum pages — as JSON, CSV or Excel, or through the API.

No login, no proxy, no API key: the Actor opens the same public pages a visitor would.

Why this Actor

• Contacts, not raw HTML. Emails, phones and the company's own social profiles, deduplicated across the homepage and the pages where contacts actually live.
• Noise filtered by design. no-reply@, Sentry and Mailchimp addresses, and documentation placeholders like info@domain.com are dropped — a list you can mail merge, not one you have to clean.
• Share buttons are not profiles. A Facebook sharer link or a tweet-this URL never ends up in the facebook or twitter field.
• Forgiving input. Domains or URLs, with automatic www/non-www and https→http fallback, so a stale CRM export still returns rows.

Sample output

One item of the dataset (long values shortened):

{
  "website": "https://shopify.com/",
  "title": "Shopify: The All-in-One Commerce Platform for Businesses - Shopify",
  "emails": [],
  "phones": [],
  "linkedin": "https://www.linkedin.com/company/shopify",
  "twitter": "https://twitter.com/shopify",
  "facebook": "https://www.facebook.com/shopify",
  "status": 200
}

What you get

• Emails from mailto: links, page text and bracketed obfuscation like name (at) domain (dot) com
• Phone numbers from tel: links and international formats
• LinkedIn, X/Twitter, Facebook, Instagram, YouTube, TikTok, GitHub, Telegram, Discord and Pinterest profiles — the company's own, not share buttons
• Page title and meta description, so a row is usable as a lead record on its own
• Automatic www/non-www and https→http fallback, so a typo or a missing redirect does not lose a site
• Monitored daily

Input

• Websites — domains or URLs, one per line.
• Contact pages per site — how many internal Contact/About/Team/Impressum pages to open after the homepage (0 = homepage only).
• Timeout per page, Websites in parallel.

Limits and notes

• Noise is filtered out on purpose: no-reply@, platform addresses (Sentry, Mailchimp, Shopify…) and documentation placeholders (info@domain.com, youremail@example.com) never reach the dataset. That is why a site can come back with zero emails while its HTML technically contains an address.
• Contacts hidden behind a form, a JavaScript widget or an image are not extracted — the Actor reads HTML, it does not run a browser or OCR.
• Large enterprise sites often publish no address at all; small and mid-sized businesses are where the hit rate is high.
• Every site is charged once, whether or not something was found. Runs that return no rows at all cost nothing.

Input example

{
  "websites": [
    "apify.com",
    "stripe.com",
    "chorelet.app"
  ],
  "maxContactPages": 3,
  "requestTimeoutSecs": 20,
  "concurrency": 5
}

How much does it cost?

Pay per website — no subscription, no minimum, no charge for platform usage.

Volume	Price
1,000 websites	$2.00
10,000 websites	$20.00
100,000 websites	$200.00

The Apify free plan includes $5 of usage every month — about 2,500 websites with this Actor, no card needed. Nothing else is charged: platform usage is included in the price, and Apify Bronze, Silver and Gold subscribers get 10%, 20% and 30% off these prices.

Use it from code, n8n, Make, Zapier or an AI agent

Run the Actor and download the dataset in one call (JSON by default; add &format=csv or xlsx):

curl -X POST "https://api.apify.com/v2/acts/chorelet~website-contacts-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"websites": ["apify.com", "stripe.com", "chorelet.app"], "maxContactPages": 3, "requestTimeoutSecs": 20, "concurrency": 5}'

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("chorelet/website-contacts-scraper").call(run_input={"websites": ["apify.com", "stripe.com", "chorelet.app"], "maxContactPages": 3, "requestTimeoutSecs": 20, "concurrency": 5})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

• n8n, Make, Zapier — use the Apify node/module: run the Actor, then "get dataset items".
• Google Sheets, Slack, webhooks — add an integration on the run's Integrations tab.
• AI agents — the Actor is available as a tool through the Apify MCP server; the dataset schema describes every field for the model.
• Schedules — run it hourly, daily or weekly from the Schedules tab.

FAQ

Where does it look for contacts?

The homepage first, then up to a few internal pages whose link or path looks like Contact, About, Team, Support or Impressum. You choose how many.

Why did a site return no emails?

Either it publishes none (a contact form only), or the only addresses on it were noise — no-reply@, a platform address or a documentation placeholder — which this Actor deliberately drops.

Does it verify that the emails work?

No. It reports what the site publishes. Run the output through an email verifier if you need deliverability.

Can it read contacts rendered by JavaScript?

No — it reads HTML rather than running a browser, which is what keeps it fast and cheap. Most contact details are in the HTML; widgets and images are not.

Is this legal?

The Actor reads pages that any visitor can open and collects business contact details that companies publish on purpose. How you use them is your responsibility — in the EU and similar jurisdictions, marketing to those addresses is regulated (GDPR, ePrivacy).

Support

Questions, missing fields or a source that changed? Open an issue on the Issues tab or write to support@chorelet.app — problems are usually fixed within a day, and the Actor is checked every morning by an automated test run. If the Actor saved you time, a short review on its Store page helps other people find it.