Source: Production search UX methodology; UX writing literature; Volume 6 zero-result investigation patterns
Classification — Patterns for handling the various forms of search failure — partial matches, zero results with suggestions, zero results without suggestions — in user-facing ways.
Convert search failure modes into useful user interactions by acknowledging the failure clearly, offering alternative paths forward, and preserving user agency.
The worst UX failure in production search is the bare "No results" page with no alternatives, no suggestions, no path forward — the user is stuck. This pattern still appears commonly in production search. Even minimal alternatives substantially improve the empty-state experience; substantial alternatives transform it from a dead-end into a redirection opportunity.
State 1: partial match. The system found some results but they're weak (low scores, spell correction inferred but uncertain). UX response: show the partial results with a banner explaining the situation ("Showing partial matches for X"); offer the inferred query as a one-click switch; preserve the original query as a fallback ("search instead for..."). The pattern communicates uncertainty honestly while preserving user control.
State 2: zero results, suggestions possible. The system has nothing for the query but has a confident alternative (typically from spell correction or query expansion). UX response: an empty-results page with the failed query prominently displayed; a clear suggestion as the primary affordance ("Did you mean X?" as a large clickable element); the original query preserved (the user might want to try a different reformulation or contact support). Production patterns avoid auto-applying corrections in zero-result cases because the auto-apply would hide the failure from the user.
State 3: zero results, no clear suggestion. The system has nothing and no good alternative — a genuine content gap or vocabulary gap. UX response: clear acknowledgment of the gap; suggested alternative paths (browse categories, popular content); contact or request affordances where relevant; a description of what kinds of things the search does cover, so the user understands the scope. The state should feel like helpful redirection, not failure.
Content for empty states. The text matters substantially. Bad patterns: "No results found." (cold, blocking, no path forward). Good patterns: "We couldn't find products matching 'X'. Try browsing our running shoe categories below, or check your spelling." (warm, redirecting, offers paths forward). UX writing guidance: acknowledge the failure clearly without blaming the user; describe what was tried; offer alternatives; maintain brand voice. Production teams often have UX writers contribute to empty-state copy because the content has substantial impact on perceived quality.
Filter dead-ends. A specific failure case: the user applied filters that collectively eliminate all results. UX response: explicitly call out the filter combination as the cause; suggest removing specific filters ("Remove 'size 14' to see 47 more results"); offer a "clear all filters" affordance. The pattern educates the user about which filter is most restrictive; without it, the user has to manually try removing each filter to find the path forward.
Suggestions in empty states. Empty states are the right place for assertive suggestions. Patterns: top related searches (queries similar to the failed one that did produce results); popular searches in this section/category; recently viewed items (for logged-in users — something the user has shown interest in); featured or curated content (when the team wants to direct attention). The suggestions should be tailored to context: a zero-result query in the shoe department should suggest shoe alternatives, not generic store-wide popular items.
Logging and operational integration. Empty states are operationally important — Volume 6 Section B documented the investigation cycle. The UX should support the operational discipline by capturing what the user does next: did they click a suggestion? Did they reformulate? Did they leave? Did they contact support? Each behavior is a signal about whether the empty-state UX worked. Production patterns: log empty-state events with the failed query; track subsequent user actions; correlate with whether the user eventually found what they wanted (or didn't).
Mobile considerations. On mobile, empty states need to be especially well-designed because the user has fewer fallback paths (no easy sidebar for filters, fewer affordances visible at once). The empty state should fit on one screen without scrolling; the primary suggestion should be obvious and large; the path back should be one tap. The discipline is harder on mobile but more important — users abandon mobile search more readily than desktop, and good empty-state UX retains them.
Every search system. The patterns are foundational; even simple search benefits from non-trivial empty-state handling. The investment is modest (mostly content design plus modest implementation work); the returns are substantial because the failure cases compound badly without it.
Alternatives — none for serious search UX. Some systems show "contact support" as the only path in empty states; this works for very limited contexts but underuses the available alternatives. Some show generic browse links; this is better than nothing but suboptimal. The contextual, redirective pattern documented here is the production default.
- Production search UX methodology writings
- Volume 6 of this series for the operational investigation patterns
- UX writing literature (Microsoft Style Guide, Mailchimp Voice and Tone, etc.)