Company & Website Lead Enricher
Pricing
Pay per event
Company & Website Lead Enricher
Input a list of domains. For each, crawl the homepage plus contact/about pages and extract emails, phone numbers, social profile links, physical address, and mailto/tel hrefs. Deterministic (regex + HTML parse), no LLM. One enriched record per domain.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Martello Systems
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Company / Website Lead Enricher
Give it a list of domains. For each one it crawls the homepage plus the obvious
contact pages (/contact, /about, etc.) and extracts the lead-relevant
contact data it finds. Extraction is deterministic (regex + HTML parse) -
no LLM, no guessing, no invented data. You get one enriched record per
domain.
Input
| Field | Required | Description |
|---|---|---|
domains | yes | List of domains or full URLs (e.g. example.com or https://example.com). |
max_pages_per_site | no | Cap on pages fetched per domain (default 3). |
include_subpages | no | Also fetch contact/about subpages found on the homepage (default true). |
Output
One dataset record per domain. A run summary is written to the key-value store
under OUTPUT.
Example record
{"domain": "example.com","input": "https://example.com","final_url": "https://example.com/","ok": true,"pages_crawled": ["https://example.com/", "https://example.com/contact", "https://example.com/about"],"emails": ["hello@example.com", "sales@example.com"],"phones": ["+1 415 555 0100", "(212) 555-0142"],"socials": {"linkedin": ["https://www.linkedin.com/company/example"],"twitter": ["https://twitter.com/example"],"facebook": ["https://www.facebook.com/example"],"instagram": ["https://www.instagram.com/example"],"youtube": ["https://www.youtube.com/@example"]},"mailto_hrefs": ["mailto:hello@example.com"],"tel_hrefs": ["tel:+14155550100"],"addresses": ["123 Market St, San Francisco, CA 94103"],"error": null}
Notes
- Crawling is routed through Apify's residential proxy pool when available, so sites are far less likely to IP-block the run.
- Robust per-domain: a fetch failure on one domain never aborts the run; the
domain still emits a record with
ok: falseand anerrormessage. - Email extraction drops common image/asset false positives (e.g.
logo@2x.png).