# Business Website Contact & Lead Extractor (`winning_moonstone/business-website-contact-lead-extractor`) Actor Extract public business emails, phones, social profiles, structured addresses, and contact forms from company websites. - **URL**: https://apify.com/winning\_moonstone/business-website-contact-lead-extractor.md - **Developed by:** [月 明](https://apify.com/winning_moonstone) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $5.00 / 1,000 website scanneds 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 ## Business Website Contact & Lead Extractor Turn public company websites into structured, reviewable business-contact records. The Actor scans each supplied homepage and prioritizes same-site pages such as Contact, About, Team, Support, Imprint, and Locations. ### What it extracts - Public email addresses with role/named classification, domain-match evidence, source pages, and free-provider labels - Phone numbers from `tel:` links and carefully filtered visible text - LinkedIn, Facebook, Instagram, X/Twitter, YouTube, TikTok, and GitHub profiles - Postal addresses explicitly published in Schema.org JSON-LD - Contact forms, company name signals, processed pages, and page-level errors - A conservative `contactConfidence` label based only on collected evidence The Actor does not guess email addresses, enrich personal identities, bypass logins, or scrape private pages. Off-domain/free-provider named-email collection is off by default; public named emails on the company's own domain can still be returned. ### Quick start ```json { "startUrls": [ {"url": "https://www.iana.org/contact"}, {"url": "https://example.com/"} ], "maxWebsites": 2, "maxPagesPerWebsite": 5, "maxDepth": 1, "includePersonalEmails": false, "timeoutSeconds": 20 } ``` Click **Start** to run the included example, then open **Output**. One dataset record is written per successfully scanned website. The table includes copyable `emailAddresses` and `phoneNumbers`; the detailed `emails` and `phones` arrays include evidence and source URLs. Export the dataset as JSON, CSV, or Excel. `OUTPUT` in the default key-value store contains the run summary and errors for websites that produced no usable page. A run in which every website fails is marked **Failed**, with the reasons preserved in `OUTPUT`. A website may scan successfully but contain no contact details. ### Safety and predictable cost - Public HTTP(S) URLs and standard ports only - DNS/IP checks block localhost, private, link-local, reserved, and other non-global targets; connections use a validated address while preserving HTTPS certificate verification - Redirect destinations are revalidated; maximum five redirects - `robots.txt` is respected; unverifiable robots rules fail closed - At least one second between requests to the same origin - Maximum 2 MB per HTML response and 512 KB for robots.txt - Maximum 50 websites, 10 page attempts per website (failed requests count), link depth 2, and roughly 4.5 minutes per run - Pay-per-event budget is checked before scanning, and the SDK saves and charges each record together; the last affordable record is retained Start with one or two websites and a spending limit. Increase limits only after reviewing data quality. ### Output notes `contactConfidence` means evidence density, not commercial quality or deliverability: - `high`: at least five pieces of public contact evidence - `medium`: two to four - `low`: one - `none`: no contact evidence on successfully scanned pages Email and phone counts are uncapped totals; saved detail arrays may be truncated according to input limits. Every email and phone includes the page URLs where it was observed. In large batches, the run time budget may stop processing before every website is scanned. Check `unprocessedWebsites` and `stoppedByTimeBudget` in `OUTPUT`, then run the remaining URLs in a new batch. Invalid URLs produce an explicit input error instead of being silently dropped. ### Pricing When monetization is enabled, the configured price is **$0.005 per successfully scanned website ($5 per 1,000 websites)**. A website scan includes up to your configured page limit. Failed websites produce no charged result. Successfully scanned sites without publicly available contacts still count as a website scan. Always check the live Pricing tab before running. ### Limitations - Server-rendered HTML only; JavaScript-only content is not rendered - Contact data can be outdated or intentionally absent - Phone formats vary globally, so ambiguous digit strings are deliberately omitted - Addresses are returned only from explicit structured data to avoid inventing locations - Domain matching is a transparent hostname comparison, not a legal or ownership assertion - Users remain responsible for website terms, privacy law, marketing consent, and permitted use For a reproducible support report, include the public URL, run ID, expected field, and actual field. Do not include passwords, private pages, or sensitive personal data. # Actor input Schema ## `url` (type: `string`): A public company website. Used when Batch website URLs is empty. ## `startUrls` (type: `array`): Up to 50 public company websites. Duplicate domains are removed. ## `maxWebsites` (type: `integer`): Hard cap for one run. ## `maxPagesPerWebsite` (type: `integer`): Maximum page attempts, including failures. Contact/about/support links are prioritized. ## `maxDepth` (type: `integer`): 0 scans only supplied URLs; 1 is recommended; 2 is the maximum. ## `includePersonalEmails` (type: `boolean`): Off by default. Named emails on the website's own domain are still returned; unrelated free-provider and off-domain named emails are omitted. ## `timeoutSeconds` (type: `integer`): Maximum time for one HTTP request, including response download. ## `maxEmailsPerWebsite` (type: `integer`): Maximum email details stored for each website; total counts remain available. ## `maxPhonesPerWebsite` (type: `integer`): Maximum phone details stored for each website; total counts remain available. ## Actor input object example ```json { "url": "https://www.iana.org/contact", "startUrls": [], "maxWebsites": 20, "maxPagesPerWebsite": 5, "maxDepth": 1, "includePersonalEmails": false, "timeoutSeconds": 20, "maxEmailsPerWebsite": 100, "maxPhonesPerWebsite": 50 } ``` # Actor output Schema ## `summary` (type: `string`): No description ## `dataset` (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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("winning_moonstone/business-website-contact-lead-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("winning_moonstone/business-website-contact-lead-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 '{}' | apify call winning_moonstone/business-website-contact-lead-extractor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,winning_moonstone/business-website-contact-lead-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 ` 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/F60sY7bzvOowKZzKc/builds/9gqZ392i40wTWhh76/openapi.json