LinkedIn X-Ray Search: How to Find Prospects With Google (Examples)
Find sales prospects with Google X-ray search: operators, 10 tested CZ/EU queries, real anonymized results and a verified Salesbot research workflow.
LinkedIn X-Ray Search: How to Find Prospects With Google (Examples)
LinkedIn X-ray search means searching Google for public LinkedIn profiles with site:linkedin.com/in/ plus words describing a role, industry, company or location. Use it to build an initial sales shortlist when you do not need Sales Navigator's structured filters. It searches Google's index, not LinkedIn's complete member database, and it cannot confirm someone's current employer.
For sales teams, the useful outcome is a candidate worth checking—not a ready-to-message lead. Below are ten queries we actually tested, including searches that returned no profile links, followed by a workflow grounded in Salesbot's current tool definitions and implementation.
What LinkedIn X-ray search finds—and what it does not
Google can show LinkedIn profile pages that it has indexed publicly. Adding a role and a location narrows the words you are looking for. Adding an industry word can reveal possible relevance, but that word might describe an earlier job, a customer or a personal interest rather than the person's current company.
Start with a question such as “Which software sales leaders might be based in Brno?” rather than “Give me every current sales director in Brno.” The first is a discovery task. The second requires completeness and current employment data that a Google query cannot establish.
Google explicitly explains that a site: query does not necessarily return every indexed URL under that prefix. It is therefore not a way to count all LinkedIn members in a market. See Google's documentation for the site operator.
Google operators for a sales prospecting query
Use the fewest conditions that express your target. Each extra exact phrase can remove useful candidates as well as irrelevant results.
| Operator | Example | Use and limitation |
|---|---|---|
site: | site:linkedin.com/in/ | Focus on profile URLs in Google's index; it is not an exhaustive profile export. |
| Quotation marks | "Head of Sales" | Look for an exact phrase; alternative job titles may disappear. |
OR | ("CTO" OR "Chief Technology Officer") | Try alternative role wording in one query; still review each result. |
| Minus | -recruiter | Exclude a word that creates noise; this can also exclude relevant people. |
intitle: | intitle:"Sales Director" | Narrow by page-title wording; indexed titles do not prove a current role. |
Google documents quotation marks, site restrictions and exclusions in its search refinement help. The OR and intitle: examples below are tested queries, not a guarantee that every combination will behave identically in another market or on another day.
Avoid turning your entire ideal customer profile into exact phrases. “Manufacturing” may not appear on a relevant finance leader's indexed page. A city name may be replaced by a metropolitan area. Use the query to discover candidates and use later checks to establish fit.
Ten tested LinkedIn X-ray queries for CZ and European sales
Method: On October 8, 2026, we ran these exact queries through DataForSEO's live Google organic search endpoint, using Czechia as the search location and English as the language. We requested the first ten organic results. The count below is the number of returned URLs containing linkedin.com/in/, not Google's estimated total and not the number of qualified leads.
These are real search outputs summarized without publishing names, profile URLs or personal snippets. We did not import these people into Salesbot or send outreach. Zero means no profile URL appeared in that response—not that no suitable person exists.
| Sales audience | Exact query | Profile links returned |
|---|---|---|
| SaaS CEOs, Prague | site:linkedin.com/in/ "CEO" "SaaS" "Prague" | 10 |
| Manufacturing CFOs, Czech Republic | site:linkedin.com/in/ "CFO" "manufacturing" "Czech Republic" | 0 |
| Software sales leaders, Brno | site:linkedin.com/in/ "Head of Sales" "software" "Brno" | 10 |
| Fintech technology leaders, Berlin | site:linkedin.com/in/ ("CTO" OR "Chief Technology Officer") "fintech" "Berlin" | 10 |
| Automotive procurement managers, Germany | site:linkedin.com/in/ "Procurement Manager" "automotive" "Germany" | 1 |
| Manufacturing HR directors, Poland | site:linkedin.com/in/ "HR Director" "manufacturing" "Poland" | 0 |
| Logistics operations directors, Netherlands | site:linkedin.com/in/ "Operations Director" "logistics" "Netherlands" | 10 |
| SaaS marketing directors, France | site:linkedin.com/in/ "Marketing Director" "SaaS" "France" | 0 |
| Cybersecurity founders, Estonia | site:linkedin.com/in/ "Founder" "cybersecurity" "Estonia" -recruiter | 0 |
| Software sales directors, London | site:linkedin.com/in/ intitle:"Sales Director" "software" "London" | 10 |
How to interpret the successful searches
The Prague, Brno, Berlin, Netherlands and London searches each returned ten profile links. That is evidence that those particular query formulations can surface candidates. It is not evidence that all ten people currently hold the requested role, work in the requested industry or are appropriate buyers.
The Berlin query tests two title variants in one search. The London query tests title wording rather than assuming that a matching phrase anywhere in a page identifies the person's job. In both cases, review the underlying profile and company context before assigning the person to a target segment.
The Germany procurement query returned one profile link among six organic results. Counting only profile links matters: the returned organic set was not always ten items, and not every returned URL matched the intended profile prefix. Treat the actual URLs as evidence, not the query syntax alone.
What to do with a zero-result query
The CFO, HR director, marketing director and Estonia founder searches returned no profile links in the checked response. We have kept those outcomes instead of substituting invented examples. Tight phrases, regional vocabulary, indexing coverage and search interpretation can all affect discovery.
For your own next test, change one condition at a time: try a broader role, remove an industry phrase or replace a country with a city. Those are suggested experiments, not additional searches included in our measured table. Record each change so that you know which condition made the difference.
X-ray versus LinkedIn Boolean search and Sales Navigator
Boolean search inside LinkedIn is a different search environment. LinkedIn documents uppercase AND, OR and NOT, quotation marks and parentheses for combining terms. Use the syntax supported by the specific LinkedIn search field; do not paste Google's site: restriction or minus exclusions into LinkedIn and assume they are interchangeable. See LinkedIn's Boolean search guidance.
Sales Navigator adds its own search experience and filters. A Google query containing a location word is not equivalent to a structured location filter. A company name in an indexed snippet is not equivalent to a current-company selection. Prefer the native search when the task depends on those distinctions, then check the results against your sales criteria.
X-ray is useful for public discovery and wording experiments. LinkedIn Boolean search is useful for expressing combinations inside LinkedIn. Neither removes the need to verify a person's current role before writing a relevant message.
How the verified Salesbot X-ray workflow works
Salesbot exposes search_google_xray. In the inspected implementation, its inputs include a job title or an array of title alternatives, location, keywords, excluded words, a requested result limit and an optional lead-list ID. At least one title is required. The search builds a Google query around the profile URL prefix and passes it to the Google search integration.
The search integration returns the query and candidate profile URLs with available names and snippets. The MCP tool also saves qualifying new contacts and returns contact IDs for new or already-existing matches. Without a selected list, it uses a Google X-Ray list. This is not a read-only preview tool: searching through this MCP workflow can create CRM records.
Saved snippet-based contacts are marked as unverified in the inspected code. enrich_contacts is a separate follow-up step, not something the Google snippet has already completed. Do not treat an indexed headline as verified current employment or assume that the search supplies a personal email address.
Use that distinction to design a reviewable workflow:
- Define the buyer role, market and relevant company context before choosing keywords.
- Choose the lead list deliberately and authorize the search, understanding that it can save contacts.
- Review the returned query, candidate URLs and duplicate matches before expanding the search.
- Enrich selected contacts, check current relevance and apply your exclusions or blacklist.
- Prepare the campaign only after the shortlist has been reviewed; check the message and recipient before authorizing outreach.
Salesbot's tool interface supports research through Claude and a custom ChatGPT connector. That does not mean a public directory endorsement or that every research step should run unattended. See Claude for sales for the research context and the LinkedIn outreach tool for the campaign workflow.
Verification boundary: We inspected the live product tool descriptions and the corresponding source implementation. We did not execute an MCP contact-import, enrichment or campaign during this article's research. The measured examples above are actual Google searches, not fabricated Salesbot response payloads or a claim of an end-to-end campaign test.
Limits: coverage, freshness and company context
A public profile may not be indexed, may have changed since Google last crawled it or may use wording that your query excludes. Search location and language also matter. The same query can produce a different result set later; the table is a dated observation, not a promised yield.
Distinguish three questions: did Google return a profile link, is the person currently relevant, and is outreach appropriate? Only the first is answered by the counts in this article. Enrichment and human review address the second. Your purpose, contact practices and applicable requirements determine the third.
Salesbot also exposes public-company website reading, which can help check what a business actually does. It is not a reason to invent a company's budget or to extract personal contact details from a website. A hiring notice can be a research cue, but it needs separate validation; this guide does not present an untested job-posting case study.
We have not published a numeric production search allowance here because we did not confirm the current account-specific allowance in the running product. A requested result limit in a tool definition is not a guarantee of that many matches or permission to collect indefinitely.
Responsible use of public profile information
Public visibility is not the same as unrestricted reuse or consent to receive a sales message. Collect only information relevant to a defined prospecting purpose, retain source context and avoid republishing personal search snippets unnecessarily. Respect objections and your team's exclusions before another campaign is prepared.
For EU prospecting, consider the applicable data-protection and outreach requirements, including GDPR, rather than assuming that “found on Google” settles them. This is a practical research guide, not legal advice or a conclusion that a particular outreach activity is permitted. Our examples therefore disclose queries and aggregate counts without identifying the people returned.
Frequently asked questions
What is LinkedIn X-ray search?
It is a Google search using site:linkedin.com/in/ with role, company, industry or location terms to find indexed public profile pages. It does not search the complete LinkedIn member database.
Is X-ray search allowed?
A public Google result does not establish that every reuse or outreach activity is allowed. Assess applicable terms, data-protection and outreach requirements for your intended use; this guide does not provide legal advice.
What is the difference between X-ray and Boolean search?
X-ray uses Google's search environment and operators such as site: and minus exclusions. LinkedIn Boolean search combines supported terms inside LinkedIn using operators such as AND, OR and NOT. Their filters and result coverage are not interchangeable.
Can I automate LinkedIn X-ray search with Salesbot?
Salesbot exposes search_google_xray, which can save candidate contacts and return their IDs. Snippet-based contacts require verification; enrichment is a separate step. Authorize the contact-saving workflow deliberately and review recipients before outreach.
Does X-ray search work for Sales Navigator?
It can surface public LinkedIn profile pages indexed by Google. It does not unlock Sales Navigator-only information or reproduce Sales Navigator's structured filters.
For the wider workflow, explore the LinkedIn automation tool or create a Salesbot account.
Written by Petr Kubíček, Founder & CEO of Sales Robots s.r.o. Queries and product implementation checked on October 8, 2026.