Skip to content
Tutorials Center
My learning

Topics

Lesson 18 of 36 ยท Information Architecture

Labeling and Search Design

Learn to write clear navigation labels, design search boxes, suggestions, filters and no-results pages, and use search logs to improve your information architecture.

The best structure fails if people cannot understand the words on it. Labels are the names of links, menus, buttons and headings. Search is what people use when they would rather ask than browse. Both are part of information architecture, and both are mostly about language.

Writing good labels

A good label is clear, specific, familiar and consistent.

  • Use the users' words. Research (interviews, card sorts, search logs) tells you what people call things. A bank may say "Remittance"; customers say "Send money".
  • Be specific. "Resources" or "Solutions" mean little. "Pricing", "Guides" and "Case studies" are concrete.
  • Be distinct. "Support" and "Help" next to each other force a guess. Labels should not overlap.
  • Lead with the keyword. "Returns and refunds" scans better than "Information about how to return".
  • Be consistent. If it is "Sign in" in the header, do not call it "Log on" in a button. Pick one term and one capitalization style.
  • Keep it short. One to three words for navigation, a few more for buttons ("Download invoice").
  • Use verbs for actions, nouns for places: "Create account" (button) versus "Account" (section).

Link text should make sense out of context. A screen-reader user can pull up a list of all links, so "Click here" and "Read more" repeated ten times is useless. Write "Read our returns policy".

Icons need labels

Icons alone are ambiguous. A heart may mean "like", "save" or "favorite". Pair icons with text unless the symbol is universal (a magnifier for search, a house for home), and still test it.

Good labels are

Familiar In the user's words
Specific Say what is behind it
1 / 2

Search matters most for large sites and for people who know what they want. A study of many sites repeatedly finds that visitors who use search are more focused and often convert more, so a bad search box is expensive.

  • Make it visible: a box with a magnifier icon, not only an icon, on content-heavy sites.
  • Make it wide enough for typical queries.
  • Support the shortcut (such as / or Ctrl+K) on desktop tools.
  • Keep it in a consistent place, usually the top right or center of the header.

Helping while typing

  • Autocomplete / suggestions: offer likely queries or results as the user types, with the typed part highlighted.
  • Spelling tolerance: handle typos ("sneekers" finds "sneakers").
  • Synonyms: "couch" should find "sofa".
  • Recent searches for return visits.

Results and filters

  • Show the query and the number of results.
  • Rank by relevance; consider boosting titles over body text.
  • Offer filters and sorting relevant to the content (price, size, date). Show the active filters and an easy way to clear them.
  • Highlight matching words and show enough context in each result.

No results

An empty page is a dead end. Instead:

  1. Say plainly that nothing matched, and repeat the query.
  2. Suggest fixes: check spelling, use fewer or more general words.
  3. Offer alternatives: popular items, categories, a contact link.
  4. Log the query so you can fix the gap.

Learning from search logs

Search logs are a gold mine. They show the exact words people use, what they fail to find, and what they search for most. Review them regularly:

  • Top queries: should these be in the main navigation?
  • Zero-result queries: missing content, missing synonyms or wrong labels?
  • Queries followed by immediate reformulation: the first results were poor.
  • Queries on pages with navigation: maybe the menu is unclear.

A stand-in: log analysis

This stand-in processes a small invented search log to show the top queries and the zero-result ones. Real logs are much larger and need privacy care (strip personal data).

JS Search log analysis (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The repeated zero-result "refund" shows people use a word your content does not use: add it as a synonym or a label.

Accessibility notes

Label the search field (<label> or aria-label), make suggestions keyboard operable, announce result counts to screen readers, and never rely on color alone for filter state. See Accessibility in UX.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which label is best for a link about product returns?

    It is specific, familiar and starts with the keyword.
  2. 2. What is a good approach to a no-results page?

    Help users recover, and log the query to find gaps.
  3. 3. What do zero-result queries in search logs reveal?

    They show where users' words do not match your content.
  4. 4. Why are icons without text risky?

    The same symbol can mean different things; add a label.

Summary

  • Labels should be clear, specific, distinct, familiar and consistent.
  • Write link text that makes sense out of context and pair icons with text.
  • Design search with a visible box, suggestions, typo tolerance, filters and a helpful no-results page.
  • Mine search logs for the real words people use and what they cannot find.
  • Make labels and search accessible.

Next: Visual Hierarchy and Layout