# Website Email Extractor - Emails, Phones, Social Links (`solarg/website-contact-extractor`) Actor

Extract emails, phone numbers and social media profiles from a list of websites or domains. Checks each homepage plus its contact, about and team pages. Flat $3 per 1,000 websites, however many pages are checked.

- **URL**: https://apify.com/solarg/website-contact-extractor.md
- **Developed by:** [Solar G](https://apify.com/solarg) (community)
- **Categories:** Lead generation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 websites

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

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

Finds contact details for a list of websites: email addresses, phone numbers and social media profiles. For each site it loads the homepage and then the pages most likely to have contact details (contact, about, team, imprint, support).

For a quick one-off check without an Apify account, a free web version with a small daily limit is available at [purfled.com/website-email-finder](https://purfled.com/website-email-finder/).

### Input

| Field | Description |
|---|---|
| `websites` | Domains or URLs, e.g. `example.com` or `https://www.example.com/contact`. When a URL has a path, that page is checked first, then the homepage. An email address such as `info@example.com` is read as its domain. Entries may also be objects with a `url` field, e.g. `{"url": "https://example.com"}`. |
| `maxPagesPerWebsite` | Pages to check per site (start page first, then likely contact pages). Default 8, max 30. |
| `proxyConfiguration` | Optional, for sites that block cloud servers. |

```json
{
  "websites": ["wholelattelove.com", "basecamp.com", "https://www.bbc.co.uk/contact"],
  "maxPagesPerWebsite": 8
}
```

### Output

One record per website:

```json
{
  "input": "wholelattelove.com",
  "website": "https://wholelattelove.com",
  "domain": "wholelattelove.com",
  "finalUrl": "https://www.wholelattelove.com/",
  "title": "Whole Latte Love - Espresso Machines, Coffee Makers & Coffee",
  "description": "We are coffee experts...",
  "emails": ["customerservice@wholelattelove.com", "support@wholelattelove.com"],
  "phones": ["+1-585-924-7170", "+1-888-411-5282", "585-404-9303"],
  "phonesUncertain": [],
  "socials": {
    "youtube": ["https://www.youtube.com/user/wholelattelovetv"],
    "facebook": ["https://www.facebook.com/WholeLatteLoveOnline"],
    "instagram": ["https://www.instagram.com/wholelattelove"]
  },
  "contactPages": ["https://www.wholelattelove.com/pages/contact-us"],
  "pagesScraped": 6
}
```

| Field | Meaning |
|---|---|
| `input` | The entry as given in the input. |
| `website` | Origin of the input, e.g. `https://example.com`. |
| `domain` | Domain of the site that was crawled, after redirects (for example `basecamphq.com` redirects to `basecamp.com`). |
| `finalUrl` | The first page's URL after redirects. |
| `emails` | Addresses on the site's own domain first. |
| `phones` | Numbers from `tel:` links and schema.org data. The same number in different formats is listed once. |
| `phonesUncertain` | Phone-like numbers found in the page text, next to a word such as "phone" or "call", or in a common national format. Check these before use. |
| `socials` | Profile URLs by network. Share buttons, login and help pages, and links to the site itself are left out. |
| `contactPages` | Pages, other than the first, where new contact details were found. |
| `pagesScraped` | Pages requested for this site. |

Supported social networks: Facebook, Instagram, LinkedIn, X/Twitter, YouTube, TikTok, Pinterest, GitHub, Telegram, WhatsApp (normalised to `https://wa.me/<number>`), Threads, Bluesky, Discord, Reddit and Snapchat.

How emails are found:

- `mailto:` links, visible text, schema.org data, and Cloudflare-protected addresses (`[email protected]`), which are decoded.
- Common obfuscations: `name [at] domain [dot] com`, `name(at)domain(dot)com`, HTML entities. The plain-word form `name at domain dot com` is kept only when it is on the site's own domain.
- Addresses elsewhere in the page source (scripts, attributes) are kept only when they are on the site's own domain. Form placeholders and percent-encoded fragments are ignored.

### Errors

A website that cannot be processed returns an item with `input`, `error` and `blocked`, and is not charged:

```json
{ "input": "shop.example-store.com", "website": "https://shop.example-store.com", "domain": "shop.example-store.com", "error": "Could not load https://shop.example-store.com: the site refused the request (HTTP 403), probably bot protection", "blocked": true }
```

- `blocked` is true when the site refused the request (HTTP 403, 429 and similar) or showed a bot-protection page. Try again with `proxyConfiguration` set to Apify Proxy.
- Other errors give the reason: the domain does not exist (DNS lookup failed), the site did not respond in time, the page was not found, or it is not an HTML page.
- Entries that are not websites (for example `not a website`) return `{"input": "...", "error": "Not a website URL or domain: ..."}`.
- Duplicate entries are checked once and charged once. `example.com`, `www.example.com`, `http://example.com` and `EXAMPLE.com` count as the same website.

### API usage

```bash
curl -X POST "https://api.apify.com/v2/acts/solarg~website-contact-extractor/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"websites": ["wholelattelove.com", "basecamp.com"]}'
```

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("solarg/website-contact-extractor").call(run_input={"websites": ["wholelattelove.com"]})
items = client.dataset(run["defaultDatasetId"]).list_items().items
```

### Pricing

$3.00 per 1,000 websites (event "Website"). That is a flat price per site, however many pages are checked, and platform usage is included. Error items are not charged.

### Limitations

- Pages are fetched without a browser, so details that only appear after JavaScript runs may be missed.
- Phone numbers in plain text are reported separately in `phonesUncertain`, because numbers in text can also be order numbers or IDs.
- Only publicly visible contact details are collected. Use them in line with applicable law (for example UK GDPR, PECR, CAN-SPAM).

Report problems in the Issues tab.

# Actor input Schema

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

Domains or URLs, e.g. example.com or https://www.example.com/contact. When a URL has a path, that page is checked first, then the homepage. Entries that are not websites are returned as error items and not charged.

## `maxPagesPerWebsite` (type: `integer`):

The homepage plus likely contact pages (contact, about, team, imprint, support). More pages find more details but take longer.

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

Optional. Only needed for sites that block cloud servers.

## Actor input object example

```json
{
  "websites": [
    "apify.com",
    "wholelattelove.com"
  ],
  "maxPagesPerWebsite": 8
}
```

# Actor output Schema

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

One row per website, in the Contacts table view.

## `results` (type: `string`):

All items in the default dataset.

# 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": [
        "apify.com",
        "wholelattelove.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("solarg/website-contact-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": [
        "apify.com",
        "wholelattelove.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("solarg/website-contact-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": [
    "apify.com",
    "wholelattelove.com"
  ]
}' |
apify call solarg/website-contact-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,solarg/website-contact-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/VBRaLX4iOBQOhgvVf/builds/b9X4hHwpHXq61fRaQ/openapi.json