Google operators for people research

Operators are how you ask Google for a page, not a person. A good query returns a team page, a talk, a byline, or a speaker bio PDF you can open. A bad query returns a pile of lookalikes and a temptation to click through a login. This guide documents five operators only: quotes, site:, OR, minus, and filetype:pdf. Those are enough for public-web people research. They are not a way around authentication, paywalls, or systems you are not allowed to use.

You do not need OneSearch to run these queries. You do need the same gates: confirm before you brief, stay in conversation prep, and do not treat results as a background check. OneSearch is not a CRA. Read FCRA and legal use. This page is not legal advice. See OneSearch vs Google when a confirm-first brief is the better tool than another tab.

Why operators, not more tabs

Twelve tabs usually means you typed the name, got a collision, and started opening everything that looked plausible. Operators shrink the set before you open. That is the only job. They do not make a result true. They do not confirm identity. They do not authorize you to read a PDF that sits behind a login. After the page is open, you still verify the claim on the original URL — verify a people-research claim — and you still run confirm the right person before a paragraph exists.

Use the builder to see the first four query shapes. It is a teaching control. It does not search OneSearch. Copy a line into Google. Change the name, company, and city to the breadcrumbs you already have — not breadcrumbs you wish you had.

The five operators

This page will not document other operators. Extra operators on a wrong identity produce a cleaner wrong brief. The five below are the ones this desk will stand behind.

• Quotes — keep a full name (or a talk title) as one phrase.
• site: — stay on one host, or one public path you already have a right to read.
• OR — allow any of a small set of public-artifact words (talk, podcast, interview, bio, speaker).
• Minus — drop an obvious collision token after you have seen it, not before.
• filetype:pdf — prefer a speaker bio, slides, or a paper that is already public.

Google's own documentation is the source of truth for syntax. See Refine web searches in Google Search Help for quotes, site:, OR, minus, and filetype. If a query stops working, change the breadcrumbs. Do not invent a sixth operator to force a hit.

Quotes

Quotes tell the engine to keep a phrase together. For people research that phrase is almost always the full name as written on the invite: "Alex Chen", "Maria Garcia". Without quotes, Alex and Chen can appear in different sentences about different people. With quotes, you still get collisions — the phrase is common — but you stop matching pages that merely contain both tokens.

Also quote a talk title or a product name once you have it from the invite or an introducer: "Alex Chen" "tail latency". Do not quote a theory. If you are not sure they used those words, leave them out. Quoted guesses hide the pages that would have confirmed a different wording.

Failure mode: quoting a nickname you invented, or quoting company plus name as one phrase when they never appear that way. Quote the name. Leave the company outside the quotes unless you have already seen that exact string on a page.

site:

site: restricts results to a host. Use it when you already know where a public page should live: the employer domain, a conference domain, a publication, or a public profile host. Pattern: "Alex Chen" site:stripe.com. The builder also emits site:linkedin.com/in because a public profile path is a candidate card. A public LinkedIn page is still not a confirm by itself — headlines go stale — but it is a better card than a random directory.

Prefer the company host before social hosts. Team pages and bylines are dated more often than profiles. Try the domain on the invite first. Do not use site: to hunt admin paths, staging hosts, or internal hostnames you are not entitled to read. If Google shows an internal hostname, you still need authorization. Close it if you do not have it.

Failure mode: site: on a host that never lists people, then concluding the person does not exist. Failure mode: chaining so many site: ideas that you never look at the open web. One host per query. Then a second query if the first is empty.

OR

OR (uppercase) means any of the terms may match. Use it for a small set of public-artifact words, not as a synonym dump. The useful set for this desk is: (talk OR podcast OR interview), sometimes (bio OR speaker OR author). Pattern: "Maria Garcia" (podcast OR interview) port. That query is how you find something you can quote.

Keep the OR group to three or four words that name a kind of page. Do not OR together every company they might have worked at — that re-creates the collision. Do not OR hobbies you invented. A returned talk is a find, not a personality you may invent.

Failure mode: lowercase or, which Google may treat as noise. Failure mode: a twelve-term OR group that matches every page on the internet that mentions the name. If the first page is unrelated, shrink the group, do not grow it.

Minus

A minus sign immediately before a token excludes pages that contain it. Use minus only after you have seen a collision and can name the token that is unique to the wrong person. Pattern, after you have seen the Austin founder: "Alex Chen" Stripe -Austin -logistics. Pattern, after you have seen the Madrid journalist: "Maria Garcia" Miami logistics -Madrid.

Do not minus on the first query. You will drop the page that would have confirmed the person because it happened to mention the excluded city in a travel sentence. Do not minus common words like -the or -inc. Do not minus a last name. The minus is a scalpel for a token you have already associated with a lookalike card: a city, a school, a company, a sport, a middle name.

Failure mode: excluding so aggressively that only one page remains — the wrong page that lacked the excluded words. If the set collapses to a single unexpected host, remove the minus and look at faces again. Minus is not a confirm. It is a way to stop seeing a card you have already rejected.

filetype:pdf

filetype:pdf asks for PDF files. In people research that usually means speaker bios, slide decks, academic pages, or public company filings that already name the person. Pattern: "Alex Chen" latency filetype:pdf. Pattern: "Maria Garcia" speaker filetype:pdf. A speaker bio PDF with a photo, a company, and a talk title is often the unique artifact that ends a collision.

Treat every PDF as a page you must be allowed to have. Conference sites and personal academic pages are the usual legitimate sources. A PDF that looks like an internal resume pack, an offer letter, or a directory export is not a research win. Do not download it to "see if it helps." Close it. Do not forward it. It is not a source for a brief.

Failure mode: treating a PDF as more true because it is a file. PDFs go stale. Write the year from the conference site. You need one artifact, not every PDF on the first page.

Query patterns

Run them in this order. Copy the strings. Do not rewrite mid-flight because a tempting headline appeared. Add one breadcrumb at a time.

1. "Full Name" Company City — the open-web first page. You want a team page, news, or a talk.
2. "Full Name" site:linkedin.com/in — candidate cards only.
3. "Full Name" site:company.com — employer host. Swap in the real domain; do not guess exotic TLDs.
4. "Full Name" (talk OR podcast OR interview) — something you can quote.
5. "Full Name" Company filetype:pdf — only if you still need a speaker bio or slides.
6. Minus a lookalike token — only after you have seen the collision and named the token.

If level 1 is all other people, add one breadcrumb you already had (product name, introducer company, talk topic). If level 1 is empty, you may have over-quoted or used a company name they never publish. Widen before you add operators. Researchers use the same order when the person is a source, not a meeting — sourced people research.

What you write down from each query is a list of cards: role, city, one hint, URL. Then you pick. Then you extract. Google found the page; you still do the confirm. That split is OneSearch vs Google: general search finds pages; a confirm-first brief holds the person still.

Worked example: Alex Chen

Invite: Alex Chen, Stripe, payments latency. You already know from Priya that there was a latency talk last year. You assume collision. You will not minus yet.

Queries you actually run, in order:

• "Alex Chen" Stripe "San Francisco"
• "Alex Chen" site:linkedin.com/in
• "Alex Chen" site:stripe.com
• "Alex Chen" (talk OR podcast OR interview) latency
• "Alex Chen" latency filetype:pdf — if you need the slides to match a face to a team page.

What you should see, and refuse to merge: SF staff engineer, payments, conference talk on tail latency, GitHub org commits; NYC principal at a quantitative shop, faculty page, different middle initial on a PDF; Austin founder, logistics podcast last month, different face. After you have seen Austin, a later query may add -Austin -logistics. Do not add those minuses on query one — the podcast is how you learned the lookalike existed.

Confirm: team page plus talk recording plus slides PDF agree on face and employer. The NYC PDF is a different person. Extract three facts with URLs. The walk-in question quotes the p99 constraint and dates the talk. You needed the talk title as a breadcrumb and the discipline not to merge — not a sixth operator.

If site:stripe.comis empty, that is not proof they do not work there. Team pages are often thin. Fall back to the talk query. Empty employer host is a missing page, not a negative screen. If someone asked you to "make sure they're clean," you should not be in this query list — that is eligibility, and this is not a CRA workflow.

Worked example: Maria Garcia

Intro email: former VP of operations, Miami logistics company, trade podcast last quarter on port delays. High collision. Title plus city beats a middle initial. You will not quote "supply chain" as if it were an identity.

Queries:

• "Maria Garcia" logistics Miami
• "Maria Garcia" site:linkedin.com/in
• "Maria Garcia" (podcast OR interview) port
• "Maria Garcia" Miami filetype:pdf speaker
• After you have seen the Madrid bylines: "Maria Garcia" Miami logistics -Madrid

Cards you must keep separate: Miami ops leader (podcast show notes, company name, badge photo); Madrid journalist (supply-chain bylines, different face); Texas school-board member (district site); LA nonprofit director if a port-adjacent event page appears. TheOR group is what finds the podcast. The minus is what stops you from reopening Madrid after you have rejected that card. The PDF query is only useful if a speaker bio ties the episode to the company. If the PDF is a different Maria at a different conference, it is another card, not a bonus fact.

Confirm line: show notes plus badge photo plus company. If the photo matches nobody else, do not merge with the journalist because both pages mention ports. Ask the organizer. Operators cannot finish a confirm the pages will not support.

Do not add filetype:pdfto harvest bios from a members-only group. If the file asks you to sign in, you do not have it. Do not use minus to hide unflattering public pages about the person you already confirmed. Minus is for lookalikes, not for editing someone's public record. If the job is eligibility, you should not be building this set.

What operators cannot do

• Confirm identity. They rank pages. You still pick a card. Two pages that both match the query can be two people.
• Make a thin web thick. If they barely exist online, extra operators will not invent a talk. Accept the silence.
• Date a fact. You open the page and read the date. A first-page result can be ten years old.
• Replace a CRA. No combination of quotes and filetype:pdf is a background check. Do not run these queries to decide hire, tenant, credit, or insurance.
• Find contact waterfalls. That is a different product. Operators that surface a public email on a conference site are incidental. Do not build a scrape.
• Authorize access. A result is not permission. See the next section.

Unauthorized access

Stop if a result is not a page you are allowed to open. Operators are not a technique for getting into accounts, behind logins, past unpaid paywalls, or into someone else's email, ATS, CRM, or Drive. Do not use site: or filetype:pdf to hunt for credentials, private resumes, offer letters, or leaked exports. Do not bypass authentication or access controls. If you are not the intended reader, close the tab.

Public means indexed and open: a team page, a news story, a talk posted by the conference, a PDF the author put on a personal site. It does not mean "Google found a URL." Finding a URL does not make use lawful. This guide will not help you interpret a leaked file. When in doubt, do not use the page. Ask for a public source, or walk in thin.

Harassment and stalking are not research. Do not use these operators to locate a home address or a family member so you can show up. If your purpose is eligibility, you need a CRA process, not a cleverer query. If your purpose is a meeting, you need one public artifact and a question.

When to stop Googling

Stop when you can write the confirm line, or when you can write that you cannot. Both are finished states. Three to five dated pages is enough. Close the set. Write six lines. Walk in. The clock is in research someone before a meeting.

Stop when two cards still fit. Operators will not break a tie the breadcrumbs cannot break. Ask the organizer. Stop when the next query needs an undocumented operator or a host you are not allowed to read. Stop when someone asks you to turn the list into a screen.

Google is the right tool when you need a specific page you will open yourself. A sourced brief is the right tool when you already know which person you mean and you want the next questions attached to that page. Do not ask operators to become a dossier. They will only become a cleaner pile of tabs.