# Website Contact & Social Extractor (`warant/website-contact-social-extractor`) Actor

Business website URLs in - verified emails, phones, social profiles and contact pages out. False-positive email filtering, optional DNS MX validation, contact-form fallback detection. Deterministic: no login, no LLM.

- **URL**: https://apify.com/warant/website-contact-social-extractor.md
- **Developed by:** [Waran T](https://apify.com/warant) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 website processeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Contact & Social Extractor

**Business website URLs in → verified contact channels out.** Feed it your lead list; get back emails,
phones, social profiles, the contact page, and whether a contact form exists — clean, deduplicated,
machine-readable.

### What you get per website

- **Emails** — mailto links and page text, with aggressive false-positive filtering (no `image@2x.png`
  artefacts, no build hashes, no placeholder domains) and **optional DNS MX validation** so addresses whose
  domain cannot receive mail are dropped, not delivered to you as "leads"
- **Phones** — publisher-declared `tel:` links first, conservative pattern match as fallback, normalised
- **Social profiles** — Facebook, Instagram, LinkedIn, X/Twitter, YouTube, TikTok (share/plugin URLs excluded)
- **Contact page URL** and **contact-form detection** — so a site that publishes no email still gives your
  workflow a next step
- `pagesChecked` so you can verify exactly what was read

### Design choices that matter

- **Fail-open MX validation**: only an authoritative "domain cannot receive mail" drops an email. A DNS
  hiccup flags the address `emailsMxUnverified` instead of silently destroying your data.
- **Deterministic**: plain HTTP fetch of home + contact/about pages. No headless browser, no LLM, no login,
  no anti-bot circumvention — it reads ordinary public pages the way any visitor does. Fast and cheap.
- **Honest output**: no email found means no email exists on those pages — not a guessed
  `firstname@domain.com`. Guessed emails bounce and burn your sender reputation.

### Input

```json
{ "websites": ["https://business-1.com", "https://business-2.com"], "maxPagesPerSite": 3, "validateMx": true }
```

Up to 500 websites per run.

### Output example (per website)

```json
{
  "website": "https://example-business.com/",
  "ok": true,
  "emails": [
    { "value": "office@example-business.com",
      "sourceUrl": "https://example-business.com/contact/",
      "dnsStatus": "domain_mail_capable" }
  ],
  "phones": [ { "value": "+15551234567", "sourceUrl": "https://example-business.com/" } ],
  "socials": { "facebook": { "urls": ["https://facebook.com/examplebiz"],
               "sourceUrl": "https://example-business.com/" } },
  "contactPageUrl": "https://example-business.com/contact/",
  "hasContactForm": true,
  "pagesChecked": ["https://example-business.com/", "https://example-business.com/contact/"]
}
```

Every contact carries the **source page URL** it was found on — you can always answer
"where did this email come from?"

**About `dnsStatus`:** `domain_mail_capable` means the domain has MX records and can receive mail.
It does **not** prove the specific mailbox exists — no tool can prove that without sending mail.
`domain_no_mx` addresses are dropped. `dns_unavailable` means the check could not run; the address is
kept and flagged rather than silently discarded.

### What this Actor does NOT do

- It never guesses or generates addresses (no `firstname@domain.com` patterns) — guessed emails bounce
  and burn your sender reputation
- It does not access login-only data, bypass CAPTCHAs, or enrich from private databases
- It cannot extract contacts a site only renders via JavaScript, or from sites that block ordinary fetches —
  such sites return their status honestly rather than fabricated data
- Results depend entirely on what the supplied site publicly serves. Not every site returns contacts.

### Pricing

**$4 per 1,000 websites processed** (pay-per-event, $0.004 per site). Process a 500-site lead list for $2.
A site is charged when it has been fetched and analysed — including sites that legitimately return no
contacts (the "no published email, has contact form" answer is itself the data).

### FAQ

**Why did a site return no emails?** Because none are published on its checked pages. See
`hasContactForm` and `contactPageUrl` for the next-best route, and `pagesChecked` for exactly what was read.
**Can it do thousands of sites?** Up to 500 per run; queue multiple runs or schedule for larger lists.
**Does it use an LLM?** No. Deterministic fetch + parse. That is why it is fast and cheap.

### Use with

n8n, Make, Zapier, AI agents, or straight from the API. Clear input/output schema — agent-friendly.

# Actor input Schema

## `websites` (type: `array`):

Business website URLs to process (max 500 per run).

## `maxPagesPerSite` (type: `integer`):

Homepage plus up to N-1 contact/about pages (1-5).

## `validateMx` (type: `boolean`):

Drop emails whose domain cannot receive mail. Recommended.

## Actor input object example

```json
{
  "websites": [
    "https://example.com"
  ],
  "maxPagesPerSite": 3,
  "validateMx": true
}
```

# Actor output Schema

## `contacts` (type: `string`):

The dataset of extracted contact records, one item per input website.

## `overview` (type: `string`):

Human-friendly table view of the extracted contacts.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "websites": [
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("warant/website-contact-social-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "websites": ["https://example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("warant/website-contact-social-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "websites": [
    "https://example.com"
  ]
}' |
apify call warant/website-contact-social-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,warant/website-contact-social-extractor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/wCGKMBZvKNuI2vBTu/builds/EIDGeVsgjHjZQ40XY/openapi.json