# Website Contact & Tech Scraper | SiteSignal (`reliable_quatrain/business-website-contact-tech-scraper`) Actor

Extract public business emails, phones, social profiles and website technology signals. Source evidence for every finding, one row per website, failed domains free.

- **URL**: https://apify.com/reliable_quatrain/business-website-contact-tech-scraper.md
- **Developed by:** [Trần Quốc Việt](https://apify.com/reliable_quatrain) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 website enricheds

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 Scraper | SiteSignal

Turn a list of business websites into structured contact and technology
profiles, with source links you can check. One row per domain, ready for CRM
enrichment, partner research or spreadsheet review.

![SiteSignal preview: public contact fields, technology signals and source evidence. Fictional sample data.](https://raw.githubusercontent.com/boyhoanghoi/site-signal-apify/main/assets/brand/sitesignal-store-preview.png)

### What SiteSignal extracts

- Public email addresses from mailto links, visible text and Organization JSON-LD.
- Published phone links and Organization JSON-LD telephone fields.
- Social profile links grouped by platform.
- Published business name, title, description and relevant contact pages.
- Contact forms observed on the fetched pages.
- Recognizable CMS, ecommerce, analytics and payment technology signatures.
- Evidence containing the observed value, source URL and extraction method.
- Flat company-field and contact exports for CRM mapping, with source pages.
- Per-page crawl diagnostics so a failed contact page is visible separately from a successful homepage.

Emails are observed addresses; mailbox existence and deliverability are not
verified. Phones are published observations. SiteSignal does not guess either
from company or person names.

Technology detection identifies signatures in fetched HTML. It is not a complete
or verified inventory of a company's software.

### How to use it

1. Add business website URLs in the Input tab.
2. Start with a few domains and the default three-page budget.
3. Run the Actor and inspect the contacts and evidence dataset views.
4. Choose **Company fields for CRM mapping** in the outputs for one flat row per
   saved website. Choose **All retained contacts and source pages** for one row per
   email, phone, social link or contact-form page. CSV and lossless JSON are provided.
   The regular dataset and spreadsheet-safe website CSV remain available.

The prefilled sample uses Python, Django and the Electronic Frontier Foundation.
These are real public websites, not paying customers or endorsements. Some pages
contain social links or contact forms without publishing an email; empty fields
are valid observations.

```json
{
  "websites": [
    {"url": "https://www.python.org/"},
    {"url": "https://www.djangoproject.com/"},
    {"url": "https://www.eff.org/"}
  ],
  "maxSites": 3,
  "maxPagesPerSite": 3,
  "respectRobots": true,
  "includeTechnology": true
}
```

Plain URL strings are also accepted. Duplicate domains are processed once.
The maximum is 1,000 input websites and five HTML pages per site. Set concurrency,
request timeout and per-site delay under Crawl limits. For remote API access,
use the generated examples in this Actor's API tab and keep your token private.

### Output

The default dataset contains one row per successfully processed website:

| Field | Meaning |
| --- | --- |
| `url`, `finalUrl`, `domain` | Requested website, final landing URL and normalized domain |
| `companyName`, `title`, `description` | Published organization and page metadata when available |
| `emails`, `phones`, `socials` | Observed contacts and normalized social profiles |
| `contactPageUrls`, `contactFormUrls` | Relevant contact pages and pages containing contact forms |
| `technologies` | Technology names, categories, evidence and source URLs |
| `evidence` | Contact values, source URLs and extraction methods |
| `pagesVisited`, `pagesChecked`, `observedAt` | Observation scope and time |
| `pagesAttempted`, `pageDiagnostics` | Attempt count and each requested page's status, final URL when available, HTTP status and failure message |
| `contactPageLimitReached` | True when the attempt limit left discovered same-site contact links unvisited; false does not imply a whole-site crawl |
| `status`, `warnings` | Result status and crawl limitations |

Failed websites are separate, nonbillable diagnostics. The Output tab includes a
run summary, diagnostics, a complete JSON report and spreadsheet-safe CSV.
Statuses can include `blocked`, `timeout`, `robots_disallowed`, `http_error` and
`network_error`. Check diagnostics when reconciling an input list.

#### Company and contact exports

`CRM_COMPANIES` / `crm-companies.csv` contain published company name, domain,
website, email, phone, source URLs, one link per social platform, contact-page
and form-page URLs, and technology names. Select the columns you want when
mapping your own CRM import. Company names are left empty when no published
organization name was found. The single email and phone are the first values
in deterministic alphabetical order, not a recommendation, ownership check or
deliverability result. Counts show when more contacts exist.

`CONTACTS` / `contacts.csv` retain all exported website contacts, with type,
platform, value, source pages and extraction methods. Email spelling variants
are deduplicated case-insensitively within a website; source evidence is kept.
The same contact on two different websites remains two observations. These
alternate exports use only saved website results and add no paid events.

CSV files escape formula-like values with an apostrophe; this includes a phone
beginning with `+`. Use the JSON versions to preserve exact contact strings in
an automated CRM integration. All contacts are marked `not_verified`. Review
the source pages and your CRM mapping before importing. No CRM is modified by
this Actor, and no messages or contact forms are submitted.

### Pricing and limits

The Actor's **Pricing tab** shows the current tariff. In pay-per-event mode, one
`website-enriched` event is recorded when a successful website result is saved to
the dataset. Failed or blocked websites do not create this event. The Actor
respects the run's spending limit and exports only saved results.

The unit is a successfully enriched website, not an email address. An accessible
site with no published email can still yield a completed result containing
metadata, social links or empty contact arrays. No contact count is guaranteed.

### Limitations

SiteSignal reads public HTML with ordinary HTTP requests. It does not execute
JavaScript, log in, solve CAPTCHAs, bypass blocked access or use a private contact
database. JavaScript-rendered details, externally embedded forms and obfuscated
addresses may be missed. A detected contact form must have email and message
fields and no password field. Its containing page is returned; form actions are
never submitted or fetched, including actions hosted by an external provider.

Per HTML page, output is capped at 100 emails, 50 phone numbers, 10 social
profiles per platform, 50 contact-page links, 50 contact-form page links and 500
evidence entries. Values are retained in deterministic discovery order, and
redundant evidence methods may be omitted to retain evidence for each contact.

Robots.txt is respected by default. Requests are bounded and paced. Only process
sites and data you are allowed to use. The Actor extracts information; it does
not send messages or submit contact forms. Review source evidence before using
the output in a business workflow.

### Support

Open an issue in the Actor's Issues tab. Include the public website URL, run ID,
expected field and observed behavior. Remove tokens and private customer data
from your report.

# Actor input Schema

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

One public business website URL per line, up to 1,000 inputs. maxSites limits processed domains.

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

Maximum number of unique websites to process. Your run spending limit may reduce this further.

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

Homepage plus same-site contact/support pages, up to this limit. More pages can find more public contacts but take longer.

## `includeTechnology` (type: `boolean`):

Look for recognizable CMS, ecommerce, analytics and payment signatures in fetched HTML. Detection is observational and may be incomplete.

## `respectRobots` (type: `boolean`):

Enabled by default. Pages excluded by robots.txt are skipped and reported in diagnostics.

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

Maximum websites in progress at once. Each site's pages are fetched sequentially.

## `timeoutSeconds` (type: `integer`):

Timeout for each HTTP request. Unreachable sites produce diagnostics, not billable rows.

## `minDelaySeconds` (type: `number`):

Minimum per-site pause in seconds. Robots crawl-delay may require a longer pause.

## Actor input object example

```json
{
  "websites": [
    "https://www.djangoproject.com/",
    "https://plausible.io/",
    "https://ghost.org/"
  ],
  "maxSites": 100,
  "maxPagesPerSite": 3,
  "includeTechnology": true,
  "respectRobots": true,
  "concurrency": 5,
  "timeoutSeconds": 20,
  "minDelaySeconds": 0.5
}
```

# Actor output Schema

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

No description

## `csv` (type: `string`):

No description

## `crmCompaniesCsv` (type: `string`):

No description

## `crmCompaniesJson` (type: `string`):

No description

## `contactsCsv` (type: `string`):

No description

## `contactsJson` (type: `string`):

No description

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

No description

## `diagnostics` (type: `string`):

No description

## `report` (type: `string`):

No description

# 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://www.djangoproject.com/",
        "https://plausible.io/",
        "https://ghost.org/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("reliable_quatrain/business-website-contact-tech-scraper").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://www.djangoproject.com/",
        "https://plausible.io/",
        "https://ghost.org/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("reliable_quatrain/business-website-contact-tech-scraper").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://www.djangoproject.com/",
    "https://plausible.io/",
    "https://ghost.org/"
  ]
}' |
apify call reliable_quatrain/business-website-contact-tech-scraper --silent --output-dataset

```

## MCP server setup

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

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/KgxuXmLMsWUuA8Jkw/builds/dxpmKC8A3juk5mwpd/openapi.json