Search earns its place once a site has enough content that browsing becomes impractical, roughly when the navigation can no longer show everything. Below that, a search box is a substitute for organising the site properly.

The threshold

Not a page count exactly, and the useful test is whether a visitor can see everything from the menu.

A site of a dozen pages, all reachable from a clear navigation, does not benefit. Somebody who cannot find something on it has encountered a naming or structure problem that search will not fix.

A site with a hundred articles, a product catalogue, or a substantial reference section does benefit, because browsing to a specific item is genuinely slower than typing it.

The rough marker is when the navigation can no longer represent the site's contents without becoming unusable itself.

Where search is genuinely needed

That last case is worth noting. A business whose customers search by a code, a model, or a specific term needs search regardless of site size, because browsing cannot substitute for an exact match.

The bad search problem

Worse than no search, and common.

A search box returning nothing for reasonable queries teaches visitors that the site cannot help them, and they leave rather than falling back to browsing.

Default search on many platforms is weak: it matches exact words, ignores synonyms and plurals, handles typographical errors poorly, and ranks results by date rather than relevance.

Which means adding a search box without improving what it returns can reduce the site's usefulness. If you are adding one, it needs to actually work for the words your visitors use.

What a working search needs

  1. Tolerance for misspelling, since visitors type quickly on phones.
  2. Synonym handling, so trade terms and customer terms both find the same page.
  3. Results ranked by relevance rather than by date.
  4. A useful empty state, offering suggestions rather than saying nothing found.
  5. Visible placement, in the header rather than in a footer.
  6. Filters, where the result set is large enough to need narrowing.

The synonym point matters most for trades. Somebody searching for a term customers use should find the page written in trade language, and the default matching will not do that unaided.

The data it produces

The strongest argument for having one, independent of whether visitors need it.

What people type into your search box is a direct record of what they wanted and could not find. That is more honest than any analytics report, because it is stated in their own words.

What it reveals: content you do not have but should, pages that exist under a name nobody uses, products people expect you to carry, and questions your site never answered.

Searches returning no results are the most valuable list on a site, and reading them monthly turns them into a content plan built from actual demand.

Recording that requires configuring site search tracking in analytics, which is a setting rather than a build and is frequently left off.

When the answer is better navigation instead

The alternative worth considering first.

If visitors search for things that exist on the site, the problem is discoverability rather than absence, and the fix is naming and structure rather than a search box.

Common causes: pages named in trade language rather than customer language, a menu organised by how the business thinks rather than what visitors want, and important pages sitting three levels down.

Fixing those helps everybody, including visitors who would never use a search box, which is most of them on a small site.

The practical position

For a small business site: no search box, better navigation, and clear page names.

Once the archive or catalogue grows past what a menu can represent, add search and make sure it handles the vocabulary your customers actually use.

Either way, if you do have one, turn on the reporting, because the queries it captures are worth more than the feature itself, and they answer the question that no analytics report does, which is covered in how pages should link to each other.


Frequently asked questions

When does a site need a search box?

When the navigation can no longer represent the site's contents without becoming unusable. Below that, search substitutes for organising the site properly.

Where is search genuinely needed?

Stores beyond a small catalogue, large article archives, reference material, directories, and anywhere visitors search by a part number or model name.

Can a search box make a site worse?

Yes. One returning nothing for reasonable queries teaches visitors the site cannot help, and they leave rather than falling back to browsing.

What does a working search need?

Misspelling tolerance, synonym handling so trade and customer terms find the same page, relevance ranking, a useful empty state, and visible placement in the header.

What is the best reason to have one?

The data. What people type is a direct record of what they wanted and could not find, stated in their own words, and no-result searches are the most valuable list on a site.

What should I do instead on a small site?

Fix naming and structure. If visitors search for things that exist, the problem is discoverability, and better page names help everybody rather than a subset.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Search box returning nothing useful?

We check whether the problem is search or navigation, and turn on the query reporting either way, since that list is worth more than the feature.

Start a Conversation