“No results” may be accurate, but it leaves the visitor with all the work. A useful empty state shows what was searched and offers a sensible next action.
Keep the failed query visible
Preserve the text in the search field so it can be edited. If filters were applied, display them clearly and make removal straightforward. A visitor searching for a blue item in an unavailable size should not have to guess that the filter, rather than the product name, eliminated every match.
Offer suggestions suited to the content: a shorter phrase, an alternative term or a relevant category. Do not claim that an unrelated popular product is a search match. Separate recommendations from actual results.
Test three recoveries
- A misspelt common term.
- A valid term combined with an overly narrow filter.
- A reasonable request for something the site genuinely does not offer.
For each, ask someone unfamiliar with the design what they would do next. Watch whether they can edit the query, remove a filter or find a relevant support route without restarting from the homepage.
Check keyboard use and screen-reader announcements as part of the actual implementation. A visible message that appears without an appropriate accessible update may not reach every user. Use established accessibility guidance for the technology involved.
Review unsuccessful queries with privacy in mind. People sometimes paste personal information into search boxes, so avoid collecting or exposing more than needed. Patterns can reveal vocabulary gaps or missing content, but one failed query does not automatically justify a new page.
The empty state succeeds when it helps someone make the next informed choice. Sometimes that choice is another search; sometimes it is learning promptly that the site does not have what they need.