How to Find Company Employees on LinkedIn With Google Dorks
site:linkedin.com/in combined with a quoted job title and company name to find publicly indexed LinkedIn profiles without a paid recruiter account. For example: site:linkedin.com/in "VP of Marketing" "Acme Corp". Google indexes public LinkedIn profiles, and the site: operator restricts results to the profile path — giving you a targeted list of employees at any company whose profiles are set to public.
Why this works
LinkedIn profiles that are set to "public" are indexed by Google. That means
Google's search engine has crawled the profile page, stored the job title, employer
name, location, and headline text, and will return that page as a result for a
query that matches. The site:linkedin.com/in operator tells Google to
only show results from that specific URL path — the one that holds individual profiles —
filtering out company pages, job posts, and everything else LinkedIn hosts.
The result is a way to browse a subset of LinkedIn's public index with precision that LinkedIn's own free-tier search does not allow — without any automation, scraping, or ToS violation. You are reading pages that LinkedIn has deliberately made public and that Google has indexed with LinkedIn's cooperation.
The core query structure
# Base pattern site:linkedin.com/in "JOB TITLE" "COMPANY NAME" "LOCATION Area" # Example: VP of Marketing at a SaaS company in Austin site:linkedin.com/in "VP of Marketing" "Austin, Texas Area" -jobs # Example: Director of Engineering at Acme Corp site:linkedin.com/in "Director of Engineering" "Acme Corp" # Example: Head of Sales, multiple title variants site:linkedin.com/in ("VP of Sales" OR "Head of Sales") "Chicago Area"
Step-by-step: building a decision-maker search (6 steps)
Start with site:linkedin.com/in
Always use /in — not site:linkedin.com alone.
The /in/ path is where individual profile URLs live (e.g.,
linkedin.com/in/jane-smith-12345). Without the path restriction,
Google returns company pages, job listings, and LinkedIn articles mixed in with
profiles.
Add a job title using a quoted phrase or intitle:
A quoted phrase like "VP of Marketing" matches profiles where that
exact string appears anywhere on the indexed page — headline, job history, or
bio. Using intitle:"VP of Marketing" is slightly stricter: the title
must appear in the page's <title> tag, which LinkedIn populates
from the profile headline. Use the quoted-phrase form when you want broader
coverage; use intitle: when you want headline-match precision.
For roles with multiple title variants, use OR:
site:linkedin.com/in ("VP of Marketing" OR "Head of Marketing") "Boston Area"
Add the company name
LinkedIn profiles include employer names in the indexed page text, so a quoted company name filters to people who list that employer. For better precision, use the company's exact display name as it appears on LinkedIn — not an abbreviation:
site:linkedin.com/in "Director of IT" "Acme Corporation"
This approach works well for targeting a specific account. It does not work for identifying everyone at a large organization whose employees use many slight name variants — in that case, omit the company filter and rely on title + location.
Add location in LinkedIn's format
LinkedIn formats location as "City, State Area" or "Greater City Area" in profiles. Matching this exact format yields far more results than using a bare city name. Common formats:
| City | LinkedIn location string |
|---|---|
| Austin | "Austin, Texas Area" |
| New York | "Greater New York City Area" |
| Chicago | "Chicago, Illinois, United States" |
| San Francisco | "San Francisco Bay Area" |
| Los Angeles | "Los Angeles Metropolitan Area" |
If results are thin, try just the city or state without the "Area" suffix — LinkedIn's format has changed over time and profiles are not always consistent.
Filter out noise with -
Title searches like "Director" or "VP" sometimes surface job listing pages or recruiter profiles that mention the title. Add exclusions:
site:linkedin.com/in "VP of Marketing" "Austin, Texas Area" -jobs -recruiter -hiring
The -jobs exclusion suppresses results from LinkedIn's job post
pages that sometimes appear in site:linkedin.com/in queries.
Run the query and review
Paste the assembled query into Google. Each result is a publicly indexed LinkedIn profile matching your filters. Click through to view the full profile (LinkedIn may ask you to log in for some profiles depending on the user's visibility settings).
Pro users on getdork can run the dork directly inside the app and get the top 20 results with titles, URLs, and snippets — without manually clicking through each one.
Query recipes for common use cases
| Goal | Example query |
|---|---|
| Find CMOs at tech companies in Seattle | site:linkedin.com/in ("Chief Marketing Officer" OR "CMO") "Seattle, Washington Area" |
| Map a specific company's leadership | site:linkedin.com/in "Acme Corp" (Director OR VP OR "Vice President") |
| Find IT decision-makers at mid-market companies | site:linkedin.com/in "Director of IT" OR "VP of Technology" "Dallas, Texas Area" |
| Recruit Python developers open to work | site:linkedin.com/in "Python" "machine learning" "open to work" "San Francisco Bay Area" |
| Find procurement managers at healthcare systems | site:linkedin.com/in "Director of Procurement" "health system" OR "hospital" |
getdork's query builder assembles the correct syntax from form fields. Free accounts get the query string to paste into Google. Pro accounts run the search in-app and export results as CSV.
Try it free at getdork.com →
Using LinkedIn dorks responsibly
Finding public profiles via Google is not scraping and does not violate LinkedIn's terms of service for individual manual use. A few things to keep in mind:
- Manual browsing only. LinkedIn's ToS prohibits automated tools that make bulk requests to their servers. Clicking through Google results to individual profiles is fine; building a bot that mass-harvests profile URLs is not.
- Public means public. Only profiles the user has set to public visibility are indexed. If a profile does not appear in Google results, it is because the user has restricted their visibility — respect that.
- Outreach quality matters. Cold outreach is fine; spam is not. Treat the data as a starting point for genuinely relevant, targeted contact — not a list for bulk messaging.
Frequently asked questions
Is using Google to find LinkedIn profiles legal?
Yes. Viewing publicly indexed LinkedIn profiles via Google is legal. These pages are intentionally public and indexed with LinkedIn's cooperation. LinkedIn's ToS prohibit automated scraping, but manual Google searches are not scraping. For the full legal and ethical breakdown, see Is Google dorking legal?
Why use site:linkedin.com/in instead of site:linkedin.com?
The /in/ path is where individual profile URLs live. Without the path
restriction, results include company pages (/company/), job posts
(/jobs/), and articles — which dilutes the profile results you're
after.
Why does my LinkedIn dork return no results?
The most common cause is over-filtering. Remove the most specific condition first — usually the exact company name or a narrow location phrase — and retry. Also note that only profiles set to public visibility are indexed by Google; if the target company has employees with private profiles, they won't appear.
Can I use OR to search multiple job titles?
Yes. Use uppercase OR: site:linkedin.com/in ("VP of Marketing" OR "Head of Marketing").
Parentheses keep the OR grouped correctly so Google applies it only to the title
choices, not the whole query.
Do I need a LinkedIn account to do this?
No. The Google search runs without any LinkedIn session. When you click through to a profile, LinkedIn may show the full page to logged-out visitors or prompt you to log in — it depends on that user's visibility settings. The dork query itself requires only a Google search.
Related guides
- Google search operators cheat sheet (with examples) — the full operator reference including site:, intitle:, inurl:, and more.
- What is Google dorking? A practical guide — how operators work, use cases, and responsible use.
- Is Google dorking legal? What's allowed and what isn't — the legal and ethical breakdown.