LinkedIn People Search — Find LinkedIn URLs by Name

Turn any list of names into clean, structured LinkedIn profile data — no login, no cookies, no LinkedIn account, no risk to your own account.

Run a search like first_name: "Jorge", last_name: "Robles" and get back up to 500 matching public LinkedIn profiles with name, headline, location, and the canonical linkedin.com/in/... URL — ready to import into your CRM, lead list, or recruiting pipeline.

---

Why pay for this Actor?

Because doing it yourself is slow, fragile, and rate-limited:

• Manual Google search: ~30 seconds per name to click through, copy URLs, parse titles. For 50 names, that's 25 minutes of mind-numbing tab work.
• LinkedIn's own search: requires a logged-in account, throttles after a dozen searches, and frequently blocks scraping accounts.
• Building your own scraper: dealing with LinkedIn's anti-bot, proxy rotation, IP bans, HTML changes — a real engineering project.

This Actor turns 25 minutes into 25 seconds, with structured JSON/CSV output. At $0.9 per 1,000 profiles, you pay less than $0.01 to find 10 LinkedIn URLs. Cheaper than a single coffee for an afternoon's worth of manual lookup work.

---

What you get

For every matched profile:

Field	Description
name	Display name
headline	Job tagline (e.g. "Software Engineer at Acme")
profileUrl	Canonical LinkedIn URL — clean, deduplicated, ready to use
location	Geographic region when available
scrapedAt	ISO timestamp

Export to JSON, CSV, Excel, or HTML with one click. Import directly into HubSpot, Salesforce, Pipedrive, Notion, or any tool that accepts CSV.

---

How it works (in 3 lines)

1. You give it a first + last name.
2. The Actor runs Google discovery queries to find matching profiles.
3. You get a clean dataset back in 15-60 seconds.

No LinkedIn account needed. No risk to your own LinkedIn account. No browser automation, no cookies, no captchas.

---

Use cases

🎯 Sales prospecting — Got a list of 200 prospect names from a conference badge scan, a CSV from your sales team, or a webinar signup list? Pipe them through this Actor and get LinkedIn URLs for outreach.

🧲 Recruiting & sourcing — Match candidate names from job applications, alumni lists, or referrals to their LinkedIn profiles. Build a sourcing pipeline that doesn't depend on LinkedIn Recruiter seats.

💼 CRM enrichment — Add LinkedIn URLs to your existing contact records in HubSpot/Salesforce/etc. Run nightly to keep your CRM up to date with LinkedIn handles.

🔬 Market & academic research — Quantify how many "John Smiths" hold engineering roles in San Francisco. Build datasets for analysis.

🤖 Automation pipelines — Trigger this Actor from Zapier, Make, n8n, or Apify's own scheduler. Feed names in, get URLs out, no manual touch.

---

Pricing

Pay-per-result. You pay only for profiles the Actor actually returns:

Plan	Profiles per search	Price
Free	up to 25 per search	$0.00
Paid	up to 500 per search	$0.9 per 1,000 profiles

No subscription, no monthly minimums. Run it once, run it nightly, run it 10,000 times — you pay only for what you receive.

Free-plan users see a one-line warning when they ask for more than 25 results; the run still completes normally with the result set capped at 25.

---

Example input

{
    "first_name": "Jorge",
    "last_name": "Robles",
    "max_results": 50
}

Example output

{
    "name": "Jorge Robles",
    "headline": "Software Engineer at Acme",
    "profileUrl": "https://www.linkedin.com/in/jorge-d-robles",
    "location": "San Francisco Bay Area",
    "scrapedAt": "2026-06-02T15:30:00.000Z"
}

---

Performance

Search size	Typical runtime
25 profiles (free tier)	~10-15 seconds
50 profiles	~15-25 seconds
100 profiles	~25-45 seconds
300+ profiles	~60-90 seconds

---

Tips for getting the most out of it

• Common names cap at ~90-100 unique results. Searching "John Smith" with max_results: 1000 still returns ~95 — Google deduplicates aggressively. For high-volume lookups, use specific names.
• Uncommon names return faster and reach the cap. "Aravind Subramaniam" wraps up in 2-3 pages; "John Smith" takes 10+ pages.
• Start small, then scale. Try a max_results: 25 run on a known name to see the data shape, then go bigger.
• Combine with other Actors. Use this Actor's output as input to a profile-enrichment Actor for full data including experience, education, and avatars.

---

What's not in the output (be upfront)

• No profile photos — Google's public search results don't expose LinkedIn avatars consistently, and fetching them from LinkedIn directly triggers anti-bot blocks. We keep the output focused on what we can deliver reliably.
• No email addresses — LinkedIn doesn't expose emails publicly, and we don't guess them.
• No connection counts, follower counts, work history — those require fetching individual profile pages, which is unreliable and expensive. If you need that, pair this Actor with a profile-enrichment Actor.

The Actor is intentionally focused: fast, reliable, cheap LinkedIn URL lookup by name. That's the job it does well.

---

Limits & responsible use

• The Actor only returns information that is publicly accessible via Google search (no login, no scraping LinkedIn directly).
• Some profiles may be missing from results — Google indexes a subset of LinkedIn's public profiles.
• Use the data responsibly. Respect LinkedIn's Terms of Service and applicable privacy laws (GDPR, CCPA, etc.) when reaching out to or storing data about real people.

---

FAQ

Do I need a LinkedIn account? No. The Actor uses Google's public search index. No LinkedIn cookies or login required.

Will this get my LinkedIn account banned? No. The Actor never touches your account or makes any request from your IP. It runs entirely on Apify's infrastructure with rotated proxies.

Why don't I get exactly the max_results I asked for? Google caps unique results per query — typically 80-100 for very common names. The Actor returns whatever Google indexed; it won't pad results.

Can I run this on a schedule? Yes. Use Apify's built-in scheduler to run nightly/weekly. Combine with webhooks for downstream automation.

How fresh is the data? Results come from Google's live index. If LinkedIn updated a profile in the last hour, Google may not have re-crawled it yet. Most data is hours to days old.

Why is location sometimes null? Google's result snippet doesn't always include a location. The Actor pulls what's there but doesn't fabricate.

---

Support

Spotted an issue, hit a weird result, or want a feature? Open an issue on the Actor page and I'll take a look. Pull requests welcome.