subimpact WhatsApp us

Website Contact & Social Extractor

The Website Contact and Social Extractor scans a list of websites and returns one row per domain with deduplicated emails, phones that keep a raw and a normalised value, and social profile URLs across Facebook, Instagram, LinkedIn, X, TikTok, YouTube, WhatsApp and Telegram. It fetches contact and about pages first, uses plain HTTP, and respects robots.txt. Pages cost $0.80 per 1,000 scanned, with no per-lead fee. Run it from Apify Console or the API.

from $0.0008 per page scanned, $0.8 per 1,000 ยท Updated Nov 2026, version 0.1.3

Key facts

Price
from $0.0008 per page scanned, $0.8 per 1,000
Pricing model
Pay per event
Output
JSON, CSV, Excel, XML, RSS via Apify datasets
Access
Apify Console, REST API, Python and JS clients, MCP tool website_contacts
Version
Updated Nov 2026, version 0.1.3
Usage
100.0% successful runs (30 days)
Actor
subimpact/website-contact-extractor

Who it is for

  • Sales teams building prospect lists from a domain list they already trust
  • Agencies auditing client and competitor contact pages
  • Directories needing verified public contact details per company
  • Researchers mapping how businesses present themselves on social

Use cases

Turn a domain list into contact rows

Paste domains or full URLs into startUrls, including bare forms such as hartamas.com, and set maxPagesPerSite to 5. Each site row returns emails, phones and socials, with pagesScanned and pagesWithContacts showing where the details were found. Duplicate domains collapse, so a messy list of one domain written five ways produces a single row.

Prefer contact pages over the homepage

Links whose URL or anchor text mentions contact, about, team, support, legal, impressum, kontakt or hubungi are fetched before other pages on the same domain. That ordering is why a five page budget usually finds the address a ten page generic crawl misses, and pagesWithContacts names the exact pages that carried a detail.

Build a clean phone list

Each phone is returned as an object with the raw string and a normalised value, so +603 7839 5617 becomes +60378395617 for matching. Numbers without an international prefix stay national digits. Text numbers that appear bare are only taken from tel links and JSON-LD, which keeps order numbers, dates and coordinates out of your phone column.

Map social presence per company

socials always contains every supported network, even when the array is empty, so the shape never shifts between rows. LinkedIn returns company and personal profiles, and share, intent and tracking links are stripped, which leaves you with profile URLs rather than the sharing buttons most pages embed.

Audit a site's published details

Set outputPerPage true to get one extra row per fetched page, each with its own emails, phones, socials, pageUrl and pageTitle. That shows which pages publish a phone number and which only carry an email, and page rows are not charged separately, so the audit costs the same as the site scan.

Output fields

FieldTypeDescription
rowType string site for one website row, page for an optional per-page row
inputUrl string The URL or domain exactly as supplied in startUrls
domain string The website domain, with a leading www. removed
pageUrl string/null The fetched page URL on a page row, null on a site row
pageTitle string/null The HTML title on a page row, null on a site row
status string success when contacts were found, no-contacts when pages were scanned but no contacts were found, error when the site could not be scanned
emails array Deduplicated email addresses, lowercase, junk and placeholder addresses removed
phones array Deduplicated phone numbers with the raw text and a normalised value
socials object Profile URLs grouped by network. Share, intent and tracking links are removed.
pagesScanned integer Pages successfully fetched as HTTP 200 HTML and scanned. 1 on a page row.
pagesWithContacts array URLs of the scanned pages that contained at least one email, phone or social profile
httpStatus integer/null 200 on a page row, null on a site row
Show all 14 fields
FieldTypeDescription
error string/null A readable failure reason on an error row, null otherwise
scrapedAt string ISO timestamp for the row

Sample output

From one of our own test runs on 20 Nov 2026, trimmed. Personal data is redacted.

1 rows, first 3 shown

[
  {
    "rowType": "site",
    "inputUrl": "https://apify.com",
    "domain": "apify.com",
    "pageUrl": null,
    "pageTitle": null,
    "status": "success",
    "emails": [
      "[email redacted]"
    ],
    "phones": [],
    "socials": {
      "facebook": [],
      "instagram": [],
      "linkedin": [
        "https://linkedin.com/company/apify"
      ],
      "x": [
        "https://x.com/apify"
      ],
      "tiktok": [
        "https://tiktok.com/@apifytech",
        "https://tiktok.com/@apifyoffice"
      ],
      "youtube": [
        "https://youtube.com/apify"
      ],
      "pinterest": [],
      "threads": [],
      "whatsapp": [],
      "telegram": []
    },
    "pagesScanned": 3,
    "pagesWithContacts": [
      "https://apify.com/",
      "https://apify.com/about",
      "https://apify.com/contact"
    ],
    "httpStatus": null,
    "error": null,
    "scrapedAt": "2026-11-20T02:43:27.029Z"
  }
]

Input

FieldTypeRequiredDescriptionDefault
startUrls array No One entry per website. Full URLs and bare domains are accepted, for example https://apify.com or hartamas.com. The first URL per domain is used as the start page. Duplicate domains are collapsed. [{"url":"https://apify.com"}]
maxPagesPerSite integer No Pages fetched and scanned per website, including the start page. Links whose URL or anchor text mentions contact, about, team, support, legal, impressum, kontakt or hubungi are fetched first. Higher values find more contacts and cost mor... 5
maxItems integer No Global cap on website rows delivered in one run. The default of 10 keeps a default run under $0.05 at 5 pages per site. Raise it for larger lists. Optional per-page rows are not counted against this cap and are not charged separately. 10
concurrency integer No How many websites are processed at the same time. Pages within one site are fetched one at a time. Lower this if target sites rate-limit you. 10
outputPerPage boolean No Adds one dataset row per successfully fetched page with that page's own contacts. These page rows are not charged separately. Billing is still per page scanned, charged once after each site row. false
respectRobotsTxt boolean No Check each site's robots.txt before fetching pages and skip disallowed URLs. Keep this on unless you own the sites or have permission to crawl them. true
proxyConfiguration object No Direct requests are the default and were measured to work for the example sites. Enable Apify datacenter or residential proxy only if target sites block the Apify IP ranges. A proxy failure fails the request and never falls back to a dir... {"useApifyProxy":false}

Example input

{
  "startUrls": [
    {
      "url": "https://apify.com"
    },
    {
      "url": "https://www.hartamas.com"
    }
  ],
  "maxPagesPerSite": 5,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Pricing

EventWhat it meansPriceLowest tier
page-scanned One web page fetched and scanned for contacts. $0.0008 $0.0008

$0.8 for 1,000 page scanned units at the listed price.

Prices from the Apify Store on 20 November 2026. Apify shows the final price before each run.

How it compares with other Apify actors

Price per 1,000 pages at Apify Store list prices. Every row is a live listing on the Store, read on 20 Nov 2026, so a buyer can check each number at the source.

Actor Price per 1,000 pages (Free plan) Higher plans (Gold) Start fee per run Platform usage Users Rating Last build
Website Contact & Social Extractor (Emails, Phones, Socials) This API Pay per event $0.8 $0.8 None Included 2 No reviews yet 18 Nov 2026
Contact Details Scraper Direct match, pay per event $2.00 $1.05 $0.001 Included 68,924 No reviews yet 11 Nov 2026
๐Ÿ“ฉ๐Ÿ“ Google Maps Email Extractor Partial match, pay per event Charges per Google Maps place, with contact and lead enrichment as separate add-ons. $0.00005 Included 95,141 4.6 (221 reviews) 18 Nov 2026
Where Contact Details Scraper is stronger

Where Contact Details Scraper is stronger

  • Much larger user base and a long review history on the Apify Store
  • Optional browser, residential proxy and email verification add-ons
  • More platforms detected, including Pinterest, Discord, Snapchat, Reddit and Threads

Where this API is stronger

  • One charge per page scanned, with no per lead or per social profile fee
  • Plain HTTP with no browser, so long URL lists run fast and cheaply
  • Robots.txt handling is an explicit input flag rather than an assumption

Full comparison: Contact Details Scraper vs this API

Where ๐Ÿ“ฉ๐Ÿ“ Google Maps Email Extractor is stronger

Where ๐Ÿ“ฉ๐Ÿ“ Google Maps Email Extractor is stronger

  • Starts from Google Maps search terms, so a prospect list can be built without any URLs
  • Also returns place address, category, rating and review count
  • Contact and social profile enrichment as optional add-ons

Where this API is stronger

  • Works from any list of website URLs, not only Google Maps places
  • One charge per page scanned, with no add-on per lead
  • No browser needed, so a large URL list stays inexpensive

Two established actors cover website contact extraction, one from URL lists and one from Google Maps searches. Both are well used and both charge add-ons for leads or enriched profiles. Ours is the plain option: any URL list in, emails, phones and social links out, one charge per page scanned and no per lead fees.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

How to run it

  1. List websites in startUrls, one per entry, as https://apify.com or a bare domain such as hartamas.com.
  2. Set maxPagesPerSite, for example 5, and maxItems as the site count cap, for example 10.
  3. Keep respectRobotsTxt on unless you own the sites or have permission to crawl them.
  4. Turn on outputPerPage if you need to know which page carried which detail.
  5. Run the actor, then read site rows in the dataset or export them as JSON, CSV or Excel.

cURL

curl -X POST "https://api.apify.com/v2/acts/subimpact~website-contact-extractor/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":[{"url":"https://apify.com"},{"url":"https://www.hartamas.com"}],"maxPagesPerSite":5,"proxyConfiguration":{"useApifyProxy":false}}'

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/website-contact-extractor").call(run_input={"startUrls":[{"url":"https://apify.com"},{"url":"https://www.hartamas.com"}],"maxPagesPerSite":5,"proxyConfiguration":{"useApifyProxy":false}})

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/website-contact-extractor').call({"startUrls":[{"url":"https://apify.com"},{"url":"https://www.hartamas.com"}],"maxPagesPerSite":5,"proxyConfiguration":{"useApifyProxy":false}});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);

MCP

claude mcp add subimpact-data -e APIFY_TOKEN=<YOUR_APIFY_TOKEN> -- npx -y @subimpact/data-mcp

# Then ask your agent to use the website_contacts tool.

n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/website-contact-extractor
Input JSON: paste the example input above.

MCP users: @subimpact/data-mcp exposes these actors as tools, so an agent can call website_contacts directly.

Limits

  • No JavaScript rendering, so details injected client-side can be missed.
  • Only HTTP 200 HTML is scanned, meaning PDFs and images are skipped.
  • Emails and phones are capped at 100 each per site, socials at 25 per network.
  • No deliverability or validity check on any address or number.

Questions people ask

What does a scan cost?

A successfully scanned HTML page costs $0.0008, which is $0.80 per 1,000 pages, and platform usage is included. There is no per-lead, per-email or per-social-profile fee. Billing happens once per site row with the page count, and error rows are never charged.

Where do the contact details come from?

From mailto and tel links, visible page text, JSON-LD Organization and LocalBusiness blocks, and sameAs values. Simple obfuscations such as name at domain dot com and Cloudflare data-cfemail values are decoded. Placeholder addresses and image file names are filtered out before they reach the output.

Why are some contacts missed?

Only HTTP 200 HTML is scanned, and there is no JavaScript rendering, so details injected after load can be missed, as can PDFs and other file types. At most 50 pages per site are read, and emails and phones are capped at 100 per site with socials capped at 25 per network.

Does it check whether an email is valid?

No. The actor does not send mail, check deliverability or confirm a phone is still in service, and it does not submit forms or solve CAPTCHAs. Treat every address as stale until you have verified it through your own channel.

Can I control which pages get fetched?

Indirectly. maxPagesPerSite sets the budget and the actor spends it on contact, about, team, support, legal, impressum, kontakt and hubungi pages first, then other same-domain links. robots.txt is checked before each fetch when respectRobotsTxt is on, and a disallowed start page becomes an uncharged error row.

What does a phone entry look like?

Each phone is an object with raw and normalised fields. raw keeps the text exactly as published, and normalised strips spacing and punctuation, keeping a leading plus only when the source carried an international prefix. That makes deduplication and matching against a CRM straightforward.

Is it acceptable to run this on any list?

Only on sites you are allowed to access. Contact details can be personal data, so you need a lawful basis before outreach, and you should follow each site's terms and applicable privacy law. The actor keeps robots.txt enforcement on by default and rejects local and private network hosts.

Need a data source that is not here?

We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.