Fixing AjaxSearch When One-Letter Words Stop Returning Results

Short words are always awkward for search. In this old AjaxSearch case, the site needed to find phrases containing very short words, but the search behavior broke after configuration changes around minimum search length.

The Usual Cause

AjaxSearch often filters out very short tokens by design. That helps performance and avoids noisy results, but it can also remove meaningful one-letter or two-letter terms in real content.

What to Review

• the minChars setting
• how the query is tokenized before matching
• whether stop-word behavior is too aggressive for the project language
• whether short terms should be supported at all in the current search UX

A Practical Rule

Lowering minChars may be necessary, but it is not free. Shorter terms increase noise and load. On a large site, that can make search slower and less relevant unless the searchable fields are already well constrained.

The right fix is usually a balance: keep the query scope tight, then reduce the minimum token length only as far as the real use case requires.