LinkedIn Lead & Contact Finder (Google SERP)

Find B2B contacts from Google-indexed LinkedIn snippets in two modes:

• 🔑 Discovery — bulk-find leads by keyword / job title / industry. Strong, index-dependent yield; returns real phones/emails when Google indexed them.
• 🎯 Targeted — resolve specific people you already know (a profile URL, public-id / vanity slug, or name + company) into one structured row each: resolved name / headline / company / publicId, plus phone / email / website when Google indexed them (see the honest yield note below).

The Actor runs Google site: searches through the Apify GOOGLE_SERP proxy and extracts phones, emails, websites and social links from the result snippets. It then parses each result title into name / headline / jobTitle / company, derives the LinkedIn public-ID, seniority and country.

How it works (and its limits)

• It issues queries like site:linkedin.com "+44" "marketing director" (discovery) or site:linkedin.com/in/<slug> (targeted) to Google and reads the result snippets (title + description) that Google returns.
• It extracts contacts only from those snippets. It does not log in to LinkedIn, does not open or render LinkedIn profile pages, and does not use any LinkedIn cookie/session or private API.
• Because of this, a contact is found only when it already leaked into a Google-indexed snippet. Phone numbers are validated with Google's libphonenumber (phonenumbers): a candidate is emitted only if it parses to a valid number, so years, "500+ connections", follower counts and post IDs are rejected, never emitted. Unavailable values are null, never fabricated.

⚠️ Honest yield note — targeted mode

Targeted mode reliably returns the resolved identity (name / headline / company / publicId / canonical profile URL) and a website when one is in the snippet. It surfaces a phone or email only when Google indexed that detail into the snippet, which is uncommon for a specific profile — for a single /in/<slug> page Google usually shows LinkedIn's generic About card with no contact. Expect most targeted rows to resolve identity with phone/email null. Discovery mode (a role/industry keyword biased by a dial code) is the higher-contact-yield path. Targeted mode still adds value: it resolves and structures a known profile, and occasionally recovers a real contact.

Input

Pick a Mode, then fill the matching fields.

Field	Mode	Type	Description
mode	both	enum	discovery (default) or targeted.
keywords	discovery	array	Search terms — role + industry works best.
maxResults	discovery	integer	Max lead rows per keyword. Default 20 (1–10000).
requirePhone / requireEmail	discovery	boolean	Keep only leads with a phone / an email.
titleKeyword	discovery	string	Keep only leads whose title/name/headline/job/company contains this text.
targets	targeted	array	One entry per person: profile URL, public-id/slug, or full name.
company	targeted	string	Optional company added to name lookups to disambiguate.
maxPagesPerTarget	targeted	integer	Google pages (10 each) read per target. Default 2 (1–10).
platform	both	enum	Target site (Linkedin). Uses site:linkedin.com.
country	both	enum	A country (localises the search and keeps only that dial code) or "Any country" to keep every valid international number. Required.
useApifyProxy	both	boolean	Route through the GOOGLE_SERP proxy (recommended). Default true.

Example — discovery

{
  "mode": "discovery",
  "keywords": ["marketing director"],
  "country": "United Kingdom (+44)",
  "maxResults": 20
}

Example — targeted

{
  "mode": "targeted",
  "targets": [
    "https://www.linkedin.com/in/williamhgates",
    "satyanadella",
    "Melinda French Gates"
  ],
  "company": "",
  "country": "United States (+1)",
  "maxPagesPerTarget": 2
}

Targets are detected automatically: a URL/slug is searched as site:linkedin.com/in/<slug> (then a name fallback); a name is searched as site:linkedin.com "<name>" "<company>" (then without company).

Output

Both modes write to the same dataset with the same columns (values are null when not present in the snippet — never fabricated).

Field	Description
type	lead (discovery), profile (targeted resolved), or error
mode	discovery or targeted
keyword	Discovery keyword (null in targeted)
target	Targeted raw input (null in discovery)
inputMode	Targeted detection: url / slug / name (null in discovery)
found	Targeted: whether a LinkedIn result was indexed; discovery leads: true
name / headline / jobTitle / company	Parsed from the result title
seniority	Rule-based: C-Level / VP / Director / Manager / null
decisionMaker	true when seniority is C-Level / VP / Director
publicId	LinkedIn public-ID / slug
url	Profile / result URL
phone_number	Primary phone in E.164 (validated)
phones	All valid phones found in the snippet
phoneCountry	Country of the primary phone (from its prefix)
email / emails / emailDomain	Primary email, all emails, and the domain
website	First non-social external site in the snippet
socialLinks	Recognised social/messaging links (Instagram, WhatsApp, GitHub, …)
title / description	Raw result title and snippet
country / dial_code	Selected country and dial code
query	The Google query that produced the row
scrapedAt	ISO-8601 UTC timestamp of extraction

Billing

Pay-per-event: one row_result event per delivered row —

• Discovery leads (always carry a contact signal) → charged.
• Targeted rows that resolved the profile (found: true) → charged.
• Error rows and unresolved targets (found: false, no LinkedIn result indexed) → pushed uncharged.

Compliance

Use only for publicly available data and in accordance with applicable data-protection laws (e.g. GDPR) and each target site's terms. This Actor reads only public Google-indexed snippets; it does not bypass any login or access private data.

Keywords

linkedin lead scraper, linkedin contact finder, linkedin profile lookup, b2b lead generation, phone number extractor, email extractor, google serp scraper, site: dork search, sales prospecting, decision maker finder, job title search, e164 phone validation, targeted profile resolver, apify lead generation.