UI Coach guide
Search UX Best Practices
Search UX for query input, results, no-results, and the moment someone is looking for a thing they can almost name.
By UI Coach Editorial ·
Search is a promise that the catalog is reachable by language. The interface has to accept messy queries, show what was understood, and recover when nothing matches. A magnifying glass in the header is not a search system.
Make the scope obvious
Are we searching the whole product, this project, or help docs? If scope can change, show it. People will assume global search if you do not tell them otherwise.
Support the query
Autcomplete should complete likely intents, not just recent strings. Spelling help, synonyms, and filters after the query all reduce dead ends. Keep the original query visible so people can edit it.
Results need structure
Lead with the best match, show why it matched when useful, and keep metadata scannable: type, owner, date. Infinite scroll can work for media. Tools often need pagination or a count because people compare items.
Zero results is a flow
Suggest broader queries, removed filters, or popular destinations. Do not show a blank list. Do not pretend there are results with unrelated items.
How to judge the work
Search is ready when the scope is visible, the original query can be edited, the best match is first, and zero results still offer a way out. If people have to guess whether they searched the whole product or only this folder, the control is lying about its reach.
Practice this on UI Coach
Challenges that include catalogs, inboxes, or resource libraries are good search rehearsals. Design the no-results state first. It exposes whether the feature has a real recovery path.
Sources
- Nielsen Norman Group on search UX