# Website Email Finder: Emails & Phone Numbers (`stas_k/website-contacts-finder`) Actor

Contact scrapers miss the email sitting right on the site, bill per lead with no ceiling, and call a guessed address verified. This one reads the site plus its contact, about and imprint pages, tags every email and phone with the page it came from, and charges a fixed price per delivered site.

- **URL**: https://apify.com/stas_k/website-contacts-finder.md
- **Developed by:** [Stas K](https://apify.com/stas_k) (community)
- **Categories:** Lead generation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 site with contacts

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?

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 and socials from any site

Contact scrapers in this store tend to fail in the same three ways, and the reviews say it
better than any marketing page could:

1. **The email is right there on the site and the scraper does not retrieve it.** The most
   repeated complaint in this category, word for word.
2. **You pay per lead, so you cannot predict the bill.** The advertised price is per page,
   the real one is per contact - and a list of 500 sites can cost ten times what you
   planned, or nothing at all, depending on luck.
3. **You get a value with no source, and sometimes a guess dressed up as verified.** If an
   email was reconstructed from a pattern, calling it "verified" is not a detail - it is
   the difference between a working campaign and a bounced one.

### What this Actor does instead

- **Crawls the pages where contacts actually live.** The address you give, plus every
  contact / about / imprint / support / privacy page linked from it (up to
  `maxPagesPerSite`, default 5). More pages, more real emails - and no browser, no proxies.
- **Every value carries its source.** Each email and phone has `foundOn` - the exact page
  it was read from, and `kind` - whether it came from a `mailto:`/`tel:` link or from the
  page text. Nothing is generated, nothing is guessed, no pattern is filled in.
- **Pay only for sites that delivered.** A site that returns at least one email or phone
  costs one event. **A site with no contacts is free** - you still get its row, with the
  reason. **A row served from the cache is free too.** That is the whole pricing model,
  no tiers to decode.
- **The same site sent twice is crawled and billed once.** `apify.com`, `https://apify.com`,
  `https://www.apify.com/` and `simplify.hr/contact` are one site, not four - duplicates are
  dropped by host before any request, and `SUMMARY.duplicatesRemoved` tells you how many.
  Different subdomains stay different sites.
- **Nothing disappears silently.** Every unique input gets a row and one of six statuses:
  `OK` (contacts found), `NO_CONTACTS` (with how many pages were checked), `BLOCKED` (the
  site answered with an anti-bot challenge page - free, HTTP status in `reason`),
  `UNREACHABLE` (the HTTP code or the exact network error in `reason`), `INVALID_URL` (the
  line is not a http(s) address - free) or `ERROR` (that one line failed unexpectedly and
  the rest of the run continued). Compare that with a run that returns fewer rows than you
  sent.

### What you get

One row per website:

```json
{
  "website": "apify.com",
  "url": "https://apify.com",
  "domain": "apify.com",
  "company": "Apify",
  "status": "OK",
  "emails": [
    {"value": "sales@apify.com", "foundOn": "https://apify.com/contact", "kind": "mailto", "role": true}
  ],
  "phones": [
    {"value": "+420 123 456 789", "e164": "+420123456789", "foundOn": "https://apify.com/contact", "kind": "tel-link"}
  ],
  "socials": {"linkedin": "https://linkedin.com/company/apify", "github": "https://github.com/apify"},
  "address": {"street": "Vodickova 704/36", "city": "Praha", "postalCode": "11000", "country": "CZ"},
  "pagesScanned": ["https://apify.com", "https://apify.com/contact"],
  "pagesFailed": [],
  "reason": "",
  "fromCache": false,
  "scannedAt": "2026-11-05T09:12:44+00:00"
}
```

Social profiles collected when linked on the site: LinkedIn, X, Facebook, Instagram,
YouTube, GitHub, TikTok, Telegram, Threads. Address comes from the site's own schema.org
(JSON-LD) markup and is `null` when the site does not publish one.

### Price

Per site **that returned contacts** - not per page, not per address, not per email inside
the row. A site with nothing to give costs **$0.00**, and the row still tells you what was
checked. Long lists behave predictably: 500 sites that all have contacts cost 500 events,
not 1,400. Duplicates are dropped before crawling, and a cached row is not charged at all.

**You set the cap and the platform enforces it.** Every run has a hard spending limit
(`maxTotalChargeUsd` - in the Console or in the API call). We lowered the smallest limit the
Actor accepts to **$0.02**, the price of one result, so a run can never cost more than the
number you chose. No tiers to decode, no invoice surprises.

**For a long list, set the cap deliberately.** 500 sites that all have contacts cost $10, while
the platform default is about $4.8 - if your list is that long, raise the cap before the run.
**If the cap is reached, the SDK documentation says the platform stops that run.** In our own two
tests, with a $0.02 and a $0.04 cap, the run finished with every row intact and nothing was
charged beyond the cap - we have not reproduced an abort ourselves, so treat it as the
documented behaviour and not as our promise. Either way `SUMMARY` is saved as the run goes
(every 25 sites, `partial: true`), so rows already found are not lost, and
`SUMMARY.cappedNotCharged` counts the sites that were reported but not billed.

### Honest limits

- **HTTP only, no JavaScript.** Sites that draw their contact block with client-side JS will
  come back as `NO_CONTACTS`. We say so instead of pretending. A browser-based mode is not
  included - it would multiply the price of every run.

- **No deliverability claims.** We do not say an email is "verified", "valid" or
  "deliverable", because we did not run an SMTP handshake. We say where we found it.

- **A phone is returned exactly as it is written on the page.** `8 (495) 123-45-67` stays
  exactly that. We never glue a `+` in front of a number that did not have one - that turned
  a Moscow number into a Vietnamese one in an earlier build. `e164` appears only when the
  page itself wrote the international form.

- **A bare number is not a phone.** A number written without `+` is taken only when a
  phone word (`phone`, `tel`, `call`, `contact`…) stands next to it, or when it is a `tel:`
  link; a `+` number is taken as written. That is how a code sample on python.org - the
  Fibonacci sequence `8 13 21 34 55 89 144` - stopped being read as two phone numbers.

- **Code samples are not contacts.** Text inside `<pre>`, `<code>` and `<samp>` is left out
  of phone and email extraction, and a phone or an address published in the site's
  schema.org (JSON-LD) markup is read too.

- **A date is not a phone, and neither is a parcel id.** Publication dates (`04.11.2026 19:48`),
  map coordinates (`50.4501 30.5234`) and tracking numbers (`1234 5678 9012` after the words
  "tracking number") are rejected before they can become a fake contact - every one of them
  was a live bug here, and every one now has a test.

- **Dot-separated phones are understood.** `202.555.0123` is a US number, not a decimal
  fraction; the guard that removed `3.14159` no longer eats it.

- **A third-party mailbox still counts.** If the only address on a site is a gmail.com
  inbox, it is returned in `foreignEmails` and the site counts as having contacts - the
  complaint we built this Actor against was "the email is on the site and the scraper
  misses it".

- **Cloudflare and friends.** A site that blocks automated access is reported as
  `BLOCKED` with the HTTP status in `reason` - and it is free.

- **Same answer twice is cached.** For `cacheMinutes` (default 24h) a repeated run is served
  from the cache in the account of whoever runs the Actor; those rows are marked
  `fromCache: true` and are **not charged** - you paid for that crawl the first time.

### Run it your way

From the Apify UI, from the API, or from an MCP client. One input is enough:

```json
{ "websites": ["apify.com", "stripe.com", "figma.com"] }
```

Words that are not guessed here: every email in the row exists on the site you sent us.

# Actor input Schema

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

One line per website: a domain (apify.com) or a full URL (https://apify.com/contact). A comma or newline separated string works too. Duplicates are dropped by host: one site, one crawl, one event. A site with no contacts is reported with the reason instead of disappearing.

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

How deep to look. Page 1 is always the address you gave; the rest go to contact/about/imprint/support/privacy pages found on it. More pages = more chances to find a hidden email, and a little more run time.

## `includeSocials` (type: `boolean`):

LinkedIn, X, Facebook, Instagram, YouTube, GitHub, TikTok, Telegram, Threads - only the ones actually linked on the site.

## `includeAddress` (type: `boolean`):

Take the company address from the site's schema.org markup (JSON-LD). Empty when the site does not publish one - nothing is filled in from a guess.

## `cacheMinutes` (type: `integer`):

A repeated run for the same site inside this window is served from cache: no second crawl, no wasted time. 0 turns the cache off.

## `concurrency` (type: `integer`):

How many websites are crawled at the same time. 8 is a good default; raise it only for large lists.

## Actor input object example

```json
{
  "websites": [
    "apify.com",
    "https://www.simplify.hr/contact"
  ],
  "maxPagesPerSite": 5,
  "includeSocials": true,
  "includeAddress": true,
  "cacheMinutes": 1440,
  "concurrency": 8
}
```

# Actor output Schema

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

Dataset with one row per website: emails with the page each one was found on, foreign emails kept apart, phones, 9 social networks, address, pages scanned and the reason when nothing was found.

## `summary` (type: `string`):

How many sites had contacts, how many were empty, blocked or unreachable, and what was charged.

# 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",
        "https://www.simplify.hr/contact"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("stas_k/website-contacts-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 = { "websites": [
        "apify.com",
        "https://www.simplify.hr/contact",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("stas_k/website-contacts-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 '{
  "websites": [
    "apify.com",
    "https://www.simplify.hr/contact"
  ]
}' |
apify call stas_k/website-contacts-finder --silent --output-dataset

```

## MCP server setup

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