Boolean search vs X-Ray search — which one should you run first?

Recruiters say “Boolean” and “X-Ray” as if they were two products. They are not. Boolean is the grammar: AND, OR, NOT, quotes, parentheses. X-Ray is a Google query that points that grammar at a public site — usually LinkedIn. If you keep a Recruiter-seat string and a totally different Google string, you will ship the wrong people on one of them.

What each one actually is

• Boolean — operators you run inside LinkedIn Recruiter, Sales Nav, Indeed, or any search box that accepts them.
• X-Ray — `site:linkedin.com/in/` (or `/jobs`, GitHub, a conference speaker list) plus the same Boolean core, executed in Google.
• Not the same as a paid seat. LinkedIn Recruiter vs Google X-Ray is about InMail and project lists. This page is about the two query types.

Run Boolean first when the seat already has the people

If you have a Recruiter seat and the req is a named-account or high-volume title, stay inside LinkedIn. Filters for current company, years, and location are faster than hoping Google indexed the right headline. Build the string from this JD — not last week’s Java habit. JD Analyzer is the first pass so AND/OR/NOT match the gates.

• Use Boolean in-product when you need current-company, past-company, or “open to work” filters.
• Tighten exclusions after page one of noise. Do not keep adding OR groups.
• Keep title variants honest: “Software Engineer” OR “Backend Engineer,” not every synonym in the industry.

Switch to X-Ray when the commercial search is empty or too expensive

X-Ray earns its keep when the seat is capped, the commercial results are intern-heavy, or the person never opens InMail. A typical Google line looks like: site:linkedin.com/in/ (“Java Developer” OR “Backend Engineer”) AND “Spring Boot” AND Dallas. Add a current- or past-company clause only when the account manager already named targets.

• Public profiles only. X-Ray will not see Recruiter-only fields.
• Google ranking is not seniority. Read the last two roles before you InMail.
• Same core skills as the Boolean string. Change the `site:` and the surface — not the must-haves.

One string, two wrappers

The failure mode is two desks, two saved queries, two versions of “must have Kafka.” Write the Boolean core once. Wrap it for LinkedIn. Wrap it again for Google. Boolean & X-Ray does that from a pasted JD — LinkedIn and Google variants plus alternate titles. Copy, run, then cut noise. Do not invent a second theory of the req.

If you still cannot say the role in one line, you are not ready to search. Finish the JD read, then generate the string. Sourcing is cheaper when the operators match the packet you will actually submit.