Two searches on the fictional music school Reed & Meter’s site show different outcomes. One query, “practice at home,” returns a list of practice notes. Another, a typo for “cello,” returns a blank area and no suggestion of what to try next. The visitor cannot tell whether the second search failed, whether the site has no cello content, or whether they should try a different word.
Reed & Meter is a teaching example, not a test result. The useful question is whether the visitor can understand the search outcome and choose a sensible next move.
Test site search on the live site. This guide makes no claim about typing into preview frames, and it does not ask you to paste a query address. Before you run searches that might have unusual effects, agree on a safe test path with the team first.
Use these questions as a way to think, not as a score:
- Is the searched term still clear on the results page?
- Is the outcome understandable, whether there are matches or none?
- Can the visitor choose a result, or a useful recovery route, without being blamed for the query?
When There Are Matches
A useful results page still shows what was asked, and it presents each match so a visitor can tell whether it is worth opening. If the query has disappeared, or if every result looks the same, the visitor has to reconstruct what they just did. On Reed & Meter’s “practice at home” search, titles and short excerpts that mention practice at home help a parent decide which note to open. A grid of identical cards with no query in view does not.
The placement of the search box itself, including whether it belongs in the header, is already covered in Should Site Search Be a Main Header Action?. This guide does not retell that decision.
When There Are No Matches
An empty state should make the query obvious, explain that nothing matched, and offer a way onward. That is the review standard this guide uses for the empty state. Nielsen Norman Group’s error-message guidelines (2023) give a no-results case as a bad example: the site “obfuscates the lack of results with puns instead of clearly conveying the situation.”
The way onward can be modest: a chance to edit the query, a few suggested topics, a link to a relevant section of the site, or a path to Contact. What matters is that the visitor is not left in a blank area, and that the page does not imply the failure is their fault.
This empty state is not the same as a product listing where selected filters return no items. That recovery pattern already lives in “Sort the Matches, and Make Empty Results Recoverable,” in Product Listing Page Best Practices. It is also not a missing page address. That error page belongs in How to Review a 404 or Dead-End Page.
WCAG 2.2 Status Messages, at Level AA, is a question for the team about whether a status message, such as a results count or a no-results notice, can be presented by assistive technology without the visitor moving focus to it. A visual review cannot settle that criterion.
Review on the Live Site
Run the search itself on the live site, along the agreed test path, and record the exact query you used. To see how the page that holds the search field is laid out, paste its address into Online Website Previewer and press Preview. Online Website Previewer previews one address at a time, and that address opens in all three frames: phone 390 by 844, tablet 820 by 1180, and desktop 1920 by 1080 CSS pixels. The previewer is a visual check of layout in your current browser, not a test of a particular device. This guide does not use it to run or check a search.
A wider pre-launch pass can include this check. See How to Test Your Website Before Launch: A Checklist.
Send a Keep or Rework Note
A useful note might say: “On the live site, starting from [search page address], in [view and size checked], a typo search for [exact query] returned a blank results area, with no restatement of the query and no suggestion of what to try next. A search for ‘practice at home’ did show matching notes, but the query was no longer visible. Please keep the searched term on the page in both cases, explain when nothing matches, and offer a way onward that does not blame the visitor.”
For how to phrase the note, see How to Give Useful Feedback on a Website Design.



