# Website Contact Finder: Emails, Phones & Socials (`hgh_han/website-contact-finder`) Actor

Extract business emails, phone numbers (E.164), social links and contact page from any list of websites. Charged only for domains where contacts are found. Hard spending cap, dedupe and skip lists built in.

- **URL**: https://apify.com/hgh_han/website-contact-finder.md
- **Developed by:** [Guangfang Han](https://apify.com/hgh_han) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Website Contact Finder – Emails, Phones & Social Links (pay only for results)

Find **business emails, phone numbers, social media profiles and the contact page** of any list of websites. Built for lead lists from Google Maps, directories or CRMs: paste domains, get one clean row per company.

### Why this one

- **Pay only for results.** Charged per domain where at least one email or phone was found (`contact-found` event). No contacts = free. No per-page or compute surprises.
- **Hard spending cap.** Set `maxChargeUsd` – the run stops before it can exceed it (plus Apify's own max-charge limit is respected).
- **No duplicates, no re-paying.** One record per domain. Skip domains you already have with `skipDomains` or `skipDatasetId` (a previous run's dataset).
- **Finds hidden emails:** `mailto:` links, plain text, obfuscated `info [at] acme [dot] com`, HTML entities, Cloudflare email protection (`data-cfemail`), JSON-LD.
- **Clean output:** junk filtered (image file names, Sentry/Wix tracking addresses, example.com, font-vendor credits, form placeholders), phones normalised to **E.164** with libphonenumber, optional **MX check** per email domain, emails tagged `generic` (info@, sales@) vs `personal`.
- **Fast & light:** HTTP-only (no browser), crawls just the home page plus contact / about / impressum / legal pages (default 5 pages, depth 1).

### Input

| Field | Description |
|---|---|
| `startUrls` / `domains` | Websites to check |
| `skipDomains`, `skipDatasetId` | Already processed – not crawled, not charged |
| `maxPagesPerSite` | Default 5 |
| `defaultCountry` | ISO-2 for local phone numbers (inferred from TLD if empty) |
| `checkMx` | Validate email domains (default true) |
| `requireEmail` | Output only domains with an email |
| `respectRobotsTxt` | Optional |
| `maxResults`, `maxChargeUsd` | Hard limits |
| `proxyConfiguration` | Optional |

### Output (one item per domain)

```json
{ "domain": "zodiacplumbing.co.uk", "url": "https://zodiacplumbing.co.uk", "emailsFound": 1,
  "emails": [{ "email": "info@zodiacplumbing.co.uk", "type": "generic", "mxValid": true, "sourceUrl": "https://www.zodiacplumbing.co.uk/" }],
  "phones": ["+441613885506"], "socials": { "facebook": "https://www.facebook.com/..." },
  "contactPageUrl": "https://www.zodiacplumbing.co.uk/contact/", "companyName": "Zodiac Plumbing and Heating",
  "pagesCrawled": 2, "status": "ok", "scrapedAt": "2026-10-26T02:55:00.000Z" }
```

`status`: `ok` (contacts found, billable), `no_contacts` (free), `failed` (site unreachable/blocked, free).

### Pricing

Pay-per-event: **$3 per 1,000 domains with contacts found** (`contact-found`). Domains without results and failed domains are not charged. Platform usage is included.

### Tested

Local test on 40 real small-business websites (dentists, plumbers, restaurants, accountants, hotels, physios, web agencies in US, UK, DE, AU, CA, PT, IE): 37/40 with at least one email, 34/40 with a phone, ~80 s total.

### Limitations

- HTTP only: sites that render contacts purely with JavaScript, or sit behind bot protection (403/challenge pages), may return no contacts.
- Contact forms without a visible address cannot yield an email.
- Emails of web agencies/developers credited in footers may appear (they are on the site); check `sourceUrl`.

### Legal / GDPR

This Actor extracts **publicly published business contact details** from company websites. It is intended for B2B use only. You are responsible for using the data lawfully (GDPR, ePrivacy, CAN-SPAM, PECR, local laws), including having a legitimate interest, honouring opt-outs and not collecting data about private individuals. Do not use it for spam.

# Actor input Schema

## `startUrls` (type: `array`):

Homepages of the businesses to check.

## `domains` (type: `array`):

Alternative to startUrls: bare domains like acme.com.

## `skipDomains` (type: `array`):

Domains already processed – they are not crawled and not charged.

## `skipDatasetId` (type: `string`):

ID of a dataset from an earlier run; every `domain` in it is skipped (no double charging).

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

Home page + up to N-1 contact/about/impressum/legal pages (depth 1).

## `defaultCountry` (type: `string`):

Used to parse local phone numbers, e.g. US, GB, DE. If empty, inferred from the domain TLD, falling back to US.

## `checkMx` (type: `boolean`):

Verify each email domain has mail servers (mxValid).

## `requireEmail` (type: `boolean`):

Only output domains with an email

## `respectRobotsTxt` (type: `boolean`):

Skip subpages disallowed by robots.txt.

## `maxResults` (type: `integer`):

Stop after this many output records (0 = no limit).

## `maxChargeUsd` (type: `number`):

Run stops before billable results would exceed this amount. Works in addition to Apify's own max-charge setting.

## `pricePerResultUsd` (type: `number`):

Must match the Actor's 'contact-found' event price.

## `chargeOnlyWithContacts` (type: `boolean`):

Keep true. Domains with no email/phone are free.

## `proxyConfiguration` (type: `object`):

Optional. Most small-business sites work without proxy.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.zodiacplumbing.co.uk/"
    }
  ],
  "maxPagesPerSite": 5,
  "checkMx": true,
  "requireEmail": false,
  "respectRobotsTxt": false,
  "maxResults": 0,
  "pricePerResultUsd": 0.003,
  "chargeOnlyWithContacts": true
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset of scraped contact records, one item per domain.

# 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 = {
    "startUrls": [
        {
            "url": "https://www.zodiacplumbing.co.uk/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hgh_han/website-contact-finder").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 = { "startUrls": [{ "url": "https://www.zodiacplumbing.co.uk/" }] }

# Run the Actor and wait for it to finish
run = client.actor("hgh_han/website-contact-finder").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 '{
  "startUrls": [
    {
      "url": "https://www.zodiacplumbing.co.uk/"
    }
  ]
}' |
apify call hgh_han/website-contact-finder --silent --output-dataset

```

## MCP server setup

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

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/cjl8yqVcdb18wI9Lc/builds/4CfoJ6vqxNMSaND20/openapi.json