Empty search states with query context
Review empty search results as a recoverable discovery state
Show the query and restrictions behind an empty result so the review focuses on a useful way back to discovery.
- ✓Old restrictions disappear from view
- ✓Clear actions erase too much
- ✓Waiting briefly looks empty
Review recovery instead of decorating the dead end
An explained empty state
Connect the absence of results to the visible query and active restrictions.
Recovery with retained context
Define which filter changes and which query stays when a customer chooses a recovery action.
Expected data supplied by the team
Use a seeded catalog to distinguish a presentation concern from a retrieval question.
Start with a reasonable query that finds nothing
A customer searches a sample catalog for a broad product category while an old availability filter remains active. The empty screen says Try another search without showing that restriction. Review whether the customer can understand why nothing is visible and choose a useful next action. An empty result is not necessarily a defect; the issue may be the missing explanation or recovery route.
Keep query and restrictions in the capture
Seed a small synthetic catalog and choose a query that has matches before applying the restrictive filter. Record the populated state, filter application, empty result, and recovery action. Note viewport, build, active facets, and the expected test inventory. Use supported browser capture or upload authorized media into Retick. Avoid real customer searches and catalog records that your team is not authorized to share.
Identify what the empty state conceals
An example issue is Empty results hide the active availability restriction. Annotate the empty-state message and the missing or obscured filter indicator. Review AI candidate findings, editing claims that the search engine is broken when the filter explains the result. Reject invented recommendations about inventory. Keep a copy suggestion distinct from a functional issue where Clear filters fails to change the visible state.
Example acceptance criteria
The empty screen should retain the submitted synthetic query and visibly identify the applied restriction. The approved clear-filter action should remove that restriction while preserving the query, then show the expected seeded results. If the product offers another recovery action, its label should describe what changes. Check those actions directly and confirm that the empty state appears only after the test result has settled.
Compare recovery, not just the illustration
Use a review cycle to compare the filtered empty state and its recovered result set after revision. Repeat with an unmatched query, all filters cleared, and a query that becomes empty after a second facet is added. Download reviewed findings or create Trello cards from a selected issue set on an individual media item. Retick does not inspect the catalog, determine whether a query should match, or repair retrieval logic. The application team supplies expected data and tests those behaviors separately from visual recovery guidance.
Give the empty result a meaningful next action
Capture a known query, apply a controlled restriction, and review the route back.