Search-Empty

Search-empty is the screen that appears when a user runs a query and gets zero matches. It carries real user intent in the form of the exact search term, giving you context no other empty state provides. Unlike first-run empty that teaches total beginners or post-clear empty that celebrates inbox zero, this state arrives mid-task with the user's own words as fuel. The best versions echo the query so the user feels heard, offer a one-click create action that uses the term as title or prompt, surface two or three related suggestions pulled from real data, and keep the tone direct instead of apologetic. The parent article calls it the most rescuable empty state because you already know what the user wanted. Ignore that signal and users bounce. Respect it and you turn absence into new content that makes the product smarter for everyone. The four design moves map cleanly here. Suggested actions become the hero. Teaching illustration shows a quick preview of the item you will create. Tone-setting copy stays short, on-brand, and useful. Sample data appears as partial matches or templates based on the keywords.

Search-empty is not a dead end. It is not the centered sad illustration with the copy no results found and a vague try different keywords link that designers still ship in 2024. It is not your generic zero-state template borrowed from a fresh project or the infinite blank prompt that AI products overuse. It is not the place for snarky one-liners that mock the missing content or for forcing the user through the entire onboarding flow again. It is not an error state in disguise and it is not a shrug. Teams that treat every empty the same waste the richest intent signal their product ever receives from a user.

Concrete examples show the difference between mediocre and sharp. Linear shipped their version in March 2023. Search for frontend payment bug and the screen repeats the exact phrase at the top, followed by a large Create issue frontend payment bug button that prefills the form with suggested labels, assignee, and even a template based on keyword detection. Below sit three related chips: payment integration test, stripe webhook failure, checkout flow regression. The copy reads No matches but we can make this instead in Linear's signature dry tone. Notion did this during their October 2022 workspace overhaul. A search for quarterly planning docs with zero hits shows three template cards with realistic sample data already rendered inside miniature previews. Click any card and you land in a fully seeded page with the title prefilled. GitHub refined theirs across 2018-2020. No results in a repo issue search for dark mode toggle offers Open new issue titled dark mode toggle with the first comment pre-populated with links to similar discussions from other repos. Figma added theirs to community search in early 2024. Zero matching UI kits triggers Publish new file request with your exact terms as the default title plus three fuzzy-matched existing files below it. Dropbox evolved theirs between their 2016 bare-bones version and the 2022 update that now suggests Create folder named after your query and surfaces related files from teammates. Superhuman used a version in their 2021 beta where email search-empty suggested creating a new saved search rule or shortcut that would catch similar messages in the future. In AI land Perplexity turns empty search results into generate anyway with adjusted parameters while Cursor suggests refined prompts that contain the original keywords. These are not decoration. Each one collapses the gap between not finding and doing.

Use this pattern whenever the product can act on the missing result. Deploy it in task managers where missing tickets should be created on the spot, in knowledge bases where missing pages become instant creation prompts, in CRMs where absent contacts turn into add-new flows, and in design libraries where absent assets trigger upload or generate. It especially wins in AI tools where the search-empty often doubles as the first prompt surface. The activation math from the parent article applies directly. Every rescued search-empty cuts the distance from confusion to first value and backfills the product with exactly the content users were hunting for. Do not use it when the zero comes from a failed fetch, broken integration, or network error. That is error-empty territory that needs plain English diagnostics, retry buttons, and status page links. Skip the full creation rescue when the search targets historical records that should exist or when the surface is narrow exact-match like SKU lookup in inventory. Never bandage terrible search quality with clever empty states. If 80 percent of queries return nothing because your indexing is garbage, fix the search engine first then design the empty state. Run the audit from the article. Open incognito, fire off twenty deliberate zero-result queries, screenshot every variation, label them, rewrite the three worst ones this week. Most teams discover their search-empty screens have not been touched since launch.

Search-empty done right turns a missed query into the exact moment users create their most useful content.