LinkedIn x-ray search is a Google query built around the site: operator: you point Google at linkedin.com/in, add the words you want, and exclude the ones you do not. A basic example is site:linkedin.com/in "product manager" fintech -jobs. Google's own Refine Google searches (opens in a new tab) page documents site: and the other operators used here.
The technique works because it searches the web for LinkedIn profile pages that Google has already indexed, rather than searching inside LinkedIn. That gives you a second surface with different limits, which is useful when LinkedIn's own search returns approximations.
Why x-ray exists alongside native search
LinkedIn's native search is a filter-and-count tool, and LinkedIn states its results are always approximate, with a counter that can differ from what is shown. It also caps the number of Boolean operators on the consumer search engine. X-ray moves the query to Google, where the syntax is different and the operator list is Google's, not LinkedIn's.
The tradeoff is directness: native search reads LinkedIn's own index, while x-ray reads whatever Google has crawled. A profile that is not indexed, or whose indexed snippet is stale, will not appear or will appear with old text. Use x-ray as a way to widen coverage, not as a replacement for LinkedIn's own filters.
The building blocks
Google's Refine searches page documents these operators, and specifies that you must not put a space between the operator and its term — site:nytimes.com works, site: nytimes.com does not.
| Operator | What it does | Example |
|---|---|---|
site: | Restrict results to one site or domain | site:linkedin.com/in |
" " | Exact word or phrase | "supply chain manager" |
- | Exclude a word | -jobs |
before: / after: | Pages last updated before or after a date | after:2026-01-01 |
filetype: | Restrict to a file type | filetype:pdf |
For profile finding, site:, quotes and - do almost all the work. before: and after: are worth remembering when you want to favour recent pages, and filetype: is rarely relevant to profile pages.
Three worked queries
These are illustrative templates, not tested result counts. Swap the role words and industries for your own target.
1 - sales leaders in software
site:linkedin.com/in ("head of sales" OR "vp sales" OR "sales director") SaaS
The quoted titles keep their word order; the OR list widens the title options; SaaS supplies the industry context.
2 - recruiters, filtering out hiring words
site:linkedin.com/in "talent acquisition" (remote OR hybrid) -jobs -"we're hiring"
The exclusions remove matching words from the profile pages the query already returns, so they can also drop recruiters who mention hiring — check the results rather than assuming the list is clean.
3 - a role in one city
site:linkedin.com/in "supply chain manager" Auckland -recruiter
Add a city or region as a plain word. It is a looser location filter than native search's Locations field, so verify the location on the profile.
Tightening a query
Most noise comes from pages that mention a role without being the profile you want. Because the query is already scoped to site:linkedin.com/in, exclusions act on the text of matching profile pages: -jobs, -hiring, -"looking for" and -recruiter remove pages that contain those words, and they can remove relevant profiles too — a recruiter who lists hiring in a headline is one example. Run the query again to see the shift, and if Google returns nothing, the query may be too narrow or the pages you want may not be indexed: remove one exclusion at a time and widen the terms.
Keep phrases quoted and single words unquoted. Quoting a single common word rarely helps, while quoting a multi-word title is usually essential to avoid pages that merely contain both words in different places.
Operators that circulate but are not on the Refine searches page
Many x-ray guides use intitle: to push a role into the page title, sometimes with the note that a LinkedIn profile title reflects the headline rather than the current job. Google's own Refine searches page reviewed here lists site:, quotes, -, before:, after: and filetype: — it does not list intitle: or inurl:. That page names some popular operators rather than an exhaustive set, so read the absence as "not listed here", not as proof the terms are unsupported. Results built on terms you use outside that list should be checked by hand.
When x-ray is the better tool
X-ray is worth reaching for when native search feels too coarse — for example, when you want an unusual phrase combination that a filter cannot express, or when you want to see how a profile is publicly indexed. It is also how you reach LinkedIn data from a general search engine, which some teams prefer for research.
It is the weaker choice when you need a structured filter such as degree of connection or current company, or when the profiles you care about are unlikely to be publicly indexed. In those cases use LinkedIn advanced search instead, which exposes filters that a Google query cannot reproduce. The two operators are also not interchangeable: site: and quotes in Google are a different language from AND, OR and NOT inside LinkedIn, which is why x-ray and LinkedIn Boolean search are separate skills.
One limitation to keep in mind: x-ray finds public pages, not access. A profile you surface this way may still be outside your network, so check the relationship before you plan how to reach out. Tools that build x-ray strings for you, such as the search-and-list features some vendors market, are a convenience layer on the same Google operators — Clapa is one place where a vendor frames its LinkedIn tooling if you want to compare approaches.
FAQ
What does x-ray search mean on LinkedIn?
It means using Google's site: operator against linkedin.com/in to find publicly indexed LinkedIn profile pages, combined with keywords and exclusions.
Is x-ray search the same as Boolean search?
No. Boolean search inside LinkedIn uses AND, OR and NOT. X-ray uses Google's operators, chiefly site:, quotes and -.
Why do some x-ray results include pages that are not the profile I want?
Because site:linkedin.com/in restricts results to URLs with that prefix, and a profile page can itself mention jobs, hiring or other roles in its text. Excluding those words removes matching profile pages too, including some you may want.
Are intitle: and inurl: Google operators?
Google's Refine searches page reviewed here does not list them; that page names some popular operators rather than an exhaustive set, so if you use them, check each result by hand.
Sources
- Google Search Help, Refine Google searches (opens in a new tab)
- LinkedIn Help, Search on LinkedIn (opens in a new tab)
- LinkedIn Help, Boolean Query Limitations (opens in a new tab)