A zero-result page is a guide, not a dead end

What it is

Zero rows are not the end page of a finding session; they are a fork on a berrypicking path. A zero-result page is a guide means the empty view should still send people into finding that can continue: a neighboring class, a topic that still has content, a browsable entry, another collection known to exist. It admits this shot missed, and refuses to style the interface as a terminus—no primary action, nowhere to go, only Back.

Guiding is not explaining the 0 again, and not loosening the current constraint one more notch. Those two steps handle this query. Guiding handles “even if this query is a total miss, finding itself is not over.”

Why it happens

Under ASK the target is allowed to change. An empty set is a legal moment to change it: the particular policy may not live in this library, but the need “reimburse” still does, and the neighborhood may hold a procedure, a training, another document number. Bates’s path depends on a visible next step; an empty page that only offers Back visually severs the path, and people generalize “not here” into “this product cannot do this job.”

Guiding has to turn other entries into the collection back into scent sources. Category links, related topics that still have hits, a recent successful browse origin—all say “finding can take another road.” If the guide pushes unrelated campaign slots or ads, the fork is swapped for an exit, and trust is worse than a plain 0: the system looks as if it is using failure to sell. What is guided to must still be a finding object, not arbitrary fill.

Studying it

Watch whether, after an empty page, people leave the product, go back the way they came, or continue from an entry the empty page offered and reach an acceptable object.

• Paradigms: exploratory tasks steered into an empty set; one condition count-and-back only, one neighborhood entries; process traces of a strategy switch (search → browse). Query logs: whether the page after zero is off-site, a re-query in the same box, or a tap on the empty page’s guide. Hearst treats empty results as still part of the search UI, not an error page.
• Independent variables: whether a browsable neighborhood is offered, semantic distance from the original query, whether the guide is finding objects or campaign content.
• Dependent variables: whether the session continues after empty, whether continuation completes an acceptable target, rate of generalizing “nothing” to the whole product.
• Methodological note: known-item tasks will score “take another road” as failure, because the gold is that one object. Exploratory tasks are what make guiding’s value visible. High tap rates on the guide can be desperate poking; constrain them with whether continuation completes an acceptable target.

Where it stops holding

In safety and compliance, empty may mean “you should not see this”; guiding to a neighbor is a leak, and a terminus is correct, with only Back. In a purchase flow, an empty miss steered to unrelated bestsellers is substituting a decision, not helping finding. Emptiness from offline or a failed service is not a finding fork; the guide is retry, not categories. When the user is clearly looking up an exact identifier, neighborhood suggestions are noise; keep the guide down to “check the ID / go back.”

Applying it

• Below cause and relax actions, offer a browsable entry in the same topic as the original query, or a neighboring class that still has content, copy-marked as another way to look.
• Do not put campaign slots unrelated to finding on the empty page; failure is not a sales moment.
• Keep the search box and the original query so someone can change one word and continue; do not make the empty page “return home” only.
• Verify by steering someone who cannot name the exact title into an empty set. If the next move is only Back or quitting the app, the page is a terminus. If they can continue from a neighborhood on that page and reach an acceptable object, guiding holds. If the neighborhood is unrelated to the original need, the guide changed the subject.

Related

• Within the group: G3.07.1 Zero-result states must explain why, not only report the count · G3.07.2 Zero results should offer concrete actions that relax constraints
• Adjacent: G3.01 Searching versus browsing · G3.10 Faceted navigation · T2.05 Empty-state and zero-result copy
• Search terms: zero results · berrypicking · exploratory search