All guides

29 Oct 2026

Bing Search Operators for Recruiters: X-Ray Sourcing Guide

How to use Bing search operators for recruiter X-Ray sourcing: inbody:, intitle:, filetype:, and site: syntax that actually works in Bing.

boolean basicsbing

Why Bing matters for recruiter X-Ray

Google is not the only search engine that indexes LinkedIn profiles. Bing indexes

a large share of public LinkedIn pages and its operator syntax is different

from Google's. A string that works in Google X-Ray often returns nothing in

Bing, and vice versa.

The key difference: Bing uses `inbody:` instead of Google's implied body

match, and `intitle:` behaves differently. If your Google string returns

empty in Bing, the syntax is the problem, not the candidates.

Bing operators recruiters actually use

  • • site: — restrict to a domain. `site:linkedin.com/in/` works in both

Google and Bing.

  • • inbody: — match a term in the page body. Bing-specific. Use it for

skills and keywords: `inbody:"financial modeling"`.

  • • intitle: — match a term in the page title. Bing's title matching is

stricter than Google's. `intitle:"Finance Manager"`.

  • • filetype: — match a file type. `filetype:pdf` finds CV documents.
  • • "quotes" — exact phrase match. Works in both engines.
  • • AND, OR, NOT — Boolean operators. Bing requires uppercase.
  • • () — grouping. Essential for complex strings.

A complete Bing X-Ray string

site:linkedin.com/in/ (intitle:"Finance Manager" OR intitle:"Senior Finance Manager") inbody:"financial modeling" inbody:"variance analysis" (inbody:"CA" OR inbody:"CFA")

Paste this into Bing. The `inbody:` terms are Bing-specific — they will not

work in Google. For Google X-Ray, use the same string without `inbody:`

and with plain quoted phrases.

Bing vs Google: the differences that matter

1. inbody: vs implied body. Google matches body terms implicitly. Bing

requires `inbody:` for body matching. Without it, Bing matches the

term anywhere on the page including the URL and metadata.

2. intitle: strictness. Bing's `intitle:` matches the exact title tag.

Google's is looser. A title that matches in Google may not match in Bing.

3. No minus operator in the same way. Bing supports `-term` for

exclusions, but the behaviour differs from Google. Test before you trust.

4. Result freshness. Bing and Google index LinkedIn at different rates.

A profile visible in Google may not be in Bing yet, and vice versa.

When to use Bing instead of Google

  • • Google X-Ray returns too many results. Bing's stricter matching

narrows the pool.

  • • You want CV documents. Bing's `filetype:pdf` is more reliable for

finding public CVs.

  • • Google is rate-limiting you. Bing has its own limits but they are

different, so alternating engines spreads the load.

Generate Bing-safe strings

The boolean search string generator outputs

Bing-safe syntax alongside the other five dialects. Paste a job description

and get all six at once. For role-ready starter strings, browse the

role search library — for example the

FP and A Manager search.

Lint your Bing string with the free boolean lint tool

before you paste it. Bing's parser is stricter than Google's, so a string that

passes in Google may fail in Bing.

Run these strings in the workspace.

Paste a JD, get all six dialects, and screen the pipeline against the same bar.

Open workspace

Related guides