Contact Details Scraper — Emails, Phones & Social Links

Give it a list of websites. Get back one clean, aggregated contact profile per website: emails, phone numbers, and social profiles — each with the exact page it was found on, so you can verify every value.

Built for lead enrichment, CRM hygiene, outreach list building, and market research.

Why this scraper

Most contact scrapers charge per page crawled and flood you with junk: image filenames that look like emails, random digit strings tagged as phones, share-button links tagged as social profiles. This actor is precision-first:

• 1 result = 1 website (not 1 page). You pay for profiles, not crawl noise.
• mailto: and tel: links are trusted first; text extraction uses conservative patterns and de-obfuscation (name [at] company [dot] com → name@company.com).
• Junk filters: image/CDN filenames, placeholder domains (example.com, yourdomain.com), tracker domains never appear in output.
• Social links are canonicalized profile URLs — share/intent/login links are excluded.
• Contact-like pages (/contact, /about, /team, /imprint, /support, /legal) are crawled first, so a 15-page budget finds what a dumb 100-page crawl misses.
• Robots.txt is respected. Public pages only. No login walls, no evasion.

No browser. Pure HTTP + HTML parsing — fast and cheap to run.

Input

Field	Type	Default	Notes
startUrls	array	—	One entry per website (https:// optional).
maxPagesPerDomain	integer	15	Crawl budget per site. Contact pages are prioritized.
maxDepth	integer	2	Link depth from the start page.
proxyConfiguration	object	Apify Proxy	Recommended: automatic.

{
    "startUrls": [{ "url": "https://apify.com" }, { "url": "acme-industrial.com" }],
    "maxPagesPerDomain": 15
}

Output schema

One dataset item per website:

{
    "domain": "apify.com",
    "website": "https://apify.com/",
    "emails": [
        { "email": "hello@apify.com", "foundOn": ["https://apify.com/contact"] }
    ],
    "phones": [
        { "phone": "+13024561234", "foundOn": ["https://apify.com/contact"] }
    ],
    "socialProfiles": {
        "linkedIn": ["https://www.linkedin.com/company/apifytech"],
        "twitter": ["https://twitter.com/apify"],
        "github": ["https://github.com/apify"]
    },
    "pagesScanned": 15,
    "scrapedAt": "2026-07-04T10:00:00.000Z"
}

Field	Meaning
emails[].foundOn	Every page the address appeared on — your audit trail.
phones[]	tel: links, international +-prefixed numbers, and strict US 3-3-4 formats like (703) 836-9300 (normalized to +1...). We prefer missing a number over inventing one.
socialProfiles	Canonical profile URLs per platform (LinkedIn, X/Twitter, Facebook, Instagram, YouTube, TikTok, GitHub).
pagesScanned	Actual pages fetched for this site.
error	Only present when pagesScanned is 0. Tells you why: e.g. "Disallowed by robots.txt" or a fetch failure reason. Every website you submit gets exactly one result item — never a silent drop.

Pricing

Pay per result. 1 result = 1 website profile (regardless of how many pages were scanned for it).

Websites	Cost at $4.00 / 1,000
100	$0.40
1,000	$4.00
10,000	$40.00

Compare: per-page pricing elsewhere at ~$1/1,000 pages × 15 pages/site ≈ $15 per 1,000 sites — and you still have to aggregate the pages yourself.

Compliance & fair use

Public web pages only. Robots.txt honored per site. Polite rate limits (1 req/s per domain). No login-walled or paywalled content. You are responsible for using extracted contact data in line with applicable law (GDPR, CAN-SPAM, etc.) in your jurisdiction.

Using from API / MCP / AI agents

Standard Apify actor — call it via REST API, scheduler, webhooks, or the Apify MCP server so LLM agents can invoke it as a tool:

curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{ "startUrls": [{ "url": "https://apify.com" }] }'

FAQ

Why did a site return zero emails? Some sites keep contacts behind JavaScript or forms only. We do not guess. Check pagesScanned and error — if pagesScanned is 0, the error field says exactly why (usually robots.txt disallowed crawling, and we honored it).

Do you verify email deliverability? No — we extract what is published, with provenance. Pipe into a verifier if you need deliverability guarantees.

Changelog

• 0.1.1 (2026-07) — Every submitted website now always gets a result item, even when zero pages could be fetched (robots.txt block or fetch failure) — the reason is in the new error field. Fixed a text-extraction bug where two adjacent links with no whitespace between them (e.g. mailto: link followed immediately by another link) could merge into one malformed email.
• 0.1.0 (2026-07) — Initial release: aggregated per-site profiles, contact-page prioritization, de-obfuscation, junk filters, provenance (foundOn), robots.txt compliance.

---

Maintained by Sturdy Data — boring, reliable scrapers. Report issues in the Issues tab; we respond within 24 hours.