This is No Results Page: Give Searchers a Way Forward as plain markdown, the version AI agents read. Same facts as the page, without the layout.
--- title: "No Results Page: Give Searchers a Way Forward · Rubric" description: Never show a bare “no results” page. Keep the query in the box, fix likely typos and say so, and offer another path to what they wanted. url: https://rubric.design/ux/search.zero-results-recovery format: agent view of this page updated: 2026-11-16 --- [UX guides](https://rubric.design/ux/) / [Site search](https://rubric.design/ux/topic/search) / Zero-result and low-confidence searches offer a way forward # Zero-result and low-confidence searches offer a way forward Usually high · How serious this usually is when it goes wrong. Not a score. ## The guideline Never show a bare "no results" page. State the query that was run, and keep it in the search box so it can be edited rather than retyped. Where a spelling correction is likely, apply it automatically and say so plainly ("Showing results for Samsung TV instead of Samsng TV"), while still letting the user search for what they actually typed if they want to. When no correction applies, offer related or broader searches, and list popular or trending items or categories as a fallback so the page is never empty. If the emptiness was caused by an overly narrow filter combination rather than the query itself, offer to relax the most restrictive filter and show what that would return. **What goes wrong:** A search page showing only “No results found.” **What good looks like:** A search page that corrects the typo and shows matching products. ## Common failures - When shoppers land on a "No Results" page, they encounter a dead end with no alternative paths, spelling suggestions, or recommended products to keep them engaged. This forces users to abandon their search or navigate away entirely. ## Where it applies ### Pages - Search ### Disciplines - Conversion - Content ### Devices - Desktop web - Mobile web - Mobile app ## Why it matters, how to fix it, and the research behind it Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first. [Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents) ## Related guides - [Every item in the list carries its price, and its unit price where packs differ](https://rubric.design/ux/product_listing.price-and-unit-price-on-every-item) · Usually high · Show a price on every item in the list, including items that are out of stock, on pre-order or configurable — where a single figure is impossible, show the… - [Autocomplete suggests as the user types, fast, clean and keyboard-operable](https://rubric.design/ux/search.autocomplete-suggestions) · Usually high · Show suggestions after two or three typed characters, with no visible lag or flicker as the user keeps typing. - [Long result lists use pagination or Load More, not silent infinite scroll](https://rubric.design/ux/product_listing.pagination-not-infinite-scroll) · Usually medium · Avoid pure infinite scroll — content injected automatically as the user nears the bottom, with no explicit action to request it — for any list a user needs to… - [Cancellation terms are stated before payment, not after](https://rubric.design/ux/auth.cancellation-policy-disclosed-before-payment) · Usually critical · State the cancellation policy — how to cancel, whether it can be done anytime, and what happens to access after cancelling — on the plan selection or payment… - [Optional add-ons offered and removable at the cart](https://rubric.design/ux/cart.optional-add-ons) · Usually critical · Offer optional extras — fast-track entry, parking, insurance, meal or seat upgrades — on the cart.