LinkedIn Boolean search builder that writes the string from three plain lists and checks it against every rule LinkedIn publishes.

How to use the LinkedIn Boolean search builder

The LinkedIn Boolean search builder above is a free generator tool that turns three plain lists of job titles and keywords into a Boolean string you can paste into LinkedIn search or Sales Navigator, then checks the string against the rules LinkedIn publishes.

You can also paste a string you already use and let the checker test it.

1. Pick where you will search

   Choose LinkedIn search, Sales Navigator or Recruiter. The operator limit and the notes change with it.

2. Fill in the lists

   Put job titles in Any of these, required words in All of these, and words to exclude in None of these.

3. Read the string and the checks

   The string updates as you type. The checker lists anything LinkedIn's rules say will not work.

4. Fix and copy

   Use Fix quotes and operators for the two most common problems, then copy the string.

5. Paste it and read the first page of results

   Run the search and open a few profiles. If the results are wrong, adjust the lists, not the filters.

How the three lists become a Boolean string

Each list maps to one Boolean operator. Terms that contain a space are put in straight quotation marks, so LinkedIn treats them as exact phrases rather than separate words.

The parentheses around the OR list matter. Without them, LinkedIn's order of precedence would attach the AND to the last title only, as the next sections explain.

What the checker tests, and where each rule comes from

Every check is a rule from LinkedIn Help or Sales Navigator Help, read on Oct 1, 2026. The checker does not run your search, and it does not guess at rules LinkedIn has not published.

Where to paste a Boolean string on LinkedIn

LinkedIn says it limits operators in its free search to keep it fast and to deter profile scraping. Keep strings for the free search short, and move long ones to Sales Navigator. Our LinkedIn Sales Navigator guide covers the rest of that product.

Why parentheses change your results

LinkedIn evaluates a Boolean string in a fixed order: quoted phrases first, then parentheses, then NOT, then AND, and OR last. A string that mixes AND and OR without parentheses therefore means something other than it seems to.

The checker flags AND and OR at the same level so you can decide. Our Boolean search on LinkedIn guide explains the order of precedence in full.

Smart quotes and strings copied from documents

Strings kept in a document or a spreadsheet often come back with curly quotation marks, because word processors replace straight quotes as you type. Sales Navigator Help says it supports only straight quotation marks and does not recognize curly ones.

Paste the saved string into the checker and click Fix quotes and operators. It turns curly quotes straight and capitalizes and, or and not when they stand outside quotes. Keep the fixed version as your saved copy, so the problem does not come back.

Title field or keyword field in Sales Navigator

Sales Navigator Help says Boolean works in the Keyword, Title and Company fields. For a seller, the title field is usually the better home for the Any of these list: a keyword can match words used anywhere on a profile, while the title field is about the role a person holds.

Use the keyword field for the All of these and None of these lists when they describe a market or a skill rather than a title.

In account searches, the Company field takes the same kind of string, for example a list of competitors to exclude. Our Sales Navigator search filters guide covers how filters and Boolean strings work together.

Boolean search or plain language search

LinkedIn's people search also understands conversational queries, such as finance leaders at nonprofits in Boston. LinkedIn Help adds that natural language search does not support quotes, and that for exact keyword matching you should use Boolean search instead.

The rule of thumb follows from that. Plain language for a quick look, Boolean for a list you will reuse, save and share with a team, where every term needs to mean exactly what it says.

Boolean strings for sellers, written for this page

These strings were written for this page. Load the first two from the example buttons in the builder, then change the titles to the ones your buyers actually use.

From a Boolean string to a prospect list

A good string is the start of a list, not the list itself. Run it, read the first twenty profiles, and adjust the lists until most of them are people you would actually write to.

Then save the search, so the same string keeps working as people change jobs. When the list is right, our guide to exporting a list from Sales Navigator covers moving it into your CRM.

Our LinkedIn prospecting guide covers what to do with the list, including LinkedIn outreach to the people on it, and our guide on how to find alumni on LinkedIn shows one way to add a warm path to it.

What the builder will not do

• Run the search. It builds and checks the string; LinkedIn runs it.
• Promise a result count. LinkedIn Help says search result counts are approximate.
• Get around limits. It warns at 15 operators for Sales Navigator and cannot lift LinkedIn's limits.
• Write search engine strings. Google X-ray searches follow different rules and are not covered.
• Store anything. The lists and the string stay in this tab.

Common LinkedIn Boolean search mistakes

• Typing and, or and not in lowercase.
• Pasting a saved string with curly quotation marks.
• Mixing AND and OR without parentheses.
• Using an asterisk as a wildcard, which LinkedIn does not support.
• Writing more than 15 operators for Sales Navigator.
• Putting a phrase with by, in or with in quotes and expecting those words to count.
• Excluding so many terms that real buyers disappear from the results.

A Boolean string skeleton you can adapt

The skeleton below was written for this page. Replace the placeholders with titles, a market word and the roles you never want to see, then paste it into the builder to check it before you run it.

("{{firstTitle}}" OR "{{secondTitle}}" OR {{oneWordTitle}}) AND {{marketWord}} NOT ({{excludedRole}} OR {{secondExcludedRole}})

Frequently asked questions