Use Google to Find LinkedIn Profiles + Emails

Sasha Bouloudnine●
7 Sept 2026

(updated)

●
11 min read
Type a name into Google and a LinkedIn profile is usually the first result. That's no accident: Google has indexed nearly every public profile on the platform.
Tweet: LinkedIn profiles many times appear first in a Google name search
LinkedIn's own search, meanwhile, sits behind a login β€” and caps you at around 1,000 results per search, less once the free account's commercial use limit kicks in.

The paid tools that promise a way around it mostly wrap a trick you can run yourself.

The trick: Google is the API. In this guide, I'll show you how to:

  1. turn Google into a LinkedIn search engine with X-ray dorks;
  2. pull public emails out of profiles with copy-paste strings;
  3. run the whole thing at scale β€” from your terminal or your AI agent.
LinkedIn ships a genuinely powerful advanced search. So why route around it? Three reasons.

First, Google needs no login. LinkedIn's search shows nothing until you sign in β€” and plenty of people don't want an account at all.

LinkedIn's signup wall: search and profiles demand an account when you're logged out
Second, you stay invisible. Open a profile while signed in and LinkedIn tells that person you looked. Read the same page from Google's index, logged out, and nobody is notified.
LinkedIn's Who viewed your profile panel β€” even free accounts see their last five visitors

Third, Google reads the whole page. LinkedIn's search matches a handful of fields β€” name, title, school. Google indexed every word, so a phrase buried in someone's About section is searchable.

The same About-section phrase: LinkedIn's search returns nothing, Google returns the profile

That last detail powers everything below. Time to aim Google at LinkedIn.

The copy-paste X-ray dork library

Every public profile lives under linkedin.com/in/. The site: operator restricts Google to exactly those pages:
site:linkedin.com/in/ "growth marketer" "London"
f
site: is a bouncer β€” it throws out everything that isn't a profile, so you only see people.
Stacking more operators on top is what recruiters call X-ray search, and we go deeper in our full X-ray search guide.
Real Google SERP for site:linkedin.com/in/ growth marketer London β€” a clean page of public profiles

Here are the recipes worth saving. Swap the quoted parts for your own.

By role and location

site:linkedin.com/in/ "Head of Sales" "Berlin" intitle:"software engineer" site:linkedin.com/in/ "remote"
f
intitle: forces the word into the page title β€” and a profile's title is usually the person's job. It's the precision knob for role searches.
For country targeting, swap the domain itself: site:de.linkedin.com/in/ returns Germany-based profiles, site:fr.linkedin.com/in/ France, and so on.
Google results for intitle software engineer site:linkedin.com/in/ remote β€” every title carries the role

By company, current or past

site:linkedin.com/in/ ("Stripe" OR "Adyen") "product manager" site:linkedin.com/in/ "ex-Google" "founder"
f
OR (capitals matter) widens the net across several companies at once.
And since a profile lists a whole career on one page, you can target where someone used to work β€” gold for alumni outreach. For a broader map of who sits where, see our LinkedIn people directory guide.
Google results for site:linkedin.com/in/ ex-Google founder β€” the alumni-outreach search

Stack exclusions to kill noise

site:linkedin.com/in/ "recruiter" "fintech" -intitle:"jobs" -"we are hiring"
f
Each minus sign removes a slice of clutter β€” job boards, open-role posts. You're left with people, not adverts. Google keeps a whole catalog of operators if you want more.
Wrap multi-word phrases in "quotes" so Google matches them exactly. Without quotes, Head of Sales also matches pages that merely mention head, sales, and of. Quotes are the difference between a shortlist and a mess.

Roles and companies draw the map. The prize most readers came for is the email.

Pull emails from LinkedIn with Google

r/LeadGeneration: Best way to extract LinkedIn personal contact emails? β€” free tools cap out fast or require a paid plan

People paste an email into their profile more often than you'd think β€” the About section, the contact box, sometimes the headline itself.

If it's on the public page, Google indexed it. Quote a fragment and only profiles containing it come back:

site:linkedin.com/in/ "growth" "@gmail.com" site:linkedin.com/in/ "founder" "@gmail.com"
f
Swap the suffix for any provider β€” "@yahoo.com", "@outlook.com", "@protonmail.com". Chasing work emails instead? Search the domain:
site:linkedin.com "@stripe.com"
f
And the same trick finds phone numbers. Swap the email fragment for a dialing code β€” "+44", "+1" β€” and published numbers surface the same way.
Google results for site:linkedin.com/in/ marketing +44 β€” phone numbers visible in the snippets

These email dorks are what people type into Google every day β€” we see the exact strings in our own Search Console data.

It's the highest-intent corner of this topic, and the one competitors skip.

Google results for site:linkedin.com/in/ growth @gmail.com β€” full email addresses sitting right in the snippets

One catch. This surfaces personal inboxes, not corporate ones. We ran the same dork across 20 large employers and five email providers: personal addresses leaked on most profiles, company domains barely showed one.

Chart: personal emails leak on most profiles while corporate addresses rarely appear
You rarely need to click through. The name, headline, and often the email sit right in Google's snippet β€” handy, because logged-out profile clicks increasingly hit a signup wall. There are other ways to extract emails from LinkedIn too, including a no-login LinkedIn email scraper. And always verify an address before you send: a found email isn't a deliverable email.

A handful of these you can copy by hand. A whole market, you can't β€” which is where scale comes in.

Do it at scale β€” the real workflow

For a few lookups, skip the tooling. Claude and ChatGPT can run a dork and hand back the top hits β€” for five leads, that's the fastest path.

ChatGPT returns a handful of LinkedIn profiles with public Gmail addresses β€” a sample, not a list

Past a few dozen, three things break at once. You want the whole list, not a sample. You want a structured file, not a chat reply. And you want it repeatable next week.

lobstr.io's Google Search scraper takes any dork you'd type into Google and returns every result as a clean CSV β€” paginating past the cap, rotating around the blocks.
lobstr.io Google Search scraper turning a search query into a clean CSV export

No code first. Four clicks:

  1. Create a squid with the Google Search Scraper.
  2. Paste your dork as the search keyword.
  3. Hit Launch.
  4. Download the CSV.
The full click-by-click walkthrough lives in how to scrape Google with no code.
The lobstr.io console mid-run β€” the Google Search Scraper collecting results for the dork, live log visible
Prefer the terminal? Install the CLI, drop in your API token, run the dork:
pip install lobstrio lobstr config set-token YOUR_API_TOKEN lobstr go google-search-scraper \ 'site:linkedin.com/in/ intitle:marketing "@gmail.com"' \ -k keyword -p max_pages=10 \ -p country="United States" -p language=English \ -o leads.csv
f
Terminal: lobstr go downloads 100 results to leads.csv in 16 seconds
That single dork returned 100 profiles, 56 of them with a public email, in 16 seconds. Real numbers from my own run β€” every row carries the profile's URL, title, and snippet.
One cleanup step. There's no email column; the address sits inside the description field. A spreadsheet regex pulls it out:
=REGEXEXTRACT(H2, "[\w.-]+@[\w.-]+\.\w+")
f

Fill the formula down and a page of messy snippets becomes a clean list of names, URLs, and addresses.

That's exactly how we built this public Google Sheet β€” 2,502 profiles from our test dorks, 370 emails extracted.
The public Google Sheet: 2,502 profiles with the extracted email column highlighted

The regex only catches addresses Google shows in full. When the snippet truncates one, the address still sits on the profile page β€” that's what the no-login profile scraper is for.

If you live in Claude, connect the two. The lobstr.io MCP server lets your agent drive the actual scraper β€” the full paginated export, not its five-link web search:
claude mcp add --transport http lobstr https://mcp.lobstr.io/mcp
f

Then ask in plain English: "Run that X-ray dork through the Google Search scraper and give me a CSV." The agent writes the query, launches the run, and returns the whole table.

Claude driving the lobstr.io Google Search scraper through the MCP β€” the dork goes in as plain English

The scraper rotates proxies and solves the CAPTCHAs that stop a manual or agent-chat workflow cold at volume. You paste the dork; it deals with the blocking.

If you'd rather skip Google altogether, my LinkedIn MCP guide pulls profiles with work emails straight from Claude.

Powerful enough that a fair question follows: are you actually allowed to do this?

The honest answer has two layers, and it's worth getting right β€” we go deeper in is LinkedIn scraping legal? (Context, not legal advice.)
Scraping public data isn't "hacking." In hiQ Labs v. LinkedIn, the Ninth Circuit held that collecting publicly accessible data doesn't violate the Computer Fraud and Abuse Act, the US anti-hacking law.
California Lawyers Association: Ninth Circuit holds data scraping is legal in hiQ v. LinkedIn

But terms of service still bind you. hiQ ultimately lost β€” not on hacking grounds, on breach of contract.

It had LinkedIn accounts, so it had agreed to LinkedIn's terms. The 2022 judgment ended in a permanent injunction plus a 500,000 dollar payment.

The lesson maps straight onto this guide: work from Google's public index, logged out, and you never agree to LinkedIn's terms in the first place.

And scraping Google's own results just survived a court challenge. In Google v. SerpApi, Google tried to use copyright law to shut down a company that scrapes its search results.

In July 2026 a federal judge threw the claim out, ruling Google can't weaponize copyright to block the scraping of uncopyrighted web data.

Search Engine Journal: court dismisses Google's DMCA claims against SerpApi

Google amended its complaint in August, so it isn't fully over β€” but the core theory lost.

On privacy, treat what you store like the business data it is.

Collecting work contact details for relevant outreach is generally defensible under GDPR's legitimate-interest basis. Keep it minimal, skip sensitive fields, honor every opt-out.

None of this is legal advice. Operating at real scale, or in a regulated industry? Run the workflow past your legal team first.

The method has edges too. Knowing them tells you when to switch tools.

The limits of the Google method

Fire off many queries quickly and Google serves a CAPTCHA. Manual searching hits that wall fast.
Google 'unusual traffic' reCAPTCHA wall β€” what heavy dorking runs into

Any single query also tops out at a few hundred results. For a big market, split the dork by city or role and run the variants.

Profiles set to block search engines never appear at all β€” Google can only show what it's allowed to crawl.

LinkedIn public profile settings β€” the visibility toggle that removes a profile from Google entirely

And the honest ceiling is the email itself.

I counted it in Sales Navigator: "@gmail" alone returns about 384,000 profiles, and adding Yahoo, Hotmail, iCloud and AOL lands around 635,000 β€” against LinkedIn's billion-plus members, well under one percent.

That count even runs low: Sales Nav's keyword search misses profiles I verified by hand. Double it for the misses and you still stay under one percent.

Sales Navigator keyword search for @gmail β€” about 380K results out of a billion-plus members

We also checked who those rare publishers are, across 2,000-plus profiles our runs collected.

Chart: executives are 13% of profiles but 2% of email publishers; freelancers double their share

Executives made up 13% of the crowd but 2% of the publishers. Freelancers and consultants doubled their share β€” people who want inbound.

The skew is geographic, too: publishers over-index in India, Nigeria, and Pakistan, even in our US-localized runs.

For executives and verified work emails, our Sales Navigator leads scraper pushes past that ceiling with a far higher hit rate.

Before you fire off your first dork, the questions everyone asks:

FAQ

Can someone tell if I find their LinkedIn profile through Google?

No. Reading the Google result β€” title, snippet, even the indexed page β€” leaves no trace. LinkedIn only logs a view when you open a profile while signed in, which is the whole point of working from Google's index.

Does "@gmail.com" really work as a search filter?

Yes β€” as a plain quoted phrase. Type "@gmail.com" straight into the query and Google matches the literal string in a profile's public text. (The intext: variant returns nothing β€” skip it.)

Can I get corporate emails this way?

Rarely. Personal inboxes leak because people type them into their profiles; company addresses almost never sit on the public page. For work emails at volume, an email finder beats Google.

How many results can one dork return?

A few hundred. Google caps every query there. Split the dork by city or role to go wider β€” or run it through the scraper, which paginates to the cap for you.

Is X-ray search against LinkedIn's terms?

Not if you stay logged out. You only agree to LinkedIn's terms by creating or using an account. Google's public index never puts you under that contract β€” the distinction that decided hiQ v. LinkedIn.

Why are so many LinkedIn profiles on Google in the first place?

By design. LinkedIn wants profiles indexed so members appear when someone searches their name β€” a textbook programmatic SEO play. Public profiles are an acquisition channel, and this guide simply reads what LinkedIn published.

Why doesn't my own profile show up on Google?

It's a visibility setting. If your public profile is switched off, Google can't index it. Turn it on under Settings and Privacy, then give Google about two weeks to catch up.

Final thoughts

Google already did the hard work: it indexed a billion-plus LinkedIn profiles and left them sitting one dork away, no login required.

Start in the browser β€” a dork or two tells you whether your list exists. The moment you need every result in a CSV, hand the same dork to the scraper, or let your agent drive it over MCP.
Got questions? Ping me on LinkedIn β€” or put the guide to work and find me yourself:
site:linkedin.com/in/ "sasha bouloudnine"
f

Related Articles

Related Squids