How to use Boolean search for LinkedIn prospecting

LinkedIn documents five constructs: uppercase AND, OR and NOT, straight quotation marks, and parentheses. It evaluates quoted phrases first, then parentheses, then NOT, then AND, then OR. That order is why an ungrouped OR can bypass a requirement you meant to apply to every title.

Wildcard asterisks, plus and minus signs, and square, curly or angle brackets are not supported. A string copied from Google or a recruiting database may use syntax that does not belong in this search. LinkedIn also drops some common stop words, such as in, by and with, so check returned records instead of treating a quoted phrase as a character-for-character match.

Each string below stays well under Sales Navigator's 15-operator limit and uses only documented syntax. Paste it into the box named in the second column, then apply location, industry or company-size criteria with the separate filters. The last column names the most common way the string misleads you.

These are starting points. No searches were run to produce this table, and it makes no claim about result counts or reply rates. Swap in the titles your buyers actually use, and keep the string short enough that you can explain why each person appeared.

LinkedIn's Sales Navigator help page says Boolean search works in three places: the Keywords box, the Title filter and the Company filter. Its query-limit page sets a maximum of 15 Boolean operators per Sales Navigator query. Both pages require uppercase operators and straight quotes.

Other Sales Navigator filters, such as geography, industry and company headcount, are chosen from lists rather than typed as expressions, and the help page does not list them as Boolean fields. Apply them alongside your typed expression instead of trying to write location or industry into a keyword string.

A typical split: put ("VP Sales" OR "Vice President of Sales") in the current Title filter, SaaS in Keywords only if you need the mention, and pick region and headcount from the list filters. That keeps each condition in the field that matches its purpose, and a long string is less likely to hit the operator limit.

For standard LinkedIn search, LinkedIn documents Boolean in the main search box at the top of the page. People search also shows Title and Company inputs under All filters, but the help page reviewed here does not say whether those accept Boolean. Test a short expression there and inspect the results before relying on it. LinkedIn says consumer search has an operator limit without publishing the number.

Use the free Boolean search builder to group alternative titles with OR, add required terms with AND, and exclude terms with NOT. It shows the generated query and explains the logic before you copy it. Generation runs locally in your browser and does not collect profiles.

To review an expression you already have, use Check an existing Boolean query. It checks pasted text locally for common syntax errors and contextual cautions without changing it. The checker and builder have separate inputs.

Choose the destination field first. A query combining role names with SaaS belongs in a broad keyword search. For a Sales Navigator Title search, build the role group alone and apply company criteria separately. A correct expression in the wrong field can still hide relevant people.

The optional Open LinkedIn people search button sends only the generated query to LinkedIn in a new tab’s search URL. It may appear in your browser history, and LinkedIn may require sign-in. Text pasted into the separate checker is not sent by this button. For Sales Navigator or Recruiter, copy the query into the appropriate search field instead.

Suppose you help services firms improve client handoffs. You might want people currently responsible for operations or client delivery at a reviewed set of companies. That gives you two different tasks: select the companies, then find plausible role holders. Putting every company characteristic into one profile keyword string makes those tasks harder to distinguish.

List the role variants you would genuinely consider. Separate requirements from helpful context. If someone can do the relevant work without using a particular phrase on their profile, that phrase should not automatically become mandatory. Conversely, adding unrelated titles simply to increase the count makes the review work larger.

Write down what would disqualify a record and how you could verify it. A current employer outside your target list is different from a profile that mentions a past employer. Search can help surface candidates, but a keyword expression cannot establish company fit or purchasing authority.

Compare operations OR marketing AND SaaS with (operations OR marketing) AND SaaS. In the first expression, AND binds more tightly than OR. An operations match can therefore pass without SaaS. In the second, the grouped choice must also satisfy SaaS.

The table below uses four fictional records with only the stated terms. It illustrates logical matching, not LinkedIn's index, personalization, visibility or live result counts. No people were searched to produce it. Both expressions can be valid syntax while answering different questions.

Blair is the important row. The ungrouped expression admits that record through its operations branch; the grouped expression does not. If SaaS is essential to this particular keyword exercise, the first query is wrong even when its results look professionally relevant. It still takes a separate check to determine whether a SaaS mention describes the person's current employer.

Use available current-title criteria for the role you want now, company filters for the employer, and geography filters for location. A broad Keywords field can match text elsewhere in a profile. Someone may mention marketing while describing an earlier job, a volunteer project or a team they collaborated with.

This distinction is especially important for NOT. Imagine a current operations director whose earlier experience includes an assistant role. A profile-wide exclusion of assistant could remove a relevant person. If your concern is current responsibility, inspect the current role and use a suitably scoped title filter rather than excluding the person's entire history.

Sales Navigator accepts Boolean only in some boxes, as the section above describes, and its list filters are not text boxes that accept an expression. Start with the field's purpose, then enter the smallest query that answers your question.

The Prospeo Sales Navigator tutorial discusses the difference between broad keywords and title searches around 3:08. Evaboot's masterclass illustrates profile-wide matches around 2:23. Those demonstrations are useful context, but neither establishes that a matched tool, sector or phrase is a current company characteristic.

For an operations-focused service, start with ("Head of Operations" OR "Operations Director"). Apply your reviewed company criteria separately. Open a few results and see whether those titles describe the work you mean. The answer may suggest another title, a narrower responsibility or a different type of company.

For a revenue-operations service, an initial role group could be ("Revenue Operations" OR RevOps). For client-delivery research, try ("Client Services Director" OR "Delivery Manager"). These are starting hypotheses, not interchangeable audiences. A delivery manager in a software engineering team may be irrelevant to a consultancy focused on client onboarding.

If context is genuinely necessary, test it as a separate requirement in the appropriate field. For example, (operations OR delivery) AND onboarding asks a different question from the title-only search. It may also miss suitable people who describe onboarding differently or omit it. Review that tradeoff before turning every desirable detail into an AND condition.

Keep a clean copy outside the search box. Straight quotes and balanced parentheses are easier to inspect in a short plain-text expression than in a long string copied from a styled document. An AI query builder can propose terms, but you still need to check the operators, field and actual matches.

Save the initial expression and filters before refining them. Review a manageable sample of returned profiles, recording why each is relevant, irrelevant or unresolved. You can use the first ten visible records for a quick diagnostic, provided you do not treat a small, ranked sample as a representative estimate of the whole result set.

Then change one thing. Add a title variant, remove a mandatory keyword or revise an exclusion. Check both newly included records and known relevant records that disappeared. A smaller count can indicate cleaner targeting, excessive filtering or simply a different question; the number alone cannot tell you which.

Use separate searches when the audience contains genuinely different role families. That keeps each expression understandable and makes its mistakes easier to diagnose. Combine reviewed records carefully afterward so the same person is not treated as two separate leads.

A copied string ending with a long list of excluded titles may look thorough. It can also discard experienced people whose profiles mention an old role, mentorship or recruitment responsibilities. Add an exclusion only when you understand the recurring false match and the scope it affects.

If LinkedIn’s help seems to give conflicting advice about quotes, check which kind of search it describes. Its People-search page says natural-language queries do not support quotes and recommends Boolean search for exact keyword matching. Its Boolean-search page supports straight quotes around phrases. Keep those quotes in a Boolean expression; the guidance to leave them out applies to natural-language queries.

For a copied expression, paste it into Check an existing Boolean query and select Check query. Review the errors and cautions, correct the expression manually, then test it in the intended LinkedIn field. For example, ("Head of Operations" OR "Operations Director") AND is missing a condition after AND: add the intended condition or remove the trailing operator. This is a syntax illustration, not a tested search. No issues found in these checks does not prove that LinkedIn will accept the expression or that its results will fit your audience.

If a query is rejected, shorten it and check the interface before assuming the account is broken. LinkedIn's query-limit page currently specifies a maximum of 15 Boolean operators for Sales Navigator. It says consumer search has a limit without publishing a numeric value on that page, and that Recruiter and Recruiter Lite have no operator-count limit. These statements do not describe result caps, unrestricted usage or permission for automated collection.

After reviewing a profile, retain enough context to explain why it belongs in your working list. OutreachGenie's named prospect lists, custom fields and notes can hold a manual record of the current company, title, profile URL, review date and relevance note. The search expression can go in a note if it will help reproduce the research.

For the handoff consultancy, a useful note might read: 'Current role covers client delivery; company is in the reviewed account list. Onboarding responsibility not confirmed. Ask about ownership before proposing a project.' That is more actionable than retaining the word match alone. It also makes the uncertainty visible to the next person using the record.

Run the search in LinkedIn and assess each result yourself; the CRM record preserves your research, not an automatic verification. LinkedIn's rules restrict certain third-party scraping and automated activity. A working query or a vendor demonstration does not grant permission to export, collect or contact everyone it returns.

For your next search, keep the first version short enough to explain aloud. Review the records it produces, identify one specific mistake and make one justified change. You will leave with a search you understand and a reason for the people you kept.