Website Contact Finder

Collect publicly exposed email, phone and social-profile references from selected websites or domains, keeping source-page evidence, confidence signals and crawl errors. Bound pages and depth, choose optional extraction or MX-domain checks and review each outcome before downstream use. Public contact discovery does not establish inbox ownership, deliverability or permission to contact someone.

Quick start

Use a known public contact page with a small page and depth cap, then inspect source URLs before expanding a website list. The existing W3C example is:

{
  "startUrls": [{ "url": "https://www.w3.org/contact/" }],
  "maxPagesPerDomain": 25,
  "crawlDepth": 2,
  "includeSitemap": true,
  "includePhones": true,
  "includeSocialLinks": true,
  "validateMx": false,
  "sameDomainOnly": true
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a small preconfigured input, then replace the websites with your own public targets.

• Full Website Contact Enrichment from Domains — Collect email, phone and social references with optional MX-domain evidence.
• Audit Public Email Source URLs — Focus on email references and their source pages with MX checks enabled.
• Find Phone Numbers from Websites — Include public phone references in a shallow crawl without MX checks.

What you get

A saved website or domain contact record with exposed references, source context, contact-page signals, crawl counts and non-fatal errors. Readable pages with no usable contact references produce no dataset row or contact charge. Their reasons appear in RUN_SUMMARY.skippedInputs. Confidence is a heuristic, and optional MX checks describe the email domain rather than proving a working mailbox or identity.

Who is it for?

• Company-data teams reviewing public contact evidence before enriching existing records.
• CRM operations teams retaining source links and uncertainty before imports.
• Business researchers inspecting a bounded group of known websites.
• Data developers building auditable contact-reference datasets and their own downstream review workflows.

How you can use the data

• Inspect a known W3C contact page. Use the existing w3.org/contact example and keep each email's sourceUrl, matchedSignals and confidence. A visible mailto reference supports a page citation rather than an ownership or consent guarantee.
• Prepare a controlled company-domain enrichment. Use your known domains with modest page and depth caps and same-domain scope. Retain seedUrl, normalized domain and errors before joining outcomes to your CRM, without silently correcting misspelled domains or inventing missing contacts.
• Select only the evidence types you need. Turn phones or social links on when useful and leave MX checks off unless domain mail-routing context matters. A linked social URL is a public reference, not independent verification that every account belongs to the company.
• Review gaps before downstream outreach. Separate a readable site with no exposed contacts from fetch failures and partial coverage. Keep source evidence in your own spreadsheet or data pipeline, applying your own privacy, anti-spam and permission review rather than automatically contacting extracted addresses.

Input settings

Setting	JSON key	Use it for	Example
Start URLs	startUrls	Full public URLs such as homepages, contact pages, or company website URLs.	[{"url":"https://www.w3.org/contact/"}]
Domains	domains	Plain domains when your source list has values like example.com.	["example.com"]
Maximum pages per domain	maxPagesPerDomain	Cap pages crawled per website to control runtime and spend.	25
Crawl depth	crawlDepth	Number of link levels to follow from each seed URL.	2
Check sitemap.xml	includeSitemap	Use sitemap URLs to discover contact, about, team, legal, and support pages faster.	true
Stay on the same domain	sameDomainOnly	Only follow links on the same website domain.	true
Extract phone numbers	includePhones	Find public phone numbers in page text.	true
Extract social links	includeSocialLinks	Find LinkedIn, Facebook, Instagram, X/Twitter, YouTube, and TikTok profile links.	true
Validate email domains with MX lookup	validateMx	Check whether each email domain has mail exchange records.	false
Proxy configuration	proxyConfiguration	Optional Apify Proxy settings. Leave disabled for normal public websites.	{"useApifyProxy":false}
Resume unfinished sources	resumeUrls	Continue source URLs recorded in PENDING_SOURCES after a run reaches its time reserve.	["https://example.com/contact"]

Output data

The existing illustrative row shows source-bound structure rather than a new contact collection:

{
  "domain": "w3.org",
  "seedUrl": "https://www.w3.org/contact/",
  "sourceUrl": "https://www.w3.org/contact/",
  "contactPageType": "mailto",
  "emails": [
    {
      "email": "contact@w3.org",
      "normalizedEmail": "contact@w3.org",
      "sourceUrl": "https://www.w3.org/contact/",
      "confidence": 100,
      "mxValid": null
    }
  ],
  "phones": [],
  "socialLinks": {},
  "matchedSignals": ["email_regex", "mailto"],
  "pagesCrawled": 3,
  "firstSeenAt": "2026-06-22T00:00:00.000Z",
  "errors": []
}

Field	Description
domain	Normalized website domain
seedUrl	Original URL used to start the crawl
sourceUrl	Best page where contact data was found
contactPageType	Signal such as contact, about, mailto, or general
emails	Email records with confidence and source URL
phones	Public phone numbers found on pages
socialLinks	LinkedIn, Facebook, Instagram, X/Twitter, YouTube, TikTok
matchedSignals	Signals that explain why the record was matched
pagesCrawled	Number of pages visited for the domain
errors	Non-fatal crawl or fetch errors

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing:

• start is charged once when a run starts.
• contact is charged for each saved website or domain record containing usable email, phone or social references. Empty outcomes and unavailable pages have no contact charge. The start fee can still apply.

Rates vary by Apify plan. See the live Pricing tab for current rates and the exact charge conditions.

Tips for best results

• Start from known home or contact pages. Targeted URLs can reduce unnecessary crawling.
• Keep page and depth caps modest. A limit is a work bound rather than a promise of complete site coverage.
• Retain same-domain scope for company review. Inspect source links before joining contacts to a record.
• Treat MX as domain evidence. It does not verify a mailbox, inbox owner or consent to receive messages.
• Review sourceUrl and errors. Confidence is heuristic. Check RUN_SUMMARY for empty, failed or deferred websites.

Limits and caveats

Use at most 100 combined start URLs, domains and resume URLs. Each page is limited to 4 MiB of decompressed content and each website to 10,000 contact signals. Choose a targeted contact-page URL for very large sites. Processing stops within the platform timeout or a 14-minute processing budget, whichever is shorter, with time reserved for shutdown.

Readable pages without usable contacts and pages returning HTTP 404 or 410 succeed without a dataset row. Check RUN_SUMMARY.skippedInputs for reasons. Access-denied pages, verification interstitials and unresolved extraction errors remain actionable failures, not proof of privacy or deletion. Mixed batches retain useful records. If every website fails unexpectedly, the run fails. Essential storage and billing errors also fail the run. Targets are used as supplied. Misspelled domains are not silently corrected.

The actor extracts public information from accessible web pages and does not access private or restricted data. Email confidence scores are heuristics based on source page and contact signals. Review results and follow applicable privacy, anti-spam, and marketing requirements before outreach.

Forms, scripts, images and restricted pages can hide contacts that are not available as readable public page text. Fewer pages than the limit can mean no further eligible links or the configured depth has been reached, rather than an exhaustive website check.

Source URLs from PENDING_SOURCES can be supplied explicitly through resumeUrls after the time reserve is reached. This is a later run rather than automatic notification or cross-run history. Keep the intended crawl limits and source context when repeating work, and inspect each run's outcomes and charges.

Privacy and data handling

This Actor only requests the permissions needed to run the input you provide. It uses your input (such as URLs, search terms, identifiers, filters, and limits) only to fetch the requested public data from the relevant source site or API for this Actor, then writes results to your Apify dataset/key-value store.

Data may pass through Apify platform services and Apify Proxy during the run, and requests are sent only to the target site or public data provider required for this Actor's results. FetchCat does not send your inputs or outputs to advertising networks, data brokers, or model-training services, and does not retain run data outside Apify storage after the run except when you explicitly share run details for transient support debugging.

You are responsible for using this Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs. Review the output before storing, sharing, or combining it with other data.

Automation and integrations

Use saved outcomes in your own CRM enrichment, Google Sheets exports, lead-scoring review or internal dashboards. Keep evidence URLs and unresolved errors with imported records. Decisions about outreach, contact ownership or identity belong to your review process.

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The existing Node.js and Python examples wait for completion and print the dataset ID. Use that ID with the Dataset API or client to read saved rows, with pagination for larger exports. The cURL example starts a run and returns its details. Wait for completion before reading its dataset.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~website-contact-finder/runs?token=APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://www.w3.org/contact/"}],"maxPagesPerDomain":25}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/website-contact-finder').call({
  startUrls: [{ url: 'https://www.w3.org/contact/' }],
  maxPagesPerDomain: 25
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/website-contact-finder').call(run_input={
    'startUrls': [{'url': 'https://www.w3.org/contact/'}],
    'maxPagesPerDomain': 25,
})
print(run['defaultDatasetId'])

MCP and AI agents

You can ask your AI assistant to collect data with Website Contact Finder and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Website Contact Finder. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/website-contact-finder"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Website Contact Finder by Fetch Cat, or give it the identifier fetch_cat/website-contact-finder.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Website Contact Finder to collect public email and source-page references from https://www.w3.org/contact/ with a three-page per-domain cap, depth 1, same-domain scope and MX checks off. Keep confidence and errors without claiming inbox ownership.”
• “Collect public phone and social-profile references from https://www.w3.org/contact/ with a three-page cap, depth 1 and same-domain scope. Keep the page evidence without assuming each linked account's identity or contacting anyone.”
• “Retrieve public contact outcomes for example.com with a two-page per-domain cap, depth 1 and MX checks off. Preserve a no-contact or fetch-failure outcome instead of inventing addresses or silently changing the domain.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can it crawl multiple websites in one run?

Yes. Add entries to startUrls or domains, with at most 100 combined entries across those fields and resumeUrls.

Does it validate every email address?

It can optionally validate the email domain with MX records. It does not send email or verify inbox ownership.

Does it charge per page?

No. The current design charges per saved website/domain contact record, not per crawled page.

Can it find social links?

Yes. It detects common public social profile domains including LinkedIn, Facebook, Instagram, X/Twitter, YouTube, and TikTok.

Troubleshooting

Why did a website return no contacts?

Some websites hide contact information behind forms, images, scripts, or login walls. Increase maxPagesPerDomain, provide a known contact page, or review the errors field.

Why are there fewer pages crawled than my limit?

The Actor stops when it finds an email or phone, runs out of eligible links, reaches the configured depth or page cap, or approaches its time budget. Social links are best-effort enrichment, not an exhaustive directory.

Should I enable proxies?

Most public websites do not need proxies. Leave proxy settings disabled unless a target blocks direct requests.

Related Actors

Related Actors from the same account:

• Facebook Pages Scraper — Collect available public Facebook Page details and visible post links.
• TikTok Profile Scraper — Collect available public TikTok profile details and video metadata.
• YouTube Channel Details Scraper — Collect public YouTube channel descriptions, identifiers and available audience counts.
• Threads Profile & Posts Scraper — Collect available public Threads profile details and posts.
• Website Content Crawler Lite — Collect text, Markdown, HTML, metadata and discovered links from public website pages.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥