Use Website Contact Page Email & Phone Crawler with Python

Crawl a website's contact, about and team pages and collect its public emails, phone numbers, and social media profile links in one normalized record per site.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "defaultCountry": "",
  "includeNamedEmails": true,
  "maxConcurrency": 5,
  "maxPagesPerSite": 5,
  "maxSitesConcurrency": 3,
  "onlyWithContacts": false,
  "renderFallback": true,
  "requestTimeoutSecs": 15,
  "respectRobotsTxt": true,
  "smartPrioritise": true,
  "urls": [
    "https://apify.com"
  ],
  "useProxy": false,
  "useSitemap": true
}

Download input.example.json and save your reviewed copy as input.json.

Field	Type	Required	Description
`urls`	array	required	Websites to scan for public contact details. You can paste full URLs or bare domains; duplicates are removed.
`maxPagesPerSite`	integer	optional	Maximum number of pages to fetch per website. Contact, about, team and imprint pages are prioritised.
`maxConcurrency`	integer	optional	How many pages of the same website may be fetched in parallel.
`maxSitesConcurrency`	integer	optional	How many websites are scanned in parallel. Lower this if you hit rate limits.
`requestTimeoutSecs`	integer	optional	Maximum time to wait for one page before trying the next proxy tier.
`defaultCountry`	string	optional	ISO 3166-1 alpha-2 country used to interpret phone numbers written without an international prefix. Leave empty to infer from the website domain.
`useProxy`	boolean	optional	Start with the Apify proxy ladder instead of trying direct requests first. The actor always retries blocked requests through the proxy ladder automatically.
`smartPrioritise`	boolean	optional	Try common contact, about, team, imprint and support paths first, and queue contact-like links ahead of other internal links.
`respectRobotsTxt`	boolean	optional	Skip pages that the website's robots.txt disallows. Turn this off only when you own the site or have permission to crawl it.
`useSitemap`	boolean	optional	Read sitemap.xml and robots.txt sitemap entries to find contact and about pages that are not linked from the homepage.
`renderFallback`	boolean	optional	If plain HTML contains no email or phone, render up to two pages in a headless browser to capture contacts loaded by JavaScript.
`onlyWithContacts`	boolean	optional	Drop records for websites where no email, phone, social profile or contact form was found.
`includeNamedEmails`	boolean	optional	Include personal addresses such as jane.smith@company.com. When off, only role addresses such as info@, sales@ and support@ are kept.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/dVdgOhanoyG0MakwT/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

One record per scanned website with source-backed emails, E.164 phone numbers, social profiles, company name, address, contact forms, crawl diagnostics and status.

Questions before you run

Which inputs are required?

The published required fields are urls

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Open on Apify Full Actor reference

Generated from source build Tlb3yWd5vt2YU7382 and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.