A search field must show what it will search
Aliases: search scope · query domain · this-page versus global
What it is
The same magnifying-glass slot may search the current list, the current site, or the open web. People build the query for the scope they believe is in force; a wrong scope turns empty results or a pile of misses into “search is bad.” A search-scope signifier marks “what this box searches” before it is used. The issue is the query’s domain, not whether Enter and a button both submit, and not how a filled box is cleared.
Why it happens
A query term’s meaning depends on domain: “design” in a document library, a people table, and the web are three different jobs. If scope is implied only by the slot’s place on the page, jumps, nesting, and a global top bar break the implication—a top-bar search looks site-wide and actually filters the current table. People do not read help first; they take a first empty result as “this thing is not in the system,” then widen keywords or quit. Writing the scope into the slot or a selector beside it externalizes the domain before the query is issued. Scope also changes expected syntax: filenames, order IDs, and natural-language questions are different shapes for different domains.
Studying it
Label the same slot “this table / this site / the web,” or leave it unlabeled, and send people in with the same information need. Record whether the first query matches the true domain, whether empty results lead to a scope change, and whether they switch to another entry. Factors: slot position (top bar versus table header), a scope dropdown. Outcomes: domain-judgment accuracy, attribution of empty results on the wrong domain (“doesn’t exist” versus “wrong place”). Eye tracking can show whether scope copy is read before submit. Do not only measure whether a hit was found; measure how people explain a miss after searching the wrong domain.
Where it stops holding
When the product has one domain (the whole app is an address book), a scope mark is surplus; the page title is enough. When several scopes coexist and the default follows context (project page to profile), the same top-bar slot must change its label or it is lying. Voice search and barcode-launched queries have no “words on the slot”; scope must be restated on the result page. Permissions shrink the actual domain: a mark that says “whole site” while results are role-filtered should read “what you can see.”
Applying it
- Put a short name of the current domain on the slot (“search orders,” “this page,” “help”), not a wordless magnifying glass.
- When context changes the domain, change that name; do not let the top-bar slot keep the previous page’s scope.
- When several domains exist, provide a discoverable scope switch and keep the current choice visible before and after submit.
- Verify by cropping the slot off the page and asking what it will search. If the answer disagrees with the true endpoint, scope is still implied by place. Then force an empty result across scopes and see whether people change scope rather than quit.