Submitted query reflected in visible heading or result-count label
Why it matters
When a user submits Italian restaurants and the results page renders without echoing that query anywhere on-screen, the user has no confirmation that their search was understood. They cannot tell whether the page is filtered, whether typos were preserved, or whether they landed on the wrong route. This is a fundamental user-experience failure: the results page must close the feedback loop by reflecting the exact string the user typed, otherwise trust in the search breaks down and the user re-enters the query or bounces.
Severity rationale
High because users lose orientation and re-query repeatedly, inflating bounce rates and server load without compromising security or data integrity.
Remediation
Read the query from the URL search params and render it in the page heading with the result count. Edit app/listings/results/page.tsx:
const query = searchParams.get('q') ?? ''
return (
<>
<h1>Results for "{decodeURIComponent(query)}"</h1>
<p>{count} listings found</p>
</>
)
Decode the parameter so characters like %20 render as spaces.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Search & Discovery UX Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from directory-search-discovery·automated