Pricing

from $0.50 / 1,000 page reads

Try for free

Go to Apify Store

Website Contact Scraper – Emails, Phones, Socials

Try for free

Scrape a business's contact details off its website: every email address and validated phone number, social and messaging profiles, postal address and contact form — one row per site. It reads the page you give plus the few pages likeliest to carry contacts, because a home page rarely does.

Pricing

from $0.50 / 1,000 page reads

Rating

0.0

(0)

Developer

Simple Actors

Actor stats

Bookmarked

Total users

Monthly active users

3 days ago

Last modified

Categories

Lead generation

Automation

Business

type

Optional

"website" for a site that was read, "error" for one that could not be. An "error" row never carries an emails key at all — that is how a site with no contact details published (emails: []) is told apart from a site that could not be read.

Type:string | null

url

Optional

The address that was asked for, exactly as given (completed to https:// if it was written as a bare host).

Type:string | null

finalUrl

Optional

The address the site was finally read from, after redirects. Worth storing back: it is what says a record's website has moved.

Type:string | null

domain

Optional

The site's host without "www." — the identity to match a lead list on.

Type:string | null

statusCode

Optional

The HTTP status the entry page answered with.

Type:integer | null

name

Optional

The business's name, from structured data, the og:site_name tag, or the site's own title.

Type:string | null

description

Optional

What the site says it is, from structured data or the page's meta description.

Type:string | null

logo

Optional

An absolute URL to the site's logo. Read first from the page itself — the image at the top named "logo", usually inside the link back to the home page — because what a site declares as its logo is often a 32-pixel favicon, its site builder's default icon, or a photograph. When the page shows no logo image (a logo drawn as inline SVG has no address to give), the declarations answer instead, best first. logoSource says which one did.

Type:string | null

logoSource

Optional

Where logo came from, so a real logo can be told from a favicon without fetching it. header is the logo the page displays and is the one to trust; jsonld and og:logo are what the site declares; apple-touch-icon and icon are favicons, square and small; og:image is the site's share picture, which may be a photograph rather than a logo. Null when the site offers no logo at all.

Type:string | null

Options:

headerjsonldog:logoapple-touch-iconiconog:imagenull

Optional

The single best email address to write to, or null when the site publishes none. Chosen by rank: an address on the site's own domain beats a Gmail one, a general address (info@, hello@, contact@) beats a personal one, one found in a mailto: link beats one found in prose, and a noreply@ address is pushed to the bottom. It is always the first entry of emails, and it is also carried as contacts[0].email.

Type:string | null

phone

Optional

The single best phone number, in E.164 form (+12125551234), or null when the site publishes none. Always the first entry of phones, and also carried as contacts[0].phone.

Type:string | null

emails

Optional

Every usable email address found, best first. Each is { email, source, foundOn } — source being how it was found ("mailto" a mailto: link, "jsonld" the site's structured data, "cloudflare" a Cloudflare-obfuscated address that was decoded, "attribute" a data-email attribute, "obfuscated" a written-out form such as name [at] example [dot] com, "text" plain text on the page) and foundOn the page it was found on. An empty array means the site was read and publishes no email address, which for many businesses is the true answer. Absent entirely on an error row.

Type:array | null

phones

Optional

Every valid phone number found, best first. Each is { number, formatted, raw, type, country, source, foundOn } — number in E.164, formatted in readable international form, raw as it was written on the page, type what the numbering plan says it is (MOBILE, FIXED_LINE, TOLL_FREE …), country the number's own country. Numbers are validated against the real numbering plan of their country, so digits that merely look like a phone number do not appear here.

Type:array | null

contacts

Optional

Ways to reach a person or a department, best first. Each is { name, role, email, phone, source, sourceUrl }. The first entry always carries the site's best email and best phone together, so contacts[0].email and contacts[0].phone are the two fields to read if you read nothing else. Later entries are the groupings the site itself made — a contactPoint in its structured data, or an email and a phone number sitting in the same block of the page, with the heading above them as name — followed by every other address and number on its own.

Type:array | null

messaging

Optional

The same idea for channels that start a conversation rather than accounts to follow: messaging.whatsapp, messaging.telegram, messaging.messenger, messaging.skype, messaging.viber, messaging.line. A wa.me link also contributes its digits to phones, since it is a phone number the site published.

Type:object | null

socialProfiles

Optional

The same profiles as a list, including the extra accounts that social has no room for — a business with two Instagram accounts has one entry in social and two here. Each is { platform, url, handle }.

Type:array | null

address

Optional

The business's postal address, or null. { street, city, region, postalCode, country, raw, source } — the parts are filled in only when the site published them separately in structured data; raw is always the whole address as one line, and source says where it came from ("jsonld", "microdata", "address-element", or "text" when it was read out of the page's own words). A text-read address is the least certain of the four and is only accepted when the lines carry a house number, a street and a postal code in that order.

Type:object | null

contactFormUrl

Optional

The page carrying a form a person could write a message into — a form with a free-text field and an email field. Search boxes and newsletter signups are not counted. Useful for the many businesses that publish a form instead of an address.

Type:string | null

phoneCountry

Optional

The country used to read phone numbers that were written without a country code. Taken from "Country for phone numbers" if given, then the site's structured data, then its domain ending, falling back to US. If a site's numbers look wrong, this is the field to check first.

Type:string | null

rendered

Optional

True when at least one of the site's pages had to be opened in a real browser because the served HTML held nothing.

Type:boolean | null

pagesRead

Optional

Which pages were read to build this row, in the order they were read. Each is { url, statusCode, rendered, role } — role being "entry" for the address you gave, "linked" for a page the site's own links led to, "guessed" for a conventional path such as /contact tried only because nothing had been found.

Type:array | null

pagesReadCount

Optional

How many pages were read for this site, and the number of page events this row was charged for. Pages that turned out not to exist are not counted and not charged. It is at most "Pages to read per website", and usually below it.

Type:integer | null

error

Optional

Error rows only: why the site could not be read. "bad_input" the address was not usable, "not_a_website" the address is a social media profile rather than a website — give the business's own site, since a profile publishes no contact details to a logged-out reader, "unreachable" the host did not answer, "http_error" it answered with a status that is not a page, "challenge" it answered with a bot check or a refusal, "not_found" there is no page at that address, "render_failed" its scripts had to be run and the browser could not, "read_failed" anything else that stopped the read.

Type:string | null

errorDescription

Optional

Error rows only: the same thing in a sentence, naming the site and what it answered.

Type:string | null

retrievedAt

Optional

When the site was read, ISO 8601, UTC.

Type:string | null

Website Contact & Email Scraper: Emails, Phones & Socials

scrapers_lat/website-contacts-scraper

Turn company websites into contacts. Per site, extract public emails, phones, WhatsApp, 15 social profiles (LinkedIn, X, Facebook, Instagram, YouTube, TikTok and more), contact people, company name and address, plus the page each contact came from. Export to JSON, CSV or Excel.

Scrapers Lat

Website Contact & Email Extractor - Emails, Phones, Socials

benthepythondev/website-contact-extractor

Give it a list of websites and get the contact details for each: emails, phone numbers and social profiles, pulled from the homepage, contact and Impressum pages. Fast, no browser. Pay per site; small premium only when an email is found.

Ben

Google Maps Lead Extractor — Business Emails, Phones & Socials

juramoshkov/google-maps-lead-extractor

Turn a Google Maps search into a contact list: one row per business with a verified email, phone and social profiles scraped from its website, plus address, category, rating and reviews. Query like "dentists in Austin, TX". Leads mode bills only for rows that carry a contact.

Jura Moshkov

Contact Details Scraper - Emails, Phones & Socials

dami_studio/contact-details-scraper

Contact details are rarely on the homepage. They live on /contact, /about, and the /impressum German law requires carry a real email. A short crawl of them returns emails ([at] obfuscation included), phones, addresses, contact forms and 10 socials. $1.50 per 1,000 sites, flat.

Dami's Studio

Website Contact Scraper — Emails & Phones from a URL List API

nexgendata/contact-info-scraper

Paste a list of website URLs and extract every email, phone number, and social profile per domain — homepage plus auto-discovered contact, about, and team pages. A bulk URL-to-contact extractor: bring the domains, get one clean row per site. No API key. Pay per record.

NexGenData

125

Website Contact & Email Extractor

technicaldost/website-contact-extractor

Extract contact details from websites in bulk: emails, phone numbers and social profiles, plus the contact page. Turn a list of domains into a lead list.

Technical Dost Solutions

Website Email Contact Scraper

omkar-cloud/website-email-contact-scraper

Website Email & Contact Scraper to extract emails, phone numbers & social profiles from any website. Export contact data as JSON, CSV, or Excel.

Chetan Jain

518

5.0

Website Contact Scraper: Emails, Phones & Social Profiles

scrapemint/website-contact-scraper

Turn a list of websites into contact data. Fetches each site's homepage plus contact and about pages and returns emails, phone numbers, and social profile links, one row per site. Built for sales teams and marketers. Pay only for sites with contacts found.

Ken M

Website Contact Finder - Email, Phone, Contact Form

arkayen-labs/website-contact-finder

Find business contact details from any website: email address, phone number, or contact form. Lead enrichment that chains after Google Maps or any other scraper to add business emails to your list. Returns a reason when no contact exists, and charges only for contacts actually found.

Balaji Thukuntala

Bulk Contact & Email Scraper — Emails, Phones & Socials

jimmywhyte/website-contact-finder

Bulk email & contact scraper: feed a list of websites — a few or thousands from a spreadsheet, CRM, or API — and get every email, phone, and social profile from their homepage and contact pages. Each email is typed (sales, support, personal) and tagged with its source page. For lead generation.