# Website Contact Extractor - Emails, Phones & Social Links (`mossgreen_zed/website-contact-extractor`) Actor Paste company websites, get one clean row per site: emails (incl. Cloudflare-hidden), phones, LinkedIn/Facebook/Instagram/X/YouTube/TikTok, company name, address, and whether they use Google Workspace or Microsoft 365. Fast HTTP, no browser. $2 per 1,000 websites, failed sites free. - **URL**: https://apify.com/mossgreen_zed/website-contact-extractor.md - **Developed by:** [Joshua Temko](https://apify.com/mossgreen_zed) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 website scrapeds 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 Extractor: Emails, Phones & Social Links (+ Email Provider) **Turn a list of company websites into a contact list.** For each site, the Actor reads the homepage and the most useful **contact, about, team and imprint pages**, then returns **one clean row per website** with: - 📧 **Emails**: from `mailto:` links, page text, schema.org data, and even **Cloudflare-protected ("\[email protected]") addresses**, which most scrapers miss. Emails on the company's own domain come first. - 📞 **Phone numbers**: from `tel:` links and schema.org, with duplicates removed. - 🔗 **Social profiles**: LinkedIn, Facebook, Instagram, X/Twitter, YouTube, TikTok, Pinterest, GitHub, Threads, WhatsApp, Telegram and Yelp. - 🏢 **Company name and address**: from JSON-LD and Open Graph. - ✉️ **Email provider (bonus)**: Google Workspace, Microsoft 365, Zoho and more, plus any security gateway (Proofpoint, Mimecast and more). This helps you segment cold email. It's fast and cheap because it uses plain HTTP with no headless browser. It's polite too: it follows robots.txt by default and fetches one page at a time per site, with a delay. ### Who uses it - **Lead generation.** Enrich website lists from Google Maps, directories, trade-show exhibitor lists or CRMs. - **Agencies.** Get the email, phone and socials for every prospect in a niche. - **Recruiters, PR and partnerships teams.** Find the right contact channel for a company quickly. ### Input ```json { "websites": ["https://apify.com", "basecamp.com", "https://www.flowprosllc.com"], "maxPagesPerSite": 4, "detectEmailProvider": true, "respectRobotsTxt": true } ``` | Field | Description | |---|---| | `websites` (required) | URLs or bare domains, one per line. Duplicates are removed. | | `maxPagesPerSite` | The homepage plus the best contact-type pages (default 4, max 20). | | `detectEmailProvider` | Adds `emailProvider` from one DNS lookup (default `true`). | | `respectRobotsTxt` | Default `true`. | | `maxConcurrency`, `delayBetweenPagesSecs`, `requestTimeoutSecs`, `proxyConfiguration` | Advanced settings. | ### Output (one row per website) This is a real row from a local test run on 2026-10-30: ```json { "domain": "flowprosllc.com", "status": "ok", "companyName": "Flow Pros Plumbing", "primaryEmail": "info@flowprosllc.com", "emails": ["info@flowprosllc.com"], "primaryPhone": "+17272659639", "phones": ["+17272659639"], "facebook": "https://www.facebook.com/FlowprosLLC", "instagram": "https://www.instagram.com/flowpros.plumbing", "youtube": "https://www.youtube.com/@FlowProsLLC", "socials": { "facebook": ["..."], "instagram": ["..."], "youtube": ["..."], "yelp": ["https://www.yelp.com/biz/flow-pros-plumbing-saint-petersburg"] }, "emailProvider": "Microsoft 365", "pagesScraped": ["https://www.flowprosllc.com/...", "https://www.flowprosllc.com/contact/", "https://www.flowprosllc.com/about/"], "scrapedAt": "2026-10-30T18:18:59+00:00" } ``` Sites that can't be reached, return an error, or are blocked by robots.txt still get a row with `status` and `error`, **and you aren't charged for them**. ### Pricing (pay per event) **$2.00 per 1,000 websites** ($0.002 per `website-scraped` event). That covers up to 4 pages per site and the email-provider lookup at no extra cost. Failed sites are free. You can cap your spend with *Max cost per run*. ### Speed 100 websites with 20 in parallel took about 45 seconds in testing. On 8 reachable local-business sites (plumbers and dentists in Tampa, FL), 7 had a phone number and 4–5 had a real email (results varied slightly between runs). On 61 large-brand homepages, 25 had a public email and 43 had social links. ### FAQ **Does it work on JavaScript-only sites?** It reads the HTML the server sends. Most business sites (WordPress, Squarespace, Wix, Webflow, Shopify) include their contact details in that HTML. Sites built purely in React or Angular may return fewer results. **Is this legal?** It only collects business contact information that companies publish on their own websites. It follows robots.txt by default. You're responsible for using the data in line with GDPR, CAN-SPAM and the other rules that apply to you. **Can I combine it with other Actors?** Yes. Feed it the website column from a Google Maps or directory scrape, then run the results through an email verifier. # Actor input Schema ## `websites` (type: `array`): Company websites or bare domains, one per line (e.g. https://acme.com or acme.com). Emails like jane@acme.com also work - the domain is used. ## `maxPagesPerSite` (type: `integer`): Homepage + the best contact/about/team/imprint pages. 3-5 finds most contacts. ## `detectEmailProvider` (type: `boolean`): One DNS lookup per site. Free bonus field for cold-email segmentation. ## `respectRobotsTxt` (type: `boolean`): Skip pages the site disallows for bots. ## `maxItems` (type: `integer`): 0 = all. ## `maxConcurrency` (type: `integer`): How many websites to process at once. Pages within a site are fetched one by one. ## `delayBetweenPagesSecs` (type: `integer`): Politeness delay. ## `requestTimeoutSecs` (type: `integer`): Per-request timeout. ## `proxyConfiguration` (type: `object`): Optional. Most sites work without a proxy. ## Actor input object example ```json { "websites": [ "https://apify.com", "basecamp.com", "https://www.peninsularplumbing.com" ], "maxPagesPerSite": 4, "detectEmailProvider": true, "respectRobotsTxt": true, "maxItems": 0, "maxConcurrency": 10, "delayBetweenPagesSecs": 1, "requestTimeoutSecs": 20, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `results` (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 = { "websites": [ "https://apify.com", "basecamp.com", "https://www.peninsularplumbing.com" ] }; // Run the Actor and wait for it to finish const run = await client.actor("mossgreen_zed/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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "websites": [ "https://apify.com", "basecamp.com", "https://www.peninsularplumbing.com", ] } # Run the Actor and wait for it to finish run = client.actor("mossgreen_zed/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": [ "https://apify.com", "basecamp.com", "https://www.peninsularplumbing.com" ] }' | apify call mossgreen_zed/website-contact-extractor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,mossgreen_zed/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 ` 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/KAJsig74ZDA8Incsj/builds/GBWecW9HzWT0PJFiP/openapi.json