The current search scope must be visible
Aliases: scoped search · search place · scope label
What it is
Before a query is issued, people must be able to see which collection the sentence will run against—the whole site, this section, this folder, or only the open article. Visible search scope means the scope is written as interface state, not inferred after the fact from the shape of the results. When scope hides in a placeholder, implicit context, or a previous session, people read local results with global expectations, or the reverse.
Making scope visible is not a decision about whether the default should follow the current page—that is a scoping policy. The claim here is only: whatever the default is, the one in force must be readable.
Why it happens
A search box does not, by itself, carry a collection boundary. The same string recalls entirely different objects in the full corpus, in Help, and in “this page.” People treat the box as an entrance to the largest set, because web search trained that habit. If the product actually binds the box to the current section, and the section name lives only as a highlight in the nav, the place in working memory and the place being searched come apart: sparse results are read as “nothing exists,” when the run was simply in the wrong field.
Scope is part of the query, yet it is often not in the query string. Unwritten, it cannot be inspected, blamed, or deliberately changed. A perfectly ranked result page is then answering a question the user did not agree to ask.
Studying it
Measure judgments of “where am I searching,” not which default layer is more accurate.
- Paradigms: place the same query in interfaces where scope is unlabeled, written in the box, or written only in the result heading; ask before issue and after results “which collection do you think this searched.” Abandonment around scope switches in query logs is field evidence, but abandonment alone does not prove the scope was unseen.
- Independent variables: label position (in-box / beside the box / results page only), whether the scope uses the same name as navigation.
- Dependent variables: accuracy of pre-issue scope judgments, rate of treating local zeros as “not in the whole corpus,” time to find a scope control on purpose.
- Methodological note: participants who just clicked in from a section page overestimate “of course we are searching this section.” Include paths that focus the box from global navigation. Inconsistent names (nav says Support, box says Help Center) cause their own errors and must be scored apart from “no scope written at all.”
Where it stops holding
A product with one collection and no local index (a flat photo album) makes a scope label noise. Command palettes and developer tools (“current file / workspace / all”) are learned patterns for experts; visibility still helps, but the cost of omission is lower than for occasional users. Voice search has no persistent box; scope has to be spoken in the confirmation, or the same mechanism holds on a different carrier.
Applying it
- Write the current scope in or immediately beside the box (“in Help,” “in this folder”), and repeat it in the result-page heading after submit.
- Use the same words as navigation and breadcrumbs. Do not give one collection two internal code names.
- When scope changes, update the label. Do not leave a stale “entire site” sitting there.
- Verify by screenshotting the box before issue, hiding the rest of the page, and asking “where will this sentence search.” A wrong answer, or “probably everything,” means scope is still not explicit.