Website Contact Extractor

Crawl seed websites and extract contact details — emails, phone numbers and social profiles (Instagram, X, LinkedIn, Facebook). Performs a light same-host crawl up to a per-domain page budget. Built for lead enrichment and outreach-list building.

What it does

Given a list of starting URLs, this Actor crawls each domain (staying on the same host) up to a page budget, scans pages for contact signals, and returns one record per domain with every email, phone number and social profile it found.

It's the enrichment step after you have a list of company sites: feed it the homepages, get back the contacts.

Features

• Seed-URL input — homepages or specific pages like /contact.
• Light same-host crawl — follows internal links up to maxPages per seed.
• Contact extraction — emails, phone numbers, and Instagram/X/LinkedIn/Facebook profiles.
• Optional proxy — enabled only if a site blocks datacenter IPs.
• Clean typed fields — base URL, host, emails, phones, and each social handle.

What people use it for

• Lead enrichment — turn a list of company sites into contact records.
• Outreach list building — collect emails and socials for sales.
• Partnership sourcing — find who to talk to at a target company.
• Directory and index building.
• Journalist and PR contact discovery.

Getting good coverage

Contact details often live on /contact, /about or the footer rather than the homepage. Pointing a seed directly at https://example.com/contact costs less crawl budget than the homepage, but a homepage seed with a reasonable maxPages will usually reach those pages too.

Data hygiene

Expect noise: some "emails" are noreply@ or role addresses, and phone formats vary by country. Design your downstream step to:

• Drop noreply/role addresses if you want humans.
• Normalise phone numbers to E.164 before dialling.
• Dedupe by host across seeds that belong to the same company.

Input

startUrls is required. maxPages sets the crawl budget per seed domain.

Field	Type	Default	What it does
startUrls (required)	array	["https://example.com"]	Seed URLs to crawl, e.g. ["https://example.com", "https://another.com/contact"].
maxPages	integer	30	Crawl budget per seed URL (same-host links only). Range 1–500.
proxyConfiguration	object	see below	Some sites block datacenter IPs. Enable Apify proxy if needed.

Input example

{
  "startUrls": [
    "https://example.com"
  ],
  "maxPages": 30
}

Output

One record per seed domain: base URL, host, emails, phones and the social profiles found.

Every dataset record contains: baseUrl, host, emails, phones, instagram, twitter, linkedin, facebook, pagesCrawled, fetchedAt.

Export the dataset as JSON, CSV, Excel, XML or JSONL from the Console, or pull it programmatically through the Apify API and any of the official clients.

How to use it

1. Click Try for free (or Start if you already have an Apify account).
2. Fill in the input fields described above — the defaults already produce a working run.
3. Press Start and watch the log; results stream into the dataset as they are found.
4. When the run finishes, open the Output/Storage tab and export as JSON, CSV or Excel.

Runs can be scheduled (hourly, daily, weekly) and wired into Slack, Google Sheets, Zapier, Make, webhooks or your own backend through Apify integrations. Everything the Console does is also available over the Apify API.

Proxy configuration

This Actor accepts a standard Apify proxy configuration object. Residential proxy is the default because the target site rate-limits datacenter IP ranges; you can select a specific exit country or supply your own proxy URLs.

{
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}

Pricing

This Actor is billed on Apify's pay-per-event model: a small charge when a run starts, plus a charge for each result written to the dataset. You only pay for records you actually receive — a run that finds nothing costs only the start event. Current rates are always shown on the Pricing tab of this page, and the run log prints your usage as it goes.

Free-plan credits from Apify cover a large amount of light usage, so you can evaluate the Actor before committing to anything.

FAQ

Do I need a proxy?

Usually not — most sites serve their own pages to any IP. Enable proxyConfiguration only if a specific site blocks datacenter IPs.

How deep does it crawl?

maxPages caps pages per seed, and it stays on the same host. It's a light contact-discovery crawl, not a full-site archive.

Can it find emails behind a form?

No — only emails present in page text or mailto: links are captured. Emails gated behind a contact form aren't extractable.

Will it respect robots.txt?

It's a focused contact crawler; if you need strict robots compliance for a given site, scope startUrls and maxPages accordingly.

Other Actors by cynix_dev

Actor	What it does
Company Tech Stack & Hiring Intelligence	Detect technologies from company websites, extract tech requirements from job postings, discover competitors.
Job Postings — ATS Boards Extractor	Pull live job postings straight from companies' public applicant-tracking boards — Greenhouse, Lever, Ashby, SmartRecruiters, and …
SEC EDGAR Filings Extractor	Search and extract SEC EDGAR filings: full-text search across all filings or company filing histories by CIK.
WHOIS & DNS Enrichment	Enrich domains with structured WHOIS data (registrar, registration/expiration dates, status, nameservers) and optional DNS …
News & Press Release Monitor	Watch company newsrooms, blogs, and press pages and get one clean record per article — with new-item detection between runs, so a …

Legal and responsible use

This Actor collects only publicly available information. You are responsible for how you use the data, including compliance with the target site's Terms of Service, robots directives, copyright, and data protection law such as GDPR and CCPA. Do not use it to gather personal data without a lawful basis.

Support and feedback

Found a bug, hit a site change, or need an extra field? Open a ticket on the Issues tab of this Actor — issues are read and fixed. Feature requests and custom-scraper enquiries are welcome through the same channel.