Contact Info Scraper -Extract Business Contact Information
Pricing
from $3.50 / 1,000 results
Contact Info Scraper -Extract Business Contact Information
Looking to gather business contact information fast? Our Business Contact Info Scraper extracts emails, phone numbers, and social profiles like Facebook, Twitter, LinkedIn, and Instagram from websites at scale. Get accurate contact details quickly and efficiently with this powerful tool.
Pricing
from $3.50 / 1,000 results
Rating
3.6
(7)
Developer
codemaster devops
Maintained by CommunityActor stats
38
Bookmarked
1.1K
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Features
Share
What does Website Contact Scraper do?
Extract publicly displayed email addresses, phone numbers, social profile links, and candidate postal addresses from websites. Enter a website URL, set page and depth limits, and download one structured result per page.
Choose browser rendering, lightweight HTTP, or auto mode with selective browser fallback. Extract links to LinkedIn, X/Twitter, Instagram, Facebook, YouTube, TikTok, Pinterest, Discord, Snapchat, Threads, Telegram, Reddit and WhatsApp. It does not scrape private profiles, verify email deliverability or discover hidden information.
Enable mergeContacts to combine pages into one deduplicated row per starting URL. Enable enrichWebsiteData for explicitly published JSON-LD people/company details with source URLs. See docs/CONTACT_FEATURES.md for modes, output fields, limits and examples.
How to scrape website contact information
- Open the Actor's Input tab and add a public website you are authorized to crawl.
- Start with a small page limit and enable Stay within domain.
- Configure the offered residential proxy option, custom proxy URLs, or disable proxies for direct access.
- Run the Actor. Inspect the dataset, run log, and
RUN_SUMMARY. - Export results using Apify's JSON, CSV, or Excel dataset download options.
{"startUrls": [{ "url": "https://quicklifesolutions.com" }],"sameDomain": true,"maxRequests": 3,"maxRequestsPerStartUrl": 3,"maxDepth": 1,"considerChildFrames": true,"proxyConfig": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}}
The crawler favors contact/about/support links when choosing which discovered pages fit a small budget. It respects robots.txt, skips media-file links, and blocks heavy image/video/font requests while retaining scripts needed to render contact details.
What contact data is returned?
| Field | Meaning |
|---|---|
recordType | page for an extracted page or merged for a combined starting-URL result |
url, domain | Final page URL and registrable domain |
startUrl, depth, referrerUrl | Starting website, link depth, and referring page |
emails | Email addresses exposed in the rendered HTML |
phones | Higher-certainty phone links, such as tel: URLs |
phonesUncertain | Phone-like text that can include false positives |
linkedIns, twitters, instagrams, facebooks | Public social profile links; twitters includes supported X links |
youtubes, tiktoks, pinterests, discords | Additional supported social links |
snapchats, threads, telegrams, reddits, whatsapps | Public profile/community/invite links |
people, companies | Optional unverified website-published JSON-LD details with source URLs |
scrapedUrls, contactSources, scrapingModes, partial | Merged-row page evidence, modes used and failure indicator |
addresses | Parsed or raw address candidates with supporting text |
frameSources | HTTP(S) frame URLs contributing to frame inspection |
All social/contact array fields are present even when empty. Arrays are deduplicated within each page; the same business contact can legitimately appear on multiple pages. Each contact field is capped at 500 entries per page; address extraction is capped at 50 candidates.
Illustrative output using fictional contact details:
{"recordType": "page","url": "https://example.com/contact","domain": "example.com","startUrl": "https://example.com/","depth": 1,"referrerUrl": "https://example.com/","emails": ["contact@example.com"],"phones": ["+12025550123"],"phonesUncertain": [],"linkedIns": [],"twitters": ["https://x.com/example"],"instagrams": [],"facebooks": [],"youtubes": [],"tiktoks": [],"pinterests": [],"discords": [],"snapchats": [],"threads": [],"telegrams": [],"reddits": [],"whatsapps": [],"addresses": [],"frameSources": []}
Address confidence measures the presence of parsed address components; it is not a probability of correctness or postal verification. The parser is strongest on US-style addresses. Other candidate addresses can retain their raw text with low confidence.
Inputs and crawl limits
| Input | Runtime default | Supported range / behavior |
|---|---|---|
startUrls | Required | 1–1000 public URLs or supported URL-list sources |
maxRequests | 50 | 1–20000 scheduled pages globally; the example prefill is 5 |
maxRequestsPerStartUrl | 25 | 1–5000 pages per starting URL, including that URL |
maxDepth | 2 | 0–30; zero processes only seed pages |
sameDomain | true | Follow links only within the seed's registrable domain; private hosting tenants are distinguished |
considerChildFrames | true | Inspect at most 20 child/descendant frames, with a short body-readiness wait |
maxConcurrency | 3 | 1–20 browser pages in parallel |
navigationTimeoutSecs | 60 | 5–180 seconds |
bodyTimeoutSecs | 20 | 5–120 seconds |
proxyConfig | Residential proxy | Apify SDK proxy configuration |
scrapingMode | browser | browser, http, or auto; example prefill uses auto |
mergeContacts | false | Merge contacts across pages for each original starting URL |
enrichWebsiteData | false | Extract published Person/Organization JSON-LD when present |
Both strings and { "url": "..." } objects are accepted. Scheme-less websites default to HTTPS; existing HTTPS URLs are preserved. Credentials in URLs, non-HTTP(S) protocols, local/private/reserved IPs, and hostnames resolving to those addresses are rejected. These checks cover seed URLs, imported lists, navigations, redirects, and browser subresources. They do not replace deployment-level egress isolation against every DNS-rebinding or proxy-resolver race.
URL-list sources support requestsFromUrl or requestsFromUrls. Remote lists can contain a JSON array of strings/URL objects or simple newline/comma-separated URLs. Downloads have a 2 MB limit, a 20-second deadline, redirect validation, and a maximum of 100 list downloads. Expanded URLs are capped at 1000 and must fit maxRequests. Complex CSV formats are not supported.
How much does contact scraping cost?
Check this Actor's Pricing tab for the active rate and whether platform usage is included. Browsers, proxy traffic, and the number of pages affect processing costs. Start with a few pages and inspect usage before expanding the crawl.
Without merging, one dataset row represents a page result. With merging, one row represents the successfully extracted pages for a starting URL. Neither is a verified lead. Technical errors are retained in RUN_SUMMARY.failures rather than pushed as billable contact dataset items. Verify the active Pricing tab for the release's billing unit; do not infer cost-per-contact from email counts.
API access, schedules, and integrations
Use Apify's generated API tab to run the same input from your code. Apify also provides schedules, run monitoring, dataset exports, and integrations for recurring workflows. These are platform capabilities, not industry/keyword filtering features implemented by this Actor.
Frequently asked questions
Does this scrape contacts directly from private social media accounts?
No. It extracts contact details and social links published on the websites you supply. It does not log into social accounts or bypass private data access.
Why are some contacts missing or uncertain?
Obfuscation, images, delayed interaction, anti-bot pages, and site changes can reduce extraction. Email and phone deliverability are not verified. Treat phonesUncertain and address candidates as data requiring review.
Can frames include third-party contact details?
Yes. Frames may contain advertisements or embedded content from other organizations. Disable considerChildFrames when those details are not relevant. sameDomain controls followed page links, not whether an already loaded public iframe can be inspected.
How do partial failures appear?
Exhausted requests appear in RUN_SUMMARY.failures. Other extracted rows remain available; merged rows have partial: true where a page failed. The run fails after saving its summary when technical failures remain. Errors are not pushed to the contact dataset. Robots exclusions are reported as skipped requests.
Does stopping a run close its browser work?
An abort request stops dispatch and tears down the crawler/browser pool. URL-list downloads receive cancellation too. Platform status and shutdown still depend on Apify's termination lifecycle and any in-flight system operations.
Can I resume a run?
Crawlee checkpoints root quotas and completed pages. Resume only with the same input and runtime version. Dataset writes, queue writes, and checkpoints are not one transaction, so an abrupt crash can produce duplicates; deduplicate successful rows by the desired source-page key if exactly-once output is required. Start fresh when upgrading from the older Apify SDK 2 implementation.
Support and data handling
Use the Issues tab for bugs. Include the run ID, expected result, source URL, and input with tokens/proxy credentials removed. Support: Quick Life Solutions and Discord.
Only crawl sites and collect data you are authorized to use. Public contact data can still concern individuals. Respect site access rules and your applicable retention/use requirements. See CONTRIBUTING.md for local testing and audit/REPORT.md for verification evidence.