# Website Contact & Tech Extractor — Emails, Phones, Stack (`dalbian/website-contact-extractor`) Actor

Give it company domains and it reads each company's own website for published emails, phone numbers, social profiles, VAT numbers and the technologies they run — respecting robots.txt, with no third-party database involved.

- **URL**: https://apify.com/dalbian/website-contact-extractor.md
- **Developed by:** [Benjamin Jerez](https://apify.com/dalbian) (community)
- **Categories:** Lead generation, Business, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$8.00 / 1,000 site analyseds

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 & Tech Extractor — Emails, Phones, Stack

Give it a list of company domains. It visits **each company's own website**, follows the pages most likely to carry contact details, and returns what that company publishes about itself: email addresses, phone numbers, social profiles, VAT and SIRET numbers, and the technologies it runs.

No third-party database. No platform. No login. No terms of service bent. Just the site the domain points at — and it obeys `robots.txt`.

### What comes back

| Field | Example (apify.com) |
| --- | --- |
| `primaryEmail`, `emails` | support@apify.com, hello@apify.com |
| `primaryPhone`, `phones` | +33 4 90 82 20 22 |
| `socialProfiles`, `linkedin` | LinkedIn, GitHub, X, YouTube, TikTok |
| `technologies` | Next.js, HubSpot, Intercom, Google Tag Manager, Cloudflare |
| `vatNumbers`, `siretNumbers` | CZ04788290, GB373153700 |
| `title`, `description` | Apify: Marketplace of ready-to-run tools for AI |
| `contactPages`, `pagesCrawled` | /about, /contact, /contact-sales — 10 pages |

`primaryEmail` prefers a generic address — `contact@`, `info@`, `hello@`, `sales@` — because that is the one a company publishes to be written to.

### The technology detection

Around forty signatures across CMS and e-commerce platforms (WordPress, Shopify, PrestaShop, Magento, Wix, Webflow), JavaScript frameworks (Next.js, Nuxt, React, Vue, Angular, Svelte), analytics (GA4, Matomo, Plausible, Hotjar), CRM and marketing (HubSpot, Salesforce, Klaviyo, Mailchimp), support chat (Intercom, Crisp, Zendesk, Tawk.to) and payments (Stripe, PayPal).

This is how an agency finds every prospect running an outdated stack, or how a SaaS finds everyone already using a tool it integrates with. A real run on a small French firm returned `WordPress, WooCommerce, PHP/7.2` — a PHP version unsupported since 2020, which is a sales conversation on its own.

### How the crawl works

Contact, about, legal-notice, impressum and privacy pages are queued ahead of everything else, in several languages, so the details are usually found within the first few pages. Static files, share links and external domains are skipped. Pages within one site are read one after another, never in parallel, while different sites run concurrently.

`robots.txt` is fetched first and respected. A site that disallows crawling is reported as `robotsBlocked` rather than silently dropped, and a site that refuses an automated request comes back with the reason — `HTTP 403 — the site refused an automated request` — so you can tell a blocked site from an empty one.

### Where this is legal, and where the responsibility passes to you

This Actor reads pages a company published for the public to read. It touches no protected database and bypasses no access control, which is what separates it from scraping a directory or a marketplace.

What you do with the output is a different matter, and it is yours. Business contact details are still personal data under the GDPR when they identify a person — `jean.dupont@firm.fr` does, `contact@firm.fr` does not. If you prospect with them you become the data controller: you need a legitimate-interest basis, you must give the information notice at first contact, and in France you must screen against **Bloctel**. The Actor runs on your own Apify account and keeps nothing.

If you only need firmographic and technology data, turn `extractEmails` off. The technology detection, identifiers and social profiles carry no personal data at all.

### Who uses this

Sales teams enriching a domain list before outreach. Agencies and web studios finding sites on an ageing stack. SaaS vendors mapping who already runs the tools they integrate with. Recruiters and researchers building a sector map. Anyone who has a list of companies and needs the way in.

### Frequently asked

**Why did a site return nothing?**
The `error` field says which: a refused automated request, a connection failure, a redirect to something that is not HTML, or a `robots.txt` that disallows crawling. An empty result is never silent.

**Why so few phone numbers?**
Because many companies publish only a form. Numbers behind a `tel:` link are trusted first; loose digit runs in page text are often dates or prices and are treated with suspicion rather than reported as phones.

**Can I crawl deeper?**
Raise `maxPagesPerSite`. Fifteen pages finds the contact details on almost any site; a hundred is for mapping a large site's structure.

**Does it find people's names and job titles?**
No, and that is deliberate. This reads what a company publishes about how to reach it, not who works there.

# Actor input Schema

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

Company domains or full URLs, one per line — apify.com, https://www.example.fr, example.co.uk. Each is visited on its own website only; nothing else is consulted.

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

How many pages to read per site. Contact, about and legal-notice pages are always visited first, so 10 to 15 finds the details on most sites. Raise it for large sites that bury their contact page.

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

How many different sites to process at once. Pages within one site are always read one after another, so a single site is never hammered.

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

Obey each site's robots.txt and skip what it disallows. Leave this on: it is what makes this Actor safe to run on a client list, and a site that forbids crawling is reported as such rather than silently skipped.

## `extractEmails` (type: `boolean`):

Collect published email addresses, with obvious placeholders and image filenames filtered out. A generic address such as contact@ is chosen as the primary one when present, because it is the one meant for inbound contact.

## `extractPhones` (type: `boolean`):

Collect phone numbers, preferring those behind a tel: link since loose digit runs in page text are often dates or prices.

## `extractSocialProfiles` (type: `boolean`):

Collect LinkedIn, Facebook, Instagram, X, YouTube, TikTok, GitHub and WhatsApp links, ignoring share buttons.

## `extractTechnologies` (type: `boolean`):

Detect the CMS, e-commerce platform, JavaScript framework, analytics, chat, payment and marketing tools in use — Shopify, WordPress, HubSpot, Stripe, Klaviyo and around forty more. This is how sales teams find everyone running a given stack.

## `extractIdentifiers` (type: `boolean`):

Pick up VAT numbers and French SIRET numbers from legal-notice pages, which lets you join a website to an official company record.

## `maxSites` (type: `integer`):

Hard stop on how many sites this run processes. Set it low for a trial before committing a full list.

## Actor input object example

```json
{
  "domains": [
    "apify.com"
  ],
  "maxPagesPerSite": 12,
  "concurrency": 5,
  "respectRobotsTxt": true,
  "extractEmails": true,
  "extractPhones": true,
  "extractSocialProfiles": true,
  "extractTechnologies": true,
  "extractIdentifiers": true,
  "maxSites": 500
}
```

# Actor output Schema

# 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 = {
    "domains": [
        "apify.com"
    ]
};

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

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

```

## MCP server setup

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