Website Contact Page Email & Phone Crawler avatar

Website Contact Page Email & Phone Crawler

Pricing

from $0.49 / 1,000 results

Go to Apify Store
Website Contact Page Email & Phone Crawler

Website Contact Page Email & Phone Crawler

Crawl a website's contact, about and team pages and collect its public emails, phone numbers, and social media profile links in one normalized record per site.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

Nimbryxo-studio

Nimbryxo-studio

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Features

Limited permissionsSingle-tenantServer interface

Share

Turn a list of company websites into one clean contact record per site. The actor crawls the homepage plus contact, about, team, support and imprint-style pages, then extracts public emails, normalised phone numbers, social profiles, the company name, postal address and contact forms — with the page each value came from.

It starts with explicit mailto:/tel: links, then reads visible text, then JSON-LD and microdata, and finally decodes common obfuscation such as [at]/[dot], HTML entities, full-width characters and Cloudflare email protection. Inline script bundles are never scanned, so analytics keys and image filenames do not end up in your dataset.

What this actor does

  • Crawls the registrable domain, so www.example.com, example.com and shop.example.com are treated as one site
  • Prioritises contact, about, team, support, imprint and legal-notice pages in English, German, French, Spanish, Italian, Portuguese and Dutch
  • Discovers unlinked contact pages from robots.txt sitemap entries and sitemap.xml
  • Extracts emails from mailto: links, visible text, JSON-LD, microdata, Cloudflare data-cfemail / /cdn-cgi/l/email-protection, and common obfuscated forms
  • Normalises phone numbers to E.164 with country and line type, using the website's country domain or your defaultCountry
  • Suppresses dates, prices, VAT/company-registry numbers, opening hours, fax labels and placeholder numbers
  • Keeps up to 19 social platforms, filtering share buttons, login pages and generic platform links
  • Renders up to two pages in a headless browser only when plain HTML contains no email or phone, blocking images, fonts and media
  • Omits empty fields instead of writing null, "", [] or {}

Output per website

One dataset item per input website. Fields are omitted when empty.

FieldDescription
typeAlways website_contacts.
websiteUrlThe normalised input URL.
statussuccess when an email, phone, social profile or contact form was found; no_contacts when pages loaded but none was found; failed when nothing could be fetched.
failureReasonOn failed rows: invalid_url, blocked, no_pages_fetched or crawl_error.
errorHuman-readable explanation on failed rows.
companyNameOrganisation name from JSON-LD, og:site_name, the page title or microdata.
companyNameSourcejsonld, og_site_name, title or microdata.
emailsSorted unique email addresses.
primaryEmailBest role address on the site's own domain, preferring contact, info, hello, sales, support.
roleEmailsAddresses such as info@, sales@, support@.
namedEmailsPersonal addresses such as jane.smith@.
emailDetailsPer address: email, type, sourceUrl, method, confidence.
phonesSorted unique E.164 numbers.
primaryPhoneBest number for the site's country, preferring fixed lines over mobiles.
phoneDetailsPer number: phone, raw, country, type, sourceUrl, method, confidence.
socialLinksObject keyed by platform with one profile URL per platform.
socialProfilesEvery profile: platform, url, sourceUrl, method.
addressPostal address from the site's own organisation JSON-LD/microdata: streetAddress, addressLocality, addressRegion, postalCode, addressCountry.
contactPageUrlHighest-scoring contact-like page found.
contactFormsUp to five contact forms: actionUrl, method, fieldCount, sourceUrl.
pagesCrawledSuccessfully fetched HTML pages.
pagesCrawledUrlsURLs of those pages.
maxDepthReachedDeepest link level reached from the start page.
skippedByRobotsURLs skipped because robots.txt disallowed them.
browserUsedtrue when the JavaScript fallback rendered a page.
crawledAtISO 8601 UTC timestamp.

emailDetails and phoneDetails carry provenance: the exact page and the extraction method (mailto, tel, visible_text, jsonld, microdata, cfemail, obfuscated) plus a confidence score from 0.75 to 0.98.

Input

FieldTypeDefaultDescription
urlsarray–Websites to scan. Required. Bare domains are accepted.
maxPagesPerSiteinteger20Pages fetched per site (1–200).
maxConcurrencyinteger5Pages fetched in parallel per site (1–20).
maxSitesConcurrencyinteger3Websites scanned in parallel (1–10).
requestTimeoutSecsinteger15Per-page timeout in seconds (5–60).
defaultCountryselectautoISO 3166-1 alpha-2 country used for phone numbers without an international prefix. Empty means infer from the domain ending.
useProxybooleanfalseStart with the Apify proxy ladder instead of direct requests. The actor retries blocked requests through the ladder automatically either way.
smartPrioritisebooleantrueTry common contact/about/team/imprint paths first.
respectRobotsTxtbooleantrueSkip pages disallowed by robots.txt.
useSitemapbooleantrueDiscover contact pages from sitemaps.
renderFallbackbooleantrueRender up to two pages in a headless browser when plain HTML has no email or phone.
onlyWithContactsbooleanfalseDrop records with no email, phone, social profile or contact form.
includeNamedEmailsbooleantrueKeep personal addresses; turn off to keep only role addresses.

Example: scan a single company site

{
"urls": ["https://apify.com"],
"maxPagesPerSite": 10,
"defaultCountry": "US"
}

Example: several sites, only rows with contacts

{
"urls": ["company-a.com", "https://company-b.co.uk", "https://company-c.de"],
"maxPagesPerSite": 15,
"onlyWithContacts": true,
"includeNamedEmails": false
}

Example: a JavaScript-heavy site through the proxy ladder

{
"urls": ["https://example-spa.com"],
"maxPagesPerSite": 8,
"renderFallback": true,
"useProxy": true
}

Use cases

  • Sales outreach — turn a list of target company websites into verified emails and phone numbers.
  • Lead enrichment — fill missing email, phone, address or social links in an existing CRM export.
  • Partnership scouting — find the right contact page and social presence before reaching out.
  • Directory building — seed a business directory with the contact details each company publishes itself.
  • Vendor research — compare how a set of suppliers presents contact channels.

FAQ

Do I need a proxy? No. Direct requests work for most sites. When a site blocks the datacenter IP, the actor retries through the Apify proxy ladder automatically; useProxy only makes it start there.

Does this render JavaScript? Only when needed. If plain HTML has no email or phone, the actor renders up to two pages (usually the homepage and the best contact page) in a headless browser, with images, fonts and media blocked. Content that requires a login, a captcha solve, or several clicks is not reached.

Why are some emails excluded? Placeholder domains (example.com, yourdomain.com), noreply-style addresses, image/font filename lookalikes, sentry/analytics addresses and addresses on asset CDNs are dropped. Inline script bundles are never scanned.

Why is a phone number missing? A number must be a valid, dialable number with 7–15 digits. Dates, prices, VAT and registry numbers, opening hours, fax labels and repeated-digit placeholders are rejected. National-format numbers need either a country-code domain or defaultCountry; otherwise only international + numbers are accepted.

Why are some phone numbers not in the format shown on the site? phones and phoneDetails[].phone are E.164 (+49374222388). The original text is kept in phoneDetails[].raw.

Why is socialLinks missing a platform? Only profiles linked from crawled pages or declared in JSON-LD sameAs are included. Share buttons, intent links, login pages and generic platform pages are skipped.

Why did a site return fewer pages than maxPagesPerSite? The crawl stops when it runs out of same-site links, reaches maxPagesPerSite, or hits robots.txt restrictions. Non-HTML responses and error pages are not counted.

Why can an output URL return 403? A site that blocked the crawler may still be recovered through the browser fallback, while the same URL returns 403 to a clean HTTP client. Some social platforms return 400/403 to non-browser clients. These are anti-bot responses, not broken URLs; the record states how the page was reached with browserUsed/proxyUsed.

Is this affiliated with any social platform? No. This is an independent, third-party actor that reads publicly available website content.

Limitations

  • Contact forms are detected, not submitted; the actor does not send messages.
  • Emails shown only inside images or a logged-in area cannot be extracted. A 30-site OCR trial found zero true image-only contacts and produced false positives, so OCR is intentionally not shipped.
  • Some sites serve a Cloudflare/Akamai/AWS WAF challenge to every datacenter and proxy IP; those rows are returned as failed with failureReason: "blocked" rather than guessed. The browser fallback tries direct first, then AUTO, then RESIDENTIAL only after a real block.
  • The JavaScript fallback is capped at two pages per site; a 20-site trial showed a 2.4× runtime increase for almost no additional contacts, so this is a deliberate design limit.
  • Pages larger than 5 MB are still downloaded in full before being skipped. Streaming the first 5 MB is a possible future optimization, not a shipped guarantee. Sitemap discovery is capped at three sitemaps, five sitemap-index children and twenty contact-like URLs; .xml.gz sitemaps are decompressed. Emails carry ownDomain and domainType (own, free_provider, third_party) so legal-page regulator/partner addresses can be filtered.
  • A company with several branches may publish several addresses; address uses the organisation's own JSON-LD address and omits branch Place entries when an organisation address exists.

Use it as an API (server mode)

Need one answer right away instead of a batch job? Send the input as an HTTP request and the results come back in the response. There's no run to start and poll.

curl -H "Authorization: Bearer $APIFY_TOKEN" \
"https://nimbryxo-studio--website-contact-page-email-and-phone-crawler.apify.actor/?urls=https%3A%2F%2Fapify.com&maxPagesPerSite=5"

Or POST the same input as JSON:

curl -X POST -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
-d '{"urls": ["https://apify.com"], "maxPagesPerSite": 5}' \
"https://nimbryxo-studio--website-contact-page-email-and-phone-crawler.apify.actor/"
  • The fields are the same as in the input above. With GET, repeat a parameter once for each value in a list.
  • You get back a JSON array with the same records a normal run saves. They're saved to the run's dataset too.
  • Each request is capped at 10 results and 4 minutes. For bigger jobs, start a normal run.
  • The request runs in your own Apify account at the Actor's normal price (a start fee plus a price per result). The server shuts down after a minute with no requests.
  • The Server tab on this page lists every parameter and lets you try a request from your browser.