Zero hits in a narrow scope should offer one-click expansion to the parent

What it is

Zero hits in this folder or this section does not mean the object does not exist. One-click expansion to the parent scope makes “run the same sentence one level up” an action on the zero-result page, instead of making people change scope and retype. “Search the whole site,” “find in the entire drive,” are product forms of this path. It is a widening of range, not a synonym swap, and not clearing filters.

The general rule for zeros is to say why and offer a next step. Here one next step is fixed: walk one level up the tree, query string unchanged.

Why it happens

A narrow-scope zero has two common truths: the object is truly not in the subtree, or it sits in the parent and the person is on the wrong layer. The second is frequent in nested collections, because the default follows the current place. Facing an empty list, the expensive correction is re-choosing scope—the control is often off-focus, and the query may have been cleared. One-click enlarge drops that correction to a single press and pre-commits to “the same sentence, a bigger box.”

Without enlarge, people rewrite the query (add words, drop words, swap synonyms) and perform irrelevant query surgery inside the wrong small set. Logs show a run of short queries after a narrow zero, never a scope change. Enlarge moves the hypothesis from “wrong words” back to “too small a place,” which is the layer more likely to be true.

Studying it

Place the target in the parent, not in the current child range, and compare presence versus absence of “search one level up / search all.”

• Paradigms: issue a query from a child folder that must zero; the target lives in the parent; the zero page either carries one-click enlarge that keeps the original string, or only says “not found,” or only offers rewrite suggestions. Empty-state copy studies supply general methods for “next action”; here the action must be a scope enlarge.
• Independent variables: whether the enlarge control exists, whether it goes to the immediate parent or jumps to global, whether the original query is kept.
• Dependent variables: time from zero to a hit, whether the query was rewritten, whether people abandon.
• Methodological note: if the target actually sits in the current scope, enlarge measures mistaken widening, not recovery. The task must be “wrong layer.” Enlarge-to-global and enlarge-to-parent are different designs; score noise and recovery separately.

Where it stops holding

When the current scope is already the root, there is no parent to enlarge into; the control should vanish or become a different widening (drop filters, spelling). A permission-isolated subtree must still be invisible after enlarge to the parent, or one click becomes a privilege escalation; a parent zero should say “no permission,” not offer another futile enlarge. When the object is not in the product at all, enlarge only delays the hit; a real zero exit (rewrite, browse) is still required. In speech, “one click” becomes a spoken confirmation: “search this sentence across all files?”

Applying it

• On a child-scope zero page, put a primary button: “Search ‘parent name’ for ‘original query’.” The press re-runs the original string in the parent scope.
• Do not write “try searching everything” without carrying the string. Do not auto-enlarge either: silent enlarge makes people think the object was never here, when the field was swapped under them.
• If the parent is also zero, then offer global or rewrite. Do not stack three equal-weight enlarges on one page.
• Verify with the target in the parent folder and the current place an empty child. After the zero, one click should show the target in the parent under the original query. If people must change scope and retype, or a click jumps to unrelated corpus-hot hits, enlarge did not aim at the parent.

Related

• Within the group: G3.16.1 Default scope should be the current context, not the whole collection · G3.16.2 Nested scopes inherit: a child collection sits inside its parent · G3.16.4 Searching several scopes at once requires one shared relevance scale · G3.16.5 Scope changes ranking; top hits from different scopes are not comparable
• Adjacent: G3.07 Zero-result handling · T2.05 Empty and zero-result copy · G3.12 Search scope
• Search terms: scope expansion · zero results · search parent collection