LinkedIn X-Ray Search on Google: The Full Guide

Every recruiter learns X-ray search the same way: someone senior hands them a Boolean string, tells them to swap in a job title, and never explains why half the results are dead profiles from 2014. This guide fixes that. You'll get working strings, the syntax rules Google actually enforces, and a clear answer on when X-ray search is the wrong tool entirely.

What LinkedIn X-ray search actually is

X-ray search means using Google's site: operator to search LinkedIn's public pages instead of using LinkedIn's own search bar. You're not logging into LinkedIn at all — you're asking Google to index and return LinkedIn profile pages that match your keywords. The basic syntax looks like this:

site:linkedin.com/in "product manager" "fintech" -intitle:"profiles"

The technique exists because LinkedIn's native search has always rationed access. Free accounts get a handful of searches before hitting a wall. Recruiter seats cost real money — $170+ a month per seat for LinkedIn Recruiter, more for Recruiter Corporate. X-ray search sidesteps all of it. You're querying Google's index, which is free, has no daily cap, and doesn't care whether you're logged into LinkedIn.

The tradeoff is real, though. Google only indexes public LinkedIn pages, and it doesn't index all of them, or update them on any schedule LinkedIn controls. You're searching a stale, partial mirror of LinkedIn — not LinkedIn itself. Profiles that are set to private, or that LinkedIn has deindexed for crawler-blocking reasons, simply won't show up no matter how good your string is. Recruiters who've used X-ray search for years know this going in. If you're new to it, budget for the fact that you'll miss people — sometimes exactly the people you need.

The exact syntax that works right now

Google's operators have narrowed over the past few years — intitle:, inurl:, and multi-term OR groups don't behave the way old sourcing blog posts from 2018 describe. Here's what's actually reliable today.

Start with the base command:

site:linkedin.com/in

This restricts results to personal profile URLs, filtering out company pages, job posts, and LinkedIn's own blog content. Don't skip it — without it you're wading through LinkedIn Pulse articles and job listings.

Add exact phrases in quotes. Google treats quoted phrases as literal strings, so "senior software engineer" returns that exact phrase, not any combination of those three words:

site:linkedin.com/in "senior software engineer" "Berlin"

Use OR for title variants, always in caps, always with parentheses around the group:

site:linkedin.com/in ("talent acquisition" OR "recruiting") "SaaS" "Amsterdam"

Exclude noise with the minus operator, no space between the dash and the word:

site:linkedin.com/in "product designer" -"intern" -"student"

Combine location and company by stacking quoted phrases — Google implicitly ANDs anything you don't OR together:

site:linkedin.com/in "data scientist" "machine learning" "London" -"recruiter"

That last exclusion matters more than people think. Recruiters index each other constantly, and a search for "data scientist" without excluding "recruiter" will surface a pile of sourcing professionals who list every skill they've ever recruited for in their headline.

Building strings for specific roles

A generic string returns generic noise. The real skill in X-ray search is translating a job requisition into search logic, and that means thinking about how people in that role actually describe themselves — not how the job posting describes the role.

For a backend engineering search, don't just search "backend engineer." Layer in stack-specific terms, because engineers self-identify by tooling more than by title:

site:linkedin.com/in ("backend engineer" OR "backend developer") ("Golang" OR "Go developer") "Dublin" -"junior"

For sales, titles vary wildly by company size — "Account Executive" at a 20-person startup and a 2,000-person enterprise mean very different seniority levels, so pair the title with a scope signal:

site:linkedin.com/in "account executive" ("enterprise" OR "strategic accounts") "SaaS" "New York"

For niche technical roles, use the tool names candidates would actually list as skills, since Google indexes the skills section along with the headline and summary:

site:linkedin.com/in "DevOps" ("Terraform" OR "Kubernetes") "Munich" -"recruiter" -"consultant"

A worked example: say you need a marketing ops person with HubSpot experience in the Netherlands. A first pass might be site:linkedin.com/in "marketing operations" "HubSpot" "Netherlands". Run it, and you'll likely get 40-80 results, many of them agency staff who list HubSpot as a certification rather than a job function. Second pass: add -"agency" and swap "Netherlands" for ("Amsterdam" OR "Utrecht" OR "Rotterdam") since Google sometimes fails to match the country-level location field reliably. That second pass usually cuts noise by half.

Common mistakes that quietly tank your results

Forgetting the dash-space rule. - "intern" with a space after the dash gets ignored by Google; it has to be -"intern" with zero space. This single typo is the most common reason a string returns way more junk than expected.

Over-stacking OR groups. Every additional OR group inside parentheses multiplies your search's breadth and dilutes relevance. Three OR groups in one string (title variants, skill variants, location variants) often returns worse results than two tightly chosen phrases. Pick your highest-signal two or three terms and commit.

Searching titles that don't match how people describe themselves. This is the deeper problem with X-ray search, and it's structural, not a syntax fix. Roughly 30-40% of qualified candidates for any given search carry titles that don't match the standard vocabulary — a "Growth Lead" doing product marketing work, a "Platform Engineer" doing what most companies call DevOps, a "Head of Revenue" who's really a VP Sales. Boolean search, whether run through LinkedIn or X-rayed through Google, matches literal strings. It has no way to understand that "Platform Engineer" and "DevOps Engineer" often describe the same job. You will never catch these candidates by adding more OR clauses, because you don't know in advance which non-obvious titles to add.

Assuming Google's index is current. Google recrawls LinkedIn on its own schedule, not LinkedIn's. Someone who changed jobs eight months ago might still show up under their old title and company. Always click through and verify before you reach out — nothing burns a candidate relationship faster than opening with "I saw you're a Senior Engineer at [company they left in Q1]."

When X-ray search isn't the right tool

X-ray search is free and it's a genuinely good first move for a narrow, well-defined search where the target title is standard and the candidate pool is small enough that 40-80 results feels sufficient. If you're sourcing for a specific, well-named role in a specific city, spend twenty minutes on Google before you spend money on anything else.

Where it breaks down is volume and title ambiguity. If you're running 8-10 searches a week across varied roles, manually rewriting Boolean strings and clicking through stale results eats 4-6 hours per role — time a solo recruiter or a small agency usually doesn't have. And because X-ray search can only match literal keywords, it structurally can't surface that 30-40% of candidates who use non-obvious titles. No amount of clever OR-stacking fixes a problem that's about semantic understanding, not syntax.

This is the gap tools like SeekOut, hireEZ, Findem, Fetcher, and Gem were built to close, and they do close it — at €10K-€90K a year, usually bundled with a LinkedIn Recruiter license you also have to pay for. That price tag makes sense for a 500-person talent org. It doesn't make sense for a solo recruiter running five open roles or a ten-person agency watching every subscription eat into placement margin.

Full disclosure since I run one of the alternatives: humaaaaans reads a profile semantically the way a recruiter would, rather than matching keywords, specifically to catch that non-obvious-title population X-ray search misses — and pricing is public, starting at €199/month with a free first search and no card required, so you can compare it against your own X-ray results before deciding either way.

For most people starting a search today, the right sequence is: try Google X-ray first, see how many results you get and how relevant they are, and only reach for a paid tool once you've hit the ceiling of what keyword matching can find. Honesty about that ceiling is worth more than another Boolean cheat sheet.