A buyer searches for a specific connector. The site returns a cheerful grid of popular products. None matches the connector number.
The page contains results. The buyer still has no answer.
A useful empty state preserves the request, states what the system knows, and offers a next step that respects the original requirement. It distinguishes a completed search with zero matches from a search that never completed.
Use the following specification to review those states before building or changing search. The copy, identifiers, tasks, and tables are fictional. Use them to specify the message, action, and preserved constraints for each state.
Identify the state before writing the message
Begin with the search response. A successful request with zero matches supports an empty-results message. A failed request supports an error message. A missing response supports neither a result count nor a claim about the catalog.
Within a completed search, keep several explanations open. The requested content may be absent. Active filters may exclude it. The submitted term may differ from the indexed language. A misspelling or exact identifier may require separate treatment.
Do not diagnose from an empty array alone. Specify which evidence the interface receives and which explanation remains unknown. If the application cannot distinguish a failed request from zero matches, that is an implementation requirement for the search owner.
Algolia separates engine behavior from frontend presentation in its no-results guidance. Broadening a query and displaying a helpful empty state are separate responsibilities. A search setting does not supply the words or actions the buyer sees.
Preserve the query and name the constraints
Keep the submitted text visible and editable. Show the active constraints near the message. A reader should not have to reconstruct which product family, region, language, or document version the search currently covers.
Name the scope accurately. “No matching manuals for this query and version” is narrower than “This product does not exist.” The latter needs evidence beyond the search response.
Keep removable filters distinct from required boundaries. A document-version filter may be adjustable. An access boundary must remain enforced. The proposed recovery action must not offer restricted material merely to populate the page.
For an editable filter, say what the action changes. “Remove the PDF filter” is reviewable. “Show more” leaves the buyer guessing. Preserve the query when changing a filter unless the buyer explicitly edits it.
Record the expected behavior for returning from a destination. The buyer should be able to resume the same query and constraints. Treat that as a usability acceptance condition, then test it in the implementation.
Use a decision table with visible recovery rules
This table is a proposed specification. It does not describe default behavior across search products. Every recovery path requires verified content or application evidence.
| Observed state | Message should establish | Useful next action | Guardrail |
|---|---|---|---|
| Completed search, zero matches, no optional filters | Nothing matched the submitted request in this scope | Edit query or browse a verified relevant category | Do not claim the item does not exist |
| Completed search, zero matches, optional filters active | Which constraints narrowed the search | Remove one named filter | Keep the original query visible |
| Possible misspelling with a verified candidate | A different spelling is available to try | Search the suggested term explicitly | Preserve access to the original term |
| Exact identifier returns zero matches | The exact code was not found | Check the code or contact the appropriate support path | Do not silently substitute a similar code |
| Search request fails | Results could not be retrieved | Retry or use a maintained alternative route | Do not label the state zero matches |
| Broadened query returns alternatives | Results come from a changed query | Review the stated change or restore the original query | Do not present alternatives as exact matches |
Choose one primary recovery action for the current state. Add a secondary route only when it serves a different need. A page full of unrelated choices shifts the diagnosis back to the reader.
Make filter removal deliberate
Consider a fictional documentation search for “installation guide,” limited to version four and PDF files. A completed request returns zero matches.
The page can show: “No PDF manuals match ‘installation guide’ for version four.” A proposed action reads: “Search all formats for version four.” The action removes the format filter while preserving the version.
A guide for version five cannot stand in for version four merely because it fills the screen. If another version is offered, label it separately and explain that the original version constraint does not apply.
Algolia documents a dedicated analytics view for searches without results. Its support article also describes filter information for those searches. That evidence can help an authorized owner inspect a reported empty state. It does not prove that removing a filter is appropriate for the reader's task.
Keep this review focused on recovery behavior. Decide content-gap priorities in a separate analysis. The empty-state specification needs to answer what the buyer can do now.
Verify spelling and synonyms against the catalog
A suggested term must have a defensible relationship to the submitted phrase. Use maintained product language, documentation titles, or an approved terminology list to verify it.
For a fictional general query, “instalation guide,” the interface might offer “Search for installation guide.” The candidate is visible, the action is explicit, and the original query remains available.
A synonym needs the same discipline. Two terms can overlap without describing the same product or task. Do not treat “connector” and “adapter” as interchangeable across every category because they appear near each other in copy.
Algolia's empty-results documentation discusses synonyms and typo tolerance. It recommends preserving precision for attributes such as product codes through attribute-specific typo settings. Those are Algolia capabilities. The proposed editorial rule here is broader: verify equivalence before recommending a replacement.
For content architecture, the headless CMS guide provides adjacent context on structured content. The recovery specification should identify who maintains approved labels and how the frontend receives them.
Treat exact identifiers as protected input
A fictional buyer enters AX-410B. The catalog has an entry for AX-4108. Their visual similarity does not establish compatibility.
The empty-state copy can say: “No exact match for AX-410B. Check the characters on your product label.” A secondary path can offer product-identification help if that service exists and its destination is maintained.
If the interface displays nearby codes, label them as different identifiers. Do not place them under an exact-match heading. Do not preselect a substitute or imply that a shared prefix proves fit.
Apply the same review to version numbers, dimensions, and other meaningful constraints. In this proposed specification, a required attribute remains required until the buyer deliberately changes it.
The recovery screen should carry uncertainty forward. A support path can help resolve an identifier. A result card alone cannot certify that two products serve the same purpose.
Make optional query relaxation explicit
Algolia documents removeWordsIfNoResults for broadening multiword queries that return no matches. Its parameter reference lists none as the default: no words are removed. The firstWords and lastWords options remove words from the beginning or end, respectively. They stop when results appear or five words have been removed. The allOptional option lets results match any subset of the query words. These settings belong to Algolia; they are not universal search behavior.
That behavior changes the matching request. Whether it is suitable depends on the words removed and the task. Treat it as an optional design decision, not an automatic definition of successful search.
For a fictional query, “compact pump maintenance overview,” an approved recovery might try “pump maintenance overview.” The interface should name the omitted word and identify the resulting items as broader matches.
For “AX-410B outdoor connector,” this specification prohibits silently dropping the identifier or the outdoor requirement. Finding a different connector would not answer the original request. Keep the exact request available even when a separate alternatives section appears.
Require the owner to document the relaxation rule, protected fields, visible explanation, and reversal action. Test those four elements together. Enabling a setting alone does not establish that the interface tells the truth about its results.
Offer relevant destinations without inventing an answer
A category link is useful when its scope relates to the query. A generic “browse everything” link may be a fallback, but it should not masquerade as a matching result.
For documentation searches, a maintained manual index can provide a second route. For product-identification questions, an appropriate contact path may help. Verify the destination and its purpose before putting either into the empty state.
Describe categories by the work they support. “Browse installation manuals” tells the reader more than “Resources.” Use the content hub architecture guide when defining those destinations and their relationships.
Keep contact optional when a self-service route exists. Do not require a lead form to retry a search. If contact is the only supported next step, say what the team can help investigate without promising an answer or response time.
Use the B2B conversion optimization guide for broader page review. Here, judge the action against the failed task rather than a desire to collect an inquiry.
Review the fictional copy as complete states
The following blocks are copy examples for review, not live controls. Each action label would stand alone in the eventual interface.
Unfiltered empty result: “No matches for ‘renewal checklist’ in this resource library. Try another term or browse account-management guides.” Proposed action: “Edit search.” Use that category only if the site maintains a relevant guide collection.
Filtered empty result: “No PDF manuals match ‘installation guide’ for version four. You can search other formats while keeping version four selected.” Proposed action: “Search all formats for version four.”
Failed request: “Search is unavailable right now. Your query is still here. Try again or open the manual index.” Proposed action: “Retry search.” Do not attach a zero-results counter to this state.
Broadened results: “No matches for the full query. These results use ‘pump maintenance overview’ without ‘compact’.” Proposed action: “Restore original query.” Keep the original wording visible above the alternatives.
Have the content and search owners read each state together. They should agree on the evidence behind every sentence. Remove any promise the application cannot support.
Test the recovery against the original task
Use a small set of synthetic tasks before release: an absent topic, a restrictive filter, a misspelling, an exact identifier, and a failed request. Add a broader-match case only if relaxation is part of the approved design.
For each task, record the submitted query, constraints, returned state, visible explanation, chosen action, and destination. Ask a reviewer to explain what changed after the action. An incorrect explanation exposes a copy or interaction problem.
Check keyboard access, visible focus, narrow-screen layout, and how state changes are conveyed with assistive technology. Keep those checks as acceptance tasks for the implementation team. Passing this worksheet does not establish complete accessibility conformance.
Finally, confirm that failure remains distinguishable from absence. Retry should retry. Filter removal should name the removed filter. Alternatives should remain alternatives.
Preserve the buyer's request. Make the next step honest.
Sources
- Algolia: empty or insufficient results, covering vocabulary, precision, and query broadening.
- Algolia: handling no-results pages, distinguishing engine behavior from frontend empty states.
- Algolia: searches without results, including filter evidence in analytics.
- Algolia: removeWordsIfNoResults reference, for the optional query-relaxation setting.