Search UX

The shop stocks it. The listing calls it something slightly different, and no part of the search knew the two were the same word.

Search is the one place where somebody hands you their intent in their own words, unprompted and specific. Baymard's 2026 benchmark still finds 56% of sites with mediocre or worse search, which makes it the most valuable signal in most products and the least designed.

Anatomy of a Search

Search is usually treated as one component. It is seven parts serving two different jobs, and most products design for one of them.

The Parts

Seven, spread across two screens.

The box and its submit. The query somebody typed. The suggestions offered while they type. The results list and the result item inside it, which decides whether anybody can tell the results apart. The refinements, meaning filters and sort. And the empty result, for when nothing matched, which article 6 covers on its own.

The query also belongs in the address, so a search can be sent, bookmarked and returned to. That is the same rule Back Button applies to any state worth linking to.

Two Jobs, One Box

The distinction that decides most of the design.

Known-item search is somebody who can name what they want: a product code, a person, a setting. Success is one correct result, fast, and everything else is noise. Exploratory search is somebody working out what exists: winter jackets, invoices from last year. Success is a set they can narrow, so filters, sort and the result item carry the weight.

A box serving both has to make the first fast without making the second useless. That is why suggestions matter so much, since they turn a vague query into a specific one before it is submitted.

What the Result Item Owes

The list is where a search succeeds or is abandoned, and the unit is the row.

Each result needs enough to be told apart from its neighbors without opening it. The thing's name, the one or two attributes people choose on, and where it sits if the site is deep. A results list of twenty near-identical titles has answered the query and not the question.

What the Box Is Not

Two things get pushed into search because there is nowhere else.

It is not a substitute for navigation, since somebody who searches because the menu was unreadable was let down upstream. And it is not a filter, since narrowing a set somebody is already looking at is a different control. Navigation Queries covers the first and Data Tables & Filtering the second.

Pro tip: Pull your hundred most common queries and mark each one known-item or exploratory. The ratio tells you which half of this module to spend your time on, and almost nobody has looked.