LinkedIn X-ray search means using Google (or Bing) to search LinkedIn's public profile pages instead of LinkedIn's own search. It costs nothing, it isn't limited by your LinkedIn plan or network, and it can surface people LinkedIn's search hides from a free account. It also has real limits: Google sees only what members make public, shows a limited number of results, and changes how its operators behave. This guide covers the operators that work, ready-to-adapt strings by role, the limits, and the rules to stay inside.

For the bigger picture — Boolean search inside LinkedIn, Recruiter, and other channels — see our LinkedIn sourcing strategies and how to find candidates on LinkedIn.

How LinkedIn X-Ray Search Works

Every LinkedIn member has a public profile page at an address like linkedin.com/in/name. If the member allows it, search engines index that page. LinkedIn's help center explains that members choose whether their public profile appears in search engines at all, and which sections are shown (LinkedIn Help). An X-ray search restricts Google to those pages with the site: operator and then filters them by the words on the page — usually the person's name, headline, current company, location and the public sections of their experience.

Two consequences follow. You only find members who left their public profile visible, and you only match what is in the public version of the profile, which can be shorter than what you see when logged in.

The Search Operators That Matter

OperatorWhat it doesExample
site:Limits results to one site or pathsite:linkedin.com/in
"quotes"Matches the exact phrase"product manager"
OREither term; write it in capitals("data engineer" OR "analytics engineer")
- (minus)Excludes a word-recruiter -jobs
( )Groups OR alternatives(Python OR Go)
intitle:The word must be in the page title — on LinkedIn, roughly the name and headlineintitle:"engineering manager"
*Stands for any word inside a quoted phrase"head of * engineering"

Google's own search help documents quotes, site:, the minus sign, before:/after: and filetype:. OR, intitle: and the wildcard are widely used by sourcers and work today, but Google doesn't promise their behaviour, so test a string before you rely on it.

What not to use: the + operator was retired years ago — use quotes instead. The ~ synonym operator is gone too; Google matches synonyms on its own. AROUND(n) (words within n words of each other) is undocumented and unreliable. And typing AND is unnecessary: a space already means "and" in Google.

Building a String, Step by Step

  1. Start with the site: site:linkedin.com/in (profiles only, not company pages or job posts).
  2. Add the title variants people actually use, in an OR group: ("backend engineer" OR "backend developer" OR "software engineer").
  3. Add one or two required skills: (Go OR Golang) Kubernetes.
  4. Add the location as it appears on profiles: "Berlin", or ("Greater London" OR London).
  5. Exclude noise: -recruiter -"talent acquisition" -jobs.
  6. Run it, read the first page, adjust. If results are off, move the title into intitle:; if there are too few, drop a skill.

If Google shows job boards instead of profiles, it has quietly dropped your site: restriction — this happens with strings that combine many OR groups and exclusions. In our tests, the same kind of search for designers returned job listings until it was simplified. Cut the string back: one title in intitle:, one skill, the city, no exclusions — then add terms back one at a time.

Put together:

site:linkedin.com/in ("backend engineer" OR "backend developer") (Go OR Golang) Kubernetes "Berlin" -recruiter -jobs

Example X-Ray Strings by Role

These are starting points. Change the titles, skills and city to your search, and test each one — results shift as Google and profiles change.

  • Software engineer (Python):
    site:linkedin.com/in ("python developer" OR "python engineer" OR "backend engineer") Django "Warsaw" -recruiter
  • Data engineer:
    site:linkedin.com/in intitle:"data engineer" (Spark OR Airflow OR dbt) "Chicago"
  • Engineering manager in fintech:
    site:linkedin.com/in ("engineering manager" OR "head of engineering") (fintech OR payments) London -recruiter
  • Account executive (SaaS):
    site:linkedin.com/in ("account executive" OR "enterprise account executive") SaaS "Austin" -intern
  • Accountant:
    site:linkedin.com/in ("chartered accountant" OR ACCA OR ACA) "Manchester" -recruitment
  • Nurse:
    site:linkedin.com/in ("registered nurse" OR RN) ("ICU" OR "critical care") "Phoenix" -staffing
  • Product designer:
    site:linkedin.com/in intitle:"product designer" Figma "Amsterdam"
  • Developers beyond LinkedIn:
    site:github.com ("machine learning" OR "ML engineer") "San Francisco"

Country subdomains. Many profiles are indexed under country addresses such as uk.linkedin.com/in or de.linkedin.com/in, and site:linkedin.com/in already includes them — in our tests, a Berlin search returned de.linkedin.com profiles. Use the country version, for example site:uk.linkedin.com/in, when you want to limit results to one country.

X-Ray on Bing

Bing supports X-ray searches too, with a few differences documented in Microsoft's advanced search options: AND, OR and NOT must be in capitals or Bing ignores them, it uses only the first 10 terms of a query, and OR groups should go in parentheses. Bing's index differs from Google's, so the same string can return different people — worth a second run for hard searches.

  • Only public profiles. Members who hide their public profile from search engines never appear.
  • A snapshot, not live data. Search engines refresh profile pages on their own schedule; a job change can take weeks to show.
  • Few results per query. Google shows a limited number of pages for any search, and since September 2025 it no longer honours the old &num=100 trick for 100 results per page. Narrow strings work better than broad ones.
  • CAPTCHAs. Paging quickly through many results makes Google ask whether you are a robot.
  • No contact details. X-ray gives you names and headlines, not emails or phone numbers.

Stay Inside the Rules

Running searches by hand in a search engine is ordinary web search. Automating it is a different matter: LinkedIn's User Agreement prohibits software, scripts or bots that "scrape or copy" profiles, and the long-running hiQ Labs v. LinkedIn case ended in December 2022 with a consent judgment and a $500,000 award against the scraping company. Use X-ray to find people, then contact them through legitimate channels — and handle the data you keep under the privacy rules that apply to you, such as GDPR.

Free Tools That Build the String for You

  • Recruitin.net builds Google X-ray strings for LinkedIn from a form (country, title, keywords, employer, education) and has builders for GitHub, Stack Overflow and Dribbble.
  • Google Programmable Search Engine lets you set up a search limited to LinkedIn profile pages; its JSON API costs $5 per 1,000 queries, up to 10,000 a day (Google).

From X-Ray Results to Outreach

An X-ray search ends with a list of names. The work starts after: checking the full profile, finding a way to reach the person, writing to them and following up. MindHunt AI covers that part. Its Chrome extension imports the LinkedIn profile you are looking at into a position, and nothing is spent until you press Import. From the profile you reveal verified emails and phone numbers and run email sequences from your Gmail or Outlook that stop when the candidate replies. On paid plans you can also skip X-ray entirely and search LinkedIn through your own account from the same screen as MindHunt AI's own candidate search.

From a Name to a Conversation

Import LinkedIn profiles in one click, reveal verified contacts and run follow-ups that stop on reply — or search LinkedIn through your own account. From $29 per seat.

Start Free →