X-ray search is a sourcing technique that uses Google's site: operator to search inside websites like LinkedIn, GitHub, and Stack Overflow - surfacing candidate profiles that platform search alone would miss. It's one of the most powerful free tools in a recruiter's arsenal, and it works because Google indexes public profile data that internal search engines often bury behind filters, paywalls, or weak algorithms.
The technique matters because most talent isn't looking for you. Only 4.1% of U.S. workers are actively job-seeking, according to the Bureau of Labor Statistics (February 2026 data). That means 95.9% of your potential candidate pool won't appear on job boards. Google operator searches help you find them wherever they've left a public digital footprint - though the technique has changed dramatically since LinkedIn restricted Google indexing in January 2024.
This guide covers every working operator, platform-specific strings for LinkedIn, GitHub, Stack Overflow, and Twitter/X, what broke in 2024 and why, and when AI-powered sourcing tools now outperform manual X-ray entirely. If you already know Boolean search fundamentals, X-ray is the natural next step.
TL;DR: X-ray search uses Google's site: operator to find candidates inside LinkedIn, GitHub, and Stack Overflow. But LinkedIn removed key profile data from Google's index in January 2024, breaking the most popular X-ray use case. GitHub is now the strongest X-ray platform for tech roles, with 180M+ developers indexed (GitHub Octoverse, 2025). For non-technical sourcing at scale, AI platforms that scan 850M+ profiles have largely replaced manual X-ray workflows.What Is X-Ray Search and How Does It Work?
According to SHRM's 2025 Recruiting Benchmarking Report, the average time-to-fill sits at 44 days. X-ray search is a technique that can compress the discovery portion of that timeline by letting recruiters bypass a platform's native search and use Google instead.
Here's the concept in plain terms. Every website with public pages gets crawled and indexed by Google. When you search site:linkedin.com/in "data scientist" "Python", you're telling Google: "Only show me results from LinkedIn's profile directory that mention both data scientist and Python." Google becomes the search engine. LinkedIn is just the database.
The name "X-ray" comes from the idea that you're seeing through a website's surface layer into its underlying data. Where LinkedIn's own search might limit results based on your account type, connection degree, or filter availability, Google shows everything it has indexed - regardless of your relationship with the platform.
The basic X-ray formula is simple:
site:[domain/path] "keyword 1" "keyword 2" "location" -exclusions
You can apply this formula to any website with public profiles. LinkedIn is the most common target, but GitHub, Stack Overflow, Twitter/X, Behance, Dribbble, and even personal blog directories all respond to X-ray searches. The technique works because Google's indexing is broader than most platforms' internal search - it captures text from headlines, bios, about sections, and even code repositories.
This approach is particularly valuable for candidate sourcing because it's completely free. You don't need a LinkedIn Recruiter seat, a GitHub Enterprise account, or any paid tool. A browser and knowledge of search operators is all it takes. But free doesn't mean unlimited - there are real constraints, especially after LinkedIn's 2024 indexing changes.
Which Google Operators Still Work for Recruiter X-Ray Searches?
Google removed the cache: operator in September 2024 and the related: operator in July 2023, according to Search Engine Journal's 2024 reporting. But the core operators that power X-ray recruiting remain fully functional. Here's the complete reference for what works today.
| Operator | Function | Example |
|---|---|---|
site: |
Restrict results to a specific domain or path | site:linkedin.com/in |
intitle: |
Keywords must appear in the page title | intitle:"software engineer" |
inurl: |
Keywords must appear in the URL | inurl:projects |
filetype: |
Find specific file types (resumes, CVs) | filetype:pdf "curriculum vitae" |
" " (quotes) |
Exact phrase match | "machine learning engineer" |
- (minus) |
Exclude a term | -jobs -hiring -recruiter |
OR |
Either term matches | "Python" OR "Go" OR "Rust" |
* (wildcard) |
Matches any word | "VP of *" |
AROUND(n) |
Terms must appear within n words of each other | "machine learning" AROUND(3) "Python" |
Operators that no longer work:
cache:- Removed September 2024. Previously let you view Google's cached version of a page.related:- Removed July 2023. Previously found sites similar to a given URL.link:- Deprecated since 2017. Used to find pages linking to a specific URL.info:- Deprecated since 2017. Previously showed page metadata.
The good news: site:, intitle:, quotes, minus, OR, and AROUND(n) are the only operators most recruiters actually need. If you've been using Boolean search on LinkedIn, the transition to Google X-ray is mostly about swapping NOT for the minus sign and adding site: at the start.
Why Is LinkedIn X-Ray Search Broken Since 2024?
In January 2024, LinkedIn removed headline, About section, work experience, education, and location data from Google's public index, as sourcing trainer Jan Tegze documented in his Full Stack Recruiter newsletter. This single change broke the most popular site-operator use case for recruiters worldwide.
Before January 2024, you could run a search like site:linkedin.com/in "software engineer" "Python" "San Francisco" and get detailed results showing candidates' job titles, skills, and locations directly in Google's search snippets. Those days are over. Here's what still works - and what doesn't.
What Google can still see on LinkedIn profiles:
- Name (as it appears in the URL slug and page title)
- The profile headline text in some cases (inconsistent)
- LinkedIn Advice article contributions
- Public posts and article content
What Google can no longer see:
- Detailed work experience and job history
- Education and certifications
- Skills endorsements
- About/summary section
- Location (in most cases)
This means a search like site:linkedin.com/in "software engineer" "Python" "San Francisco" now returns dramatically fewer results, and the results that do appear may not accurately reflect the candidate's current role or skills. The keywords might be matching on fragments that happen to appear in the page's metadata rather than in the rich profile data that used to be available.
LinkedIn X-ray strings that still produce some results (2025):
site:linkedin.com/in "software engineer" "san francisco" -jobs -directory
site:linkedin.com/in (Python OR Go) "senior" -"connect" -"recruiter"
site:linkedin.com/advice/ "Director" "Amazon"
The last example searches LinkedIn Advice pages, where contributors' titles and companies are still indexed. It's a workaround, not a replacement. LinkedIn made this change to push recruiters toward LinkedIn Recruiter, their $10K+/year premium product. For most sourcing teams, LinkedIn X-ray search has gone from a primary tool to a supplementary one. The platforms where X-ray still works well are GitHub, Stack Overflow, and Twitter/X.
Why Is GitHub the Best Platform for X-Ray Tech Sourcing?
GitHub now hosts 180M+ developers globally, with 36 million new developers joining in 2025 alone - that's roughly one new developer every second, according to GitHub's Octoverse 2025 report. Unlike LinkedIn, GitHub profiles remain well-indexed by Google, making it the strongest X-ray platform for technical recruiting in 2025.
GitHub profiles typically show a developer's bio (including location, current employer, and personal website), programming languages used across repositories, contribution frequency, and the kinds of projects they work on. All of this gets indexed by Google, giving X-ray search rich data to match against.
GitHub X-ray strings (verified working 2025):
Machine learning engineer in San Francisco:site:github.com "machine learning" "San Francisco" "data scientist" -intitle:repositories
TypeScript/React developer in Seattle:site:github.com "TypeScript" "React" "Seattle" -intitle:issues -intitle:pull
Open-to-work developers (any language):site:github.com "open to work" OR "open to opportunities" -intitle:issues
Python developer with specific framework experience:site:github.com "Python" ("Django" OR "FastAPI") "senior" -intitle:repositories
Add -intitle:repositories -intitle:issues -intitle:pull to filter out repository and issue pages and focus on user profiles. The -intitle: exclusions keep results focused on actual developer profiles rather than project pages.
Importantly, GitHub sourcing through Google is also uniquely valuable because it shows verified work samples. Unlike LinkedIn - where anyone can claim "Python expert" in a headline - GitHub shows actual code, commit history, and project complexity. A developer with 500 commits to a production Kubernetes project tells you more than any keyword match ever could.
How Do You Use Site-Operator Search on Stack Overflow and Twitter/X?
The 2025 Stack Overflow Developer Survey drew 49,000+ responses from 177 countries, and 76.2% of respondents identified as professional developers. Stack Overflow user profiles are still well-indexed by Google and contain location, top technology tags, and reputation scores - all useful signals for evaluating expertise depth.
Stack Overflow X-Ray Strings
Java developer in California:site:stackoverflow.com/users "java" "california"
Python/ML specialist in New York:site:stackoverflow.com/users "python" "machine learning" "new york"
High-reputation C++ developer:site:stackoverflow.com/users "C++" "computer vision" "software engineer"
Stack Overflow reputation scores act as a rough quality signal. A user with 10,000+ reputation has answered hundreds of community-vetted questions correctly - that's a stronger expertise indicator than most resume bullet points. Look for developers whose top tags match your target skills and whose answer activity shows recent engagement.
Twitter/X X-Ray Strings
Twitter/X is less structured than GitHub or Stack Overflow, but developer bios often contain job titles, tech stacks, and location information that Google indexes.
Data engineer who's open to opportunities:site:twitter.com "data engineer" "open to opportunities" -inurl:status
ML engineer in a specific metro:site:twitter.com "ML engineer" OR "machine learning" "San Francisco" -inurl:status
The -inurl:status exclusion filters out individual tweets and keeps results focused on profile pages. In practice, Twitter/X operator searches work best for developers and tech professionals who actively maintain their bios. They're less reliable for non-technical roles where professionals are less likely to list skills in their Twitter bio.
What Are the Biggest Limitations of Manual X-Ray Search?
Recruiters spend roughly one-third of their workweek on sourcing activities, according to GoodTime's 2025 Hiring Insights Report. Despite that investment, manual site-operator searches have structural limitations that no amount of operator mastery can solve. Understanding these constraints helps you decide when this approach is the right tool - and when it's time to switch to something faster.
1. LinkedIn - the biggest platform - is mostly broken for these searches. After LinkedIn's January 2024 indexing change, the single largest professional database (over 1 billion registered users, per LinkedIn's newsroom) returns inconsistent, incomplete results through Google. If your primary sourcing target is non-technical professionals, this technique lost its most important platform.
2. You can only search one platform at a time. Additionally, the technique requires a separate search for each website. Searching LinkedIn, GitHub, Stack Overflow, and Twitter/X for the same candidate profile means running four separate queries, reviewing four separate result sets, and manually deduplicating across them. That's time-intensive for a single role and nearly impossible to scale across a full requisition load.
3. You need to predict exact keywords. Moreover, this method relies on literal string matching. If a candidate describes themselves as "built cloud infrastructure for a 200-person engineering org" instead of "DevOps engineer," they won't appear in your search for "DevOps." You have to anticipate every possible way someone might describe their skills - and you'll inevitably miss variations you didn't think of.
4. Results degrade at scale. Consequently, Google typically returns 100-300 results per query before accuracy drops. For common role titles in major metro areas, you'll exhaust the useful results quickly and start seeing irrelevant matches. There's no way to page through millions of profiles the way a dedicated candidate database can.
5. No outreach workflow built in. Finally, this approach finds names. That's it. You still need to find contact information, write personalized messages, send outreach across multiple channels, track responses, and schedule follow-ups - all manually. The search is free, but the total workflow cost in time is enormous.
When Should You Switch from X-Ray Search to AI Sourcing?
AI adoption in recruiting climbed from 26% to 43% in a single year, according to SHRM's 2025 Talent Trends report (surveying 2,040 HR professionals). Thirty-two percent of organizations now automate candidate searches with AI. The shift isn't theoretical - it's already happening, and it directly addresses every limitation of manual X-ray search.
Here's specifically what AI sourcing handles that manual operator searches can't:
Semantic understanding. Describe your ideal candidate in natural language - "senior backend engineer who's scaled microservices at a Series B startup" - and AI maps that to matching profiles. No operator syntax, no keyword prediction, no missed variations. AI understands context, not just literal strings.
Multi-source aggregation. Instead of running separate site-operator searches across LinkedIn, GitHub, and Stack Overflow, AI sourcing platforms search across aggregated data sources simultaneously. Pin scans 850M+ candidate profiles with 100% coverage in North America and Europe - the kind of reach that would take weeks of manual X-ray work to approximate.
Built-in outreach and scheduling. Where X-ray ends at "here's a name," AI sourcing platforms handle the entire top-of-funnel workflow: contact discovery, personalized multi-channel outreach across email, LinkedIn, and SMS, response tracking, and interview scheduling. Pin's automated outreach delivers a 48% response rate - well above the typical single-digit rates most recruiters see from cold InMail.
Scale without degradation. Manual operator results get worse after 100-300 results. By contrast, AI sourcing maintains accuracy across millions of profiles because it's matching on semantic relevance, not keyword frequency.
As Laura Rust, Founder and Principal at Rust Search, explains: "Pin helps me find needle-in-a-haystack candidates with real precision, like filtering by company size during someone's tenure, so I can zero in on the right operators for a specific stage."
Pin's AI handles sourcing, outreach, and scheduling in one workflow - try it free.
How Does X-Ray Search Compare to AI Sourcing?
According to SHRM's 2025 data, 69% of HR professionals now use AI for recruiting tasks. Nevertheless, manual Google operator searches still fill a practical role for specific scenarios. Here's when each approach makes sense.
| Dimension | X-Ray Search | AI Sourcing |
|---|---|---|
| Cost | Free | From $100/mo (Pin) to $10K+/yr |
| Search input | Google operators and keywords | Natural language descriptions |
| LinkedIn effectiveness | Severely limited since Jan 2024 | Full access to aggregated profile data |
| GitHub/SO effectiveness | Strong - profiles fully indexed | Also strong - plus contact info included |
| Database scope | One platform per search | 850M+ profiles across sources |
| Outreach built in | No - manual process required | Yes - email, LinkedIn, SMS automated |
| Speed | Minutes to hours per search | Seconds to minutes |
| Best for | Quick tech sourcing on GitHub/SO, budget-constrained teams | Full-cycle sourcing, high-volume hiring, non-technical roles |
In practice, the answer for most teams is straightforward: use Google operator searches for quick, targeted tech sourcing on GitHub and Stack Overflow where profiles are still richly indexed. Use AI sourcing for everything else - especially LinkedIn-heavy roles, high-volume hiring, and any scenario where you need outreach automation. For a full breakdown of the platforms available, see our 2026 guide to sourcing tools for recruiters.
How Do You Find Resumes and CVs with the Filetype Operator?
Beyond searching platform profiles, the filetype: operator can surface actual resume and CV files that candidates have uploaded to personal websites, university directories, or portfolio platforms. According to ERE Media's sourcing research, filetype searches remain one of the most underused techniques among recruiters - yet they tap into a pool of candidate data that no social platform indexes.
Basic resume X-ray formula:filetype:pdf "software engineer" "Python" "San Francisco" -jobs -template -sample
This searches Google's index for PDF files containing those keywords. Add -template -sample -example to filter out resume template websites that contaminate results. You can also target Word documents with filetype:docx, though PDFs are far more common.
University directory search:site:*.edu filetype:pdf "resume" "computer science" "machine learning" 2024 OR 2025
University career centers often host student and alumni resume books as PDFs. Adding year terms helps filter for recent graduates. This is particularly effective for entry-level technical recruiting where LinkedIn profiles may be sparse.
Portfolio site search:filetype:pdf "UX designer" "portfolio" ("Figma" OR "Sketch") "resume"
Designers frequently host PDF portfolios and resumes on personal domains. The filetype search finds these even when the designer's website doesn't appear in standard Google results.
A word of caution: resume files found through X-ray may be outdated. Someone's 2022 resume won't reflect their current role or skills. Always cross-reference what you find with their LinkedIn profile or other current sources before reaching out. Contacting someone about a role they held three years ago is a quick way to lose credibility.
What Are the Best Google Operator Strings for Recruiting?
According to SHRM's 2025 Talent Trends report, 69% of organizations still struggle to fill roles - which means the right search string can be the difference between an empty pipeline and a full one. These 10 strings are tested and working as of 2025. Each includes the site: operator, role-specific keywords, and common exclusions. Customize the location and skill terms for your specific search.
GitHub Strings (Strongest for Tech Roles)
Senior Python developer:site:github.com "Python" ("Django" OR "FastAPI" OR "Flask") "senior" -intitle:repositories -intitle:issues
Frontend React/TypeScript developer:site:github.com "React" "TypeScript" ("frontend" OR "front-end") -intitle:issues -intitle:pull
DevOps/infrastructure engineer:site:github.com ("Kubernetes" OR "Terraform" OR "Docker") ("infrastructure" OR "DevOps" OR "SRE") -intitle:repositories
Mobile developer (iOS or Android):site:github.com ("Swift" OR "Kotlin") ("mobile" OR "iOS" OR "Android") -intitle:issues -intitle:topics
Stack Overflow Strings
Data scientist:site:stackoverflow.com/users "python" "machine learning" OR "data science"
Backend Java developer:site:stackoverflow.com/users "java" "spring" OR "microservices"
LinkedIn Strings (Limited Post-2024)
Generic professional search (reduced accuracy):site:linkedin.com/in "product manager" "SaaS" -jobs -directory -company
LinkedIn Advice contributor search (workaround):site:linkedin.com/advice "VP of Engineering" OR "Director of Engineering"
Twitter/X Strings
Developer open to opportunities:site:twitter.com ("software engineer" OR "developer") "open to" -inurl:status
Design professional:site:twitter.com ("UX designer" OR "product designer") ("portfolio" OR "design system") -inurl:status
Start with these templates and iterate. The best X-ray strings evolve through testing - run the search, scan the first 20-30 results, and tighten or broaden based on what you see. Add more OR variations for job titles if volume is low. Add more exclusions with the minus sign if results are cluttered with irrelevant pages.
One practical tip: bookmark your best-performing strings. A strong X-ray query for "senior Python developer in Austin" works just as well three months from now as it does today - and you won't have to rebuild it from scratch. Create a shared document with your team's top strings organized by role type and platform. This turns one-off searches into a reusable sourcing library that gets better over time.
Frequently Asked Questions
Does X-ray search still work on LinkedIn in 2025?
Partially. LinkedIn removed detailed profile data (work experience, education, skills, location) from Google's index in January 2024. You can still find LinkedIn profiles through X-ray, but the results are incomplete and unreliable for filtering by specific roles or skills. GitHub and Stack Overflow are now stronger X-ray targets for technical recruiting. For non-technical LinkedIn sourcing, AI platforms scanning 850M+ profiles deliver more consistent results.
Is X-ray search legal for recruiting?
Yes. X-ray search only accesses publicly available information that's already indexed by Google. You're not scraping data, bypassing paywalls, or accessing private profiles. It's the same as typing any other Google search. That said, always comply with local data protection regulations (GDPR in Europe, for example) when collecting and storing candidate information you find through X-ray searches.
What is the best alternative to X-ray search for sourcing?
AI-powered sourcing platforms are the most direct replacement. They search across aggregated candidate databases - Pin searches 850M+ profiles - using natural language instead of operators, and include built-in outreach and scheduling. For teams spending a third of their workweek on manual sourcing (GoodTime, 2025), AI platforms reduce that to minutes while maintaining better accuracy across non-technical roles.
How do I X-ray search for candidates on GitHub?
Use this formula: site:github.com "[skill]" "[location]" -intitle:repositories -intitle:issues. GitHub profiles are well-indexed by Google and show bio, location, programming languages, and project activity. With 180M+ developers on the platform (GitHub Octoverse, 2025), it's the strongest X-ray target for technical recruiting. Add language-specific terms and exclude non-profile pages with -intitle: operators.
Can X-ray search find candidates that LinkedIn Recruiter can't?
It used to - before January 2024, X-ray search could surface public LinkedIn profiles without requiring a Recruiter seat. Now that LinkedIn has restricted Google indexing, X-ray search actually finds fewer LinkedIn candidates than LinkedIn Recruiter does. Where X-ray still excels is on other platforms: GitHub for developers, Stack Overflow for technical specialists, and Twitter/X for professionals who maintain detailed bios. Combining X-ray across these platforms with AI sourcing for LinkedIn gives you the broadest reach.
Is X-Ray Search Still Worth Learning in 2025?
Absolutely - but with caveats. Google operator sourcing remains a valuable skill for any recruiter's toolkit. On GitHub and Stack Overflow, it's still the fastest free way to find technical candidates with verified work samples. The syntax is straightforward, the cost is zero, and the ability to search inside any publicly indexed website gives sourcers reach that platform-native search can't match.
However, the landscape has shifted significantly. LinkedIn's 2024 indexing restrictions removed the technique's most important use case. Google operator deprecations have trimmed the toolkit. And with 43% of organizations already using AI for HR tasks (SHRM, 2025), the gap between manual workflows and AI-powered sourcing is widening every quarter. Recruiters who relied on this method as their primary sourcing approach now need a broader strategy.
Ultimately, the most effective sourcing strategy combines both. Use Google operator searches for quick GitHub and Stack Overflow searches when you need verified technical talent fast. Use AI sourcing for high-volume hiring, non-technical roles, and any workflow where you need outreach, scheduling, and candidate management built into the search itself.
Search 850M+ profiles with Pin's AI sourcing - free to start
