Contact Enrichment Scraper

Turn a plain list of website domains into structured business contact data: emails, phone numbers, social profiles, postal addresses, and VAT / company registration numbers.

Why use this actor?

You have domains — from a CRM export, a directory scrape, or a prospect list — and you need the actual contact details behind them. This actor visits each website, finds the pages where contact data lives (contact, about, impressum, team, legal), and returns one clean, aggregated record per domain. No login, no cookies, no API keys for the target sites.

Built for lead generation, sales prospecting, CRM enrichment, and B2B data teams that need reliable output instead of half-empty rows.

What it extracts

• Emails — from mailto: links, page text, and obfuscated forms: name [at] domain [dot] com, HTML entities, and Cloudflare email-protection encoding are all decoded automatically
• Phone numbers — from tel: links, schema.org data, and page text, normalized to international +-prefixed format with the country inferred from the domain TLD
• Social profiles — LinkedIn, Facebook, Instagram, X (Twitter), YouTube, TikTok company pages (share/intent links are filtered out)
• Postal addresses — from schema.org JSON-LD PostalAddress objects and <address> tags
• VAT numbers — EU VAT IDs (BE, NL, DE, FR, IT, ES, PL, AT, and 20+ more formats)
• Registration numbers — HRB/HRA (Germany), KvK (Netherlands), SIRET/SIREN/RCS (France), KBO/BCE (Belgium), CVR (Denmark), Org.nr (Sweden/Norway), CIF (Spain), REGON (Poland), IČO (Czechia/Slovakia)
• Company name — from JSON-LD organization data, og:site_name, or the page title

Every extracted value comes with provenance: the evidence field lists the exact page URLs each email, phone, or address was found on, so you can verify anything before it goes into your CRM.

How to scrape website contact data

1. Paste your domains into the Domains field (one per line — acme.de or https://acme.de both work), or pass full Start URLs instead
2. Optionally adjust Max Pages per Domain (default 10) — the homepage is always fetched first, then the crawler spends the remaining budget on the highest-value pages (contact, impressum, about, team, legal), with sitemap hints as a fallback
3. Run the actor and download the results as JSON, CSV, or Excel, or pull them via the Apify API
4. Each domain produces exactly one output item, so the dataset maps 1:1 to your input list

The crawler is HTTP-based (no headless browser), which makes it fast and cheap: a typical domain completes in a few seconds at roughly 10 page fetches.

Input

Field	Type	Required	Description
domains	Array	No*	Website domains to enrich, e.g. ["acme.de", "example.fr"]
startUrls	Array	No*	Alternative: full URLs; the domain is derived from each
maxPagesPerDomain	Integer	No	Crawl budget per domain (default: 10, max: 50)
maxDomains	Integer	No	Safety cap on domains per run (default: 100)
proxyConfiguration	Object	No	Proxy settings (Apify datacenter proxies by default)

*Provide either domains or startUrls. If both are empty, the actor runs on a small set of demo domains so you can inspect the output format.

Output

One item per domain:

Field	Type	Example
domain	String	"acme.de"
website	String	"https://www.acme.de/"
companyName	String	"ACME GmbH"
emails	Array	["info@acme.de", "sales@acme.de"]
phones	Array	["+49301234567"]
socialProfiles	Object	{"linkedin": "https://linkedin.com/company/acme"}
socialLinks	Array	All social URLs with platform labels
addresses	Array	["Hauptstraße 1, 10115 Berlin, DE"]
vatNumbers	Array	["DE123456789"]
registrationNumbers	Array	["HRB 12345"]
evidence	Object	Per-value foundOn page URLs
pagesCrawled	Integer	8
crawledUrls	Array	URLs of the crawled pages
scrapedAt	String	ISO 8601 timestamp

Example output

{
    "domain": "sipgate.de",
    "website": "https://www.sipgate.de/",
    "companyName": "sipgate",
    "emails": ["info@sipgate.de", "presse@sipgate.de"],
    "phones": ["+4921159980"],
    "socialProfiles": {
        "linkedin": "https://www.linkedin.com/company/sipgate",
        "instagram": "https://www.instagram.com/sipgate"
    },
    "addresses": ["Gladbacher Str. 74, 40219 Düsseldorf, DE"],
    "vatNumbers": ["DE219349391"],
    "registrationNumbers": ["HRB 39841"],
    "evidence": {
        "emails": [
            { "value": "info@sipgate.de", "foundOn": ["https://www.sipgate.de/impressum"] }
        ]
    },
    "pagesCrawled": 9,
    "scrapedAt": "2026-06-11T10:00:00.000Z"
}

Use cases

• Sales prospecting — enrich a target-account list with direct contact channels before outreach
• CRM hygiene — fill the gaps in existing records (missing phone, missing LinkedIn page)
• B2B databases — keep company registries up to date with verified VAT and registration numbers
• Compliance checks — confirm a supplier publishes a legal address and VAT ID (impressum data)
• Agency lead gen — qualify local businesses by checking which contact channels they actually publish

Cost estimate

The actor uses lightweight HTTP crawling (no browser), so compute cost is low: typically $0.10–0.30 in platform usage per 1,000 pages fetched, which at the default 10-page budget means roughly 100 domains enriched per ~$0.25 of compute, plus per-result pricing.

Tips for best results

• Keep the default maxPagesPerDomain of 10 for a good speed/coverage balance; raise it for large corporate sites with deep legal sections
• German, Austrian, and Swiss sites are gold: the legally required impressum almost always contains a phone number, address, VAT ID, and registry number
• Single-page JavaScript apps occasionally render contact data client-side only; the crawler still catches most of it via JSON-LD, meta tags, and raw script payloads, but a fully client-rendered site may return fewer fields
• Results are deduplicated and normalized: emails lowercased, phones in +-international format

Limitations

• The actor reads publicly published data only — it does not guess or generate email patterns
• Fully client-rendered sites (no SSR, no JSON-LD) may yield fewer values
• Phone normalization infers the country from the domain TLD; numbers on .com domains without an explicit + prefix are skipped rather than guessed wrong
• Respect GDPR and the target websites' terms of service when processing personal data

Need this data on a schedule, or a custom version?

We run this scraper as a managed service for businesses: scheduled runs, deduplication, delta detection, and delivery to your inbox, Google Sheets, or API — maintenance included. We can also build a custom version with your exact fields and filters, or combine multiple sources into one feed.

See studioamba.dev/services or email hello@studioamba.dev for a free data sample. We maintain 300+ European web scrapers and answer within one business day.