LinkedIn Boolean Search: What LinkedIn Actually Supports

A search string with square brackets and an asterisk in it returns a page of results on LinkedIn, and the results are wrong. Nothing announces the problem. LinkedIn treats those characters as ordinary text rather than as grouping symbols or wildcards, so the query still runs and quietly matches something other than what was asked. The string looks sophisticated, the result set looks plausible, and the list built from it is off.

LinkedIn's own help pages set out exactly which operators work, and the supported set is smaller than most Boolean guides suggest. Reading the actual specification takes about four minutes and removes most of the reasons a string misbehaves.

What LinkedIn publishes as supported

LinkedIn's help article on using Boolean search, which the page itself timestamps as last updated five months before this was fetched on 1 September 2026, names four operators and two grouping devices.

AND returns results containing every term in the list. OR returns results containing any of them. NOT excludes a term. Quotation marks match an exact phrase. Parentheses group logic so that a complex expression evaluates in the order you intended.

Two conditions attach to that list, and both cause silent failures when they are missed.

The first is capitalisation. LinkedIn's help page states that when using AND, NOT and OR, "you must type them in uppercase letters for the search to work correctly". A lowercase and is not an operator. It is a keyword, and the search dutifully looks for profiles containing that word.

The second is stop words inside quoted phrases. The same page notes that in order to optimise overall site performance, stop words such as by, in and with "are not used". A quoted phrase built around one of those words is not matching the phrase you typed.

What silently does nothing

This is the part that costs people lists. LinkedIn's help page is explicit: "LinkedIn does not support braces { } , brackets [ ] , angle brackets < > , or wildcards like asterisks * in Boolean searches". It adds that while the plus and minus operators may appear to work in some cases, they are not officially supported, and recommends AND in place of plus and NOT in place of minus.

Boolean guides on prospecting blogs are full of asterisk wildcards, because wildcards work on other search engines and on some applicant tracking systems. On LinkedIn the asterisk is a character in your query. A search for engineer* looks for that literal string.

SupportedPublished on LinkedIn's help page

• AND, OR and NOT, in uppercase only
• Quotation marks for an exact phrase
• Parentheses for grouping
• A stated order of precedence

Unsupported and silentNamed on the same page

• Braces, square brackets and angle brackets
• Asterisk wildcards
• The plus and minus operators, unofficial at best
• Lowercase and, or, not, which read as keywords

Nothing in the second column produces an error message. That is the whole problem. A broken Boolean string on LinkedIn fails by returning a different, smaller, wrong-shaped result set, and the only way to notice is to sanity-check the output against a query you already know the answer to.

The order of precedence, which fixes most broken strings

A string that returns roughly the right people plus a large group of obviously wrong ones is usually a precedence problem rather than an operator problem. LinkedIn sets out its evaluation order on the same help page, beginning with quotation marks, where "Phrase matching occurs before any Boolean logic is applied", and it is worth committing to memory.

1. Step 1Quoted phrases

   Exact phrase matching happens before any Boolean logic is applied at all.

2. Step 2Parentheses

   Grouped expressions are evaluated before ungrouped logic, and parentheses are the only grouping symbol LinkedIn recognises.

3. Step 3NOT

   Applied once quotes and parentheses have resolved.

4. Step 4AND

   Evaluated after NOT and before OR.

5. Step 5OR

   Lowest precedence of the Boolean operators, which is why an ungrouped OR list swallows the rest of the query.

OR sitting at the bottom explains the single most common defect. Try VP sales OR marketing and the low precedence of OR means the query is not asking for a VP in either function. Group it, as LinkedIn's own example does, and the intent survives: VP NOT (assistant OR SVP) excludes both of the grouped titles from the VP set.

The operator cap, which almost nothing else mentions

LinkedIn runs a separate help page on Boolean query limitations, and it carries a number that changes how you build strings for prospecting. The page states that on the consumer search engine "we place a limit on the amount of Boolean search operators used in a single query", and gives two reasons: keeping the free search engine fast, and that by limiting the number of operators "we also secure our members by deterring profile scraping". That page timestamps itself as last updated two years before the 1 September 2026 fetch.

The limits then split by product. Recruiter and Recruiter Lite have no operator cap, because LinkedIn describes them as built for professional search users. And for Sales Navigator, in LinkedIn's own words, "you can use a maximum of 15 Boolean operators in a single search query".

Fifteen is a real constraint on a prospecting string. A title expression covering six seniority variants and excluding four adjacent functions is already at or past it. No number for consumer search appears anywhere on that page, so anyone giving a specific figure for free LinkedIn search is supplying something LinkedIn itself does not, and the honest way to find your own ceiling is to lengthen a string until the results stop changing.

The practical consequence is to stop treating the keyword box as the whole targeting mechanism. In Sales Navigator, seniority, function, headcount, geography and tenure are structured filters, and a filter costs no operator budget. Spend the fifteen on the thing filters cannot express, which is almost always the title vocabulary a market uses for one role. Sales Navigator lead generation covers how those lists behave when you go to export them, which is a separate and larger problem.

Where a Boolean string genuinely belongs in an outbound build

Boolean search on LinkedIn does one job well: discovering what a role is actually called inside a market you do not know yet.

Run three or four competing title strings, look at who comes back, and the vocabulary settles quickly. Head of Revenue Operations and Sales Operations Manager may be the same seat in a market, or two seats, and no amount of desk research settles it faster than reading forty profiles that the strings disagree about. That output feeds a written target definition, which is the thing the rest of the programme runs on. What that definition has to contain is in ideal customer profile.

What Boolean search does not do is produce a contact list. LinkedIn shows you who sits in a role and hands out no verified work email addresses, so the resolution step happens somewhere else, through a provider sequence that stops at the first confident answer. The economics of that ordering are in waterfall enrichment.

There is also a line worth staying on the right side of while doing any of this. The limitations page gives profile scraping as one reason the cap exists, in its own words that by limiting the number of operators "we also secure our members by deterring profile scraping". What the User Agreement says about automation, and what it costs an account to test it, are in what LinkedIn's terms say about scraping.

When the results look wrong

• ✓Yes: Every AND, OR and NOT is in uppercase
• ✓Yes: Every OR list is wrapped in parentheses of its own
• ✓Yes: No braces, square brackets or angle brackets appear anywhere in the string
• ✓Yes: No asterisk is being used as a wildcard
• ✓Yes: Quoted phrases do not depend on a stop word to carry their meaning
• ✓Yes: The operator count is inside the product's cap, which is 15 on Sales Navigator
• ✓Yes: Structured filters are carrying seniority, geography and headcount rather than the keyword box
• ~Depends: The string was checked against a query whose correct answer you already know

The mistake that survives a perfect string

A string that returns exactly the right two thousand people is a targeting artefact and not a programme, and on LinkedIn the constraint downstream of it is acceptance rather than volume.

Ignored and pending invitations are one of the restriction triggers set out in LinkedIn prospecting, so a bigger list drawn the same way applies the same acceptance rate to more people and grows the pending pile faster than it grows pipeline. That is the argument for narrowing a Boolean string well past what the operator cap forces. What LinkedIn does and does not disclose about invitation limits is in the connection limit page.

Our own position sits underneath that. We run one message per campaign, and we do not run LinkedIn re-touches on people who did not reply, because a second message lands directly beneath the first in the same thread and reads as a bump whatever the campaign structure calls it. The first message therefore has to do all of the work, which makes the quality of the Boolean string upstream matter more than it would in a programme willing to send four times.

The short version

LinkedIn supports AND, OR and NOT in uppercase, quotation marks for exact phrases, and parentheses, which its help page calls "the only grouping symbols LinkedIn.com recognizes". The same page puts braces, square brackets, angle brackets and asterisk wildcards outside the supported set, and treats the plus and minus operators as unofficial. None of the unsupported characters produces an error, so a broken string returns a wrong result set rather than a warning.

Precedence runs quotes, then parentheses, then NOT, then AND, then OR. OR sitting last is why an ungrouped OR list behaves nothing like the query you had in mind.

A cap on consumer search exists with no figure attached to it, there is no cap on Recruiter or Recruiter Lite, and for Sales Navigator the limit is "a maximum of 15 Boolean operators in a single search query". Structured filters cost none of that budget, so spend the operators on title vocabulary and let filters take everything else.

Use Boolean search to learn what a role is called in a market and to write a target definition you can defend. Resolve contact details elsewhere, keep the list narrow enough that acceptance stays plausible, and remember that the string is the cheapest part of the programme to fix.

If you would rather see a list, the copy and the sending infrastructure built around your market before committing to any of it, see what a campaign would look like.

Operators, precedence order and Boolean operator limits are taken from LinkedIn's own help pages, fetched on 1 September 2026. On those two pages LinkedIn gives no operator limit for consumer search, and none is stated here.