Boolean Search Checker & Converter

Paste any boolean string. Get every syntax error that silently breaks a search, a plain-English reading of how it groups, and the same query rewritten for eight platforms with their documented limits checked. No sign-up.

Try an example
Corrected string for LinkedIn Recruiter
("software engineer" OR "backend engineer" AND python NOT recruiter)
ErrorsThings that break the search
1
WarningsLikely to return the wrong people
2
Search terms
4
Boolean operatorsSome platforms cap this
3
CharactersFor LinkedIn Recruiter
68
What was fixed, and why it mattered
Curly quotes replaced with straight quotes (4). Word and Google Docs insert them; search engines do not treat them as quotes.warning

A curly quote is an ordinary character to a search engine, so the phrase is not treated as a phrase and the search silently widens.

Missing closing bracket added at the end (1).error

Unbalanced brackets change how the groups combine, so the query runs but matches a different set of people than you intended.

AND and OR are mixed at the same level without brackets. Platforms read that left to right, which is rarely what you mean: put each OR list inside its own brackets.warning

Without brackets, platforms read left to right, so developer OR engineer AND python can return every developer regardless of Python.

How your query actually reads

Brackets decide who you get back. This is the grouping the platform will apply, in plain English.

AND and OR mixed without brackets, so this reads left to right

  └ the exact phrase "software engineer"

  └ the exact phrase "backend engineer"

  └ python

  └ but not: recruiter

The same search on every platform
LinkedIn Recruiter4 terms

AND, OR and NOT must be in capitals. LinkedIn states it does not support the * wildcard, and that the + and - operators are not officially supported, so exclusions are written as NOT. LinkedIn states positively that Recruiter and Recruiter Lite have no operator limit.

("software engineer" OR "backend engineer" AND python NOT recruiter)

Wildcard: documented as not supported

LinkedIn Recruiter documentation
LinkedIn Sales Navigator4 terms

Same syntax as Recruiter, but Sales Navigator documents a maximum of about 15 boolean operators in one query. It also warns that curly quotation marks are not supported, only straight ones.

("software engineer" OR "backend engineer" AND python NOT recruiter)

Wildcard: documented as not supported. Operator limit: 15

LinkedIn Sales Navigator documentation
Google X-ray4 terms

A space already means AND, so the keyword is dropped. OR must be capitalised. Exclusions use a leading minus with no space after it. Google documents no length limit on its own search box.

("software engineer" OR "backend engineer" python -recruiter)

Wildcard: not documented

Google X-ray documentation
Bing4 terms

Bing documents AND, OR, NOT and parentheses, and requires NOT and OR in capitals. It processes only the first 10 terms of a query, so long strings are silently truncated.

("software engineer" OR "backend engineer" AND python NOT recruiter)

Wildcard: not documented. Processes the first 10 terms only

Bing documentation
Indeed4 terms

Indeed documents AND, OR and quotes, and documents exclusion only as a leading minus, with no NOT keyword and no wildcard. Multi-word terms should be quoted.

("software engineer" OR "backend engineer" AND python -recruiter)

Wildcard: not documented

Indeed documentation
Greenhouse4 terms

Greenhouse documents AND, OR, NOT, quotes, parentheses and the * wildcard, so Java* matches Java and JavaScript. Full Text Search must be switched on. Smart quotes pasted from a document break the query.

("software engineer" OR "backend engineer" AND python NOT recruiter)

Wildcard: documented as supported

Greenhouse documentation
Workable4 terms

In Workable's boolean mode AND is the default between terms and NOT is written as a prefix. Fuzzy matching is on by default, so results include near-spellings. Its basic search box behaves as OR instead, which changes the same string's meaning entirely.

("software engineer" OR "backend engineer" AND python NOT recruiter)

Wildcard: documented as supported

Workable documentation
Ashby4 terms

Ashby documents that the word NOT does not work and that exclusion is written as ! or -. Operators do not need capitals, square brackets group as well as parentheses, and * is documented as a leading modifier only, so *script matches javascript and typescript.

("software engineer" OR "backend engineer" AND python !recruiter)

Wildcard: documented as supported

Ashby documentation

What the checker fixes

Most boolean searches that return nothing, or the wrong people, fail on syntax rather than logic. Paste your string and the checker repairs the usual suspects and lists every change it made:

  • Brackets: a missing or extra ), and empty () groups.
  • Quotes: an unclosed phrase, and curly quotes (“ ”) pasted from Word or Google Docs that search engines do not read as quotes.
  • Operators: lowercase and / or / not, a string that starts or ends with an operator, doubled operators like AND OR, and commas used as separators.
  • Ambiguity: AND and OR mixed at the same level without brackets, which platforms read left to right.

LinkedIn, Google and Indeed do not speak the same boolean

  • LinkedIn Recruiter wants AND, OR and NOT in capitals, supports brackets and quotes, and does not support the * wildcard.
  • Google X-ray treats a space as AND, only understands OR in capitals, and excludes with a leading dash: -recruiter instead of NOT recruiter.
  • Indeed documents AND, OR and quotes, but documents exclusion only as a leading minus. It documents no NOT keyword and no * wildcard.

Pick the platform under Format for and copy the rewritten string. Build a new string from scratch with the Boolean Search String Builder, widen it with the Synonym Expander, or point it at public profiles with the X-ray Search Builder.

From a string to real candidates

A corrected string still only searches the platform you paste it into, one at a time, with no contact details attached. HeroHunt runs the same query against a live candidate index across LinkedIn, GitHub and the open web, screens every match against your role, and reveals verified emails and phone numbers.

Frequently asked questions

The things that make a search return nothing or the wrong people: missing or extra brackets, an unclosed quote, empty brackets, a string that starts or ends with an operator, doubled operators like AND OR, curly quotes pasted from Word or Google Docs, lowercase and / or / not, and commas used as separators. Every fix is listed so you can see exactly what changed.

The operators genuinely differ, and each vendor documents its own. LinkedIn requires capitals and states it does not support the asterisk wildcard, and that the plus and minus operators are not officially supported. Google documents the minus for exclusion but documents neither OR nor parentheses. Bing documents all of them plus its precedence order, but processes only the first 10 terms. Indeed documents AND, OR and quotes, but documents exclusion only as a leading minus, with no NOT keyword and no wildcard. Ashby documents that the word NOT does not work and that exclusion is an exclamation mark or a minus. Greenhouse and Workable both support the wildcard, and Workable applies fuzzy matching by default. The converter rewrites your query for whichever you pick and links its documentation.

It is free and needs no sign-up. Everything runs in your browser; the string never leaves your device and nothing is stored.

developer OR engineer AND python is ambiguous: platforms read it left to right, so it may match any engineer with Python, or any developer at all. Put each OR list in its own brackets: (developer OR engineer) AND python. The checker flags this, and shows you a plain-English reading of how the brackets actually group.

The checker tells you when it does. Bing documents that only the first 10 terms of a query are used, so a long string is truncated without warning. Sales Navigator documents a maximum of 15 boolean operators. LinkedIn states positively that Recruiter and Recruiter Lite have no operator limit, while free consumer search is capped at an unpublished number. None of the platforms documents a character limit on the search box, despite what is widely repeated.

LinkedIn documents a 16-word stop-word list for its Keywords filter: and, or, the, of, at, by, to, for, with, in, they, have, from, not, but and after. A phrase like head of engineering leans on a word LinkedIn may drop, so the checker flags any phrase containing one. LinkedIn does not state whether the list applies inside quoted phrases, so treat it as a warning rather than a certainty.

A boolean string only searches the platform you paste it into. Sign in to HeroHunt to run the corrected query against a live candidate index across LinkedIn, GitHub and the open web, screen the results against your role, and reveal contact details in one place.