Why Basic Patent Search Syntax Details Matter
A patent search can include the right concepts, classifications, and technical terminology and still produce incomplete or unnecessarily noisy results.
The problem is often not the search strategy itself, but the way the database interprets the query.
Patent databases do not always treat spaces, punctuation, proximity operators, wildcards, and classification codes in the same way. A search string transferred from another platform may therefore behave differently from what the searcher intended.
In PatSeer, for example, words separated by a space are treated as an exact match by default. Searching:
TA:(guide rna)
looks for the phrase “guide rna.” To find records where both terms appear independently within the title or abstract, the query must use an explicit Boolean operator:
TA:(guide AND rna)
Other native syntax features can also make queries cleaner and more precise.
The underscore operator helps account for inconsistent drafting. A search for:
zinc_finger
can retrieve “zinc finger,” “zinc-finger,” and “zincfinger” without requiring a long OR statement.
CAPS Search is useful when an acronym is also a common word. Searching:
C:'LED'
retrieves uppercase “LED” while excluding lowercase uses such as “the process led to an improvement.”
Classification searching can also be simplified. Adding $ to the end of a complete classification code expands the search across all dependent subgroups:
CPC:C12N15/00$
For proximity searching, structural operators such as ws and wp allow terms to be restricted to the same sentence or paragraph. Adding a number, such as wp30, can further require the terms to appear within 30 words of each other.
These details may appear minor, but they can significantly affect which patent records are included or excluded from a result set.
The complete guide explains PatSeer’s exact-match behaviour, punctuation rules, classification expansion, proximity combinations, query modifiers, and wildcard differences across major patent databases.
Read the full article: How to Improve Patent Search Queries with Finer Syntax Details

Comments
Post a Comment