How to use Boolean search for LinkedIn prospecting

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.

LinkedIn documents uppercase AND, OR and NOT, straight quotation marks, and parentheses. Its help page does not support wildcard asterisks or alternative grouping brackets. Use the documented operators instead of plus and minus signs. A string copied from Google or a recruiting database may use syntax that does not belong in this search.

Think of OR as a choice between acceptable alternatives. AND adds a requirement; it does not mean that two job titles are synonyms. NOT excludes matches in the field being searched, which can be broader than the person's current role. Keep that field scope in mind before adding an exclusion.

LinkedIn evaluates phrases and groups before NOT, then AND, then OR. Parentheses make your intended grouping explicit. Quotes are useful for phrases, but LinkedIn also notes that some common stop words are not used in processing. Check returned records instead of assuming a quoted phrase is a strict character-for-character test.

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 exposes several search fields and filters, but their availability and behavior should be checked in your account. A selection filter is not necessarily a text box that accepts 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 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.