Handling a no-results page usually involves two separate parts: how search behaves when a query returns no hits, and how your UI responds when that happens.
On the search side, you can reduce empty-result searches by adjusting your no-results behavior. For example, removeWordsIfNoResults lets Algolia broaden a query automatically when no matches are found. Depending on your use case, you can also use Rules to guide users toward other relevant content or promotions.
On the UI side, displaying a no-results message or fallback state must be implemented in your frontend. If you’re using InstantSearch, you can customize the empty state shown when a search returns no hits and provide actions such as clearing filters or refining the query.
For general guidance on improving no-results behavior, see the guide on query expansion and no-results strategies. For frontend implementation, see the InstantSearch guide for conditional display and empty states.