Most small business websites with a few pages do not need on-site search: clear navigation does the job. Search starts to earn its place when visitors have to find one item among many, such as a large product range, a help centre, a library of articles or a directory. If people regularly say “I could not find it on your site”, that is the strongest sign.
Search is not a substitute for structure
Visitors use search when navigation fails them or when they already know what they want. A search box can mask a confusing site, but it cannot fix one. Before you add search, check that your navigation design and information architecture make the main journeys obvious. Good internal linking also helps visitors move between related pages without searching.
How much content is “enough”?
There is no official threshold, so treat these as rules of thumb rather than facts:
| Site type | Search worth considering? |
|---|---|
| Brochure site of about 5 to 15 pages | Rarely, navigation is enough |
| Service business with a blog of a few dozen posts | Maybe, if visitors look for specific topics |
| Online shop with a wide range | Yes, plus filters and category pages |
| Documentation, help centre or resource library | Yes, search is a core feature |
| Directory, listings or event sites | Yes, with filters |
A better test than page count is behaviour. Look at your support enquiries, your analytics and how people describe their difficulties. If many visits begin and end on a navigation page, or customers email questions your site answers, search may help.
The main ways to add search
1. Built into your platform
Many content management systems and shop platforms include a basic search box. It is the simplest option and often enough for small sites. The limits are usually weak ranking, little tolerance for typos and plain results lists. Test it with five real queries before deciding it is fine.
2. Static-site search index
For sites built with a static site generator, a search index can be created at build time and shipped with the site, so searching runs in the visitor’s browser. Pagefind is one open source example. Its documentation explains that it runs after your static site generator, indexes the generated HTML and outputs a static search bundle, with no server component, and that it should be run after every build before deployment. Its docs also recommend setting the lang attribute on the html element for best results.
This suits blogs, documentation and brochure sites with a content library, where content changes at deploy time rather than minute by minute. It does not suit content that changes constantly in a database, such as live stock levels.
3. Hosted search from a search provider
Google’s Programmable Search Engine lets you build a search engine limited to your own site or a set of sites, with customised look and feel and an embeddable element. At the time of writing (November 2026), Google’s documentation lists a free standard element that shows ads, and paid options and a JSON API that show no ads, the latter with a daily query limit. Check the current page for the up-to-date terms before you commit. Other hosted search services exist, generally priced by volume of records and searches.
4. Custom or enterprise search
Large catalogues sometimes need a dedicated search platform with typo tolerance, synonyms, filtering and merchandising rules. That is a larger project, and usually only justified when search directly drives sales.
Choosing between them
| Option | Best for | Trade-offs |
|---|---|---|
| Platform built-in | Small shops and sites | Basic ranking and features |
| Static index (such as Pagefind) | Static sites, blogs, docs | Updates at build time, not real time |
| Hosted search | Medium sites needing better results | Third-party dependency, ads or fees |
| Custom or enterprise | Large catalogues | Cost and maintenance |
Making search useful
A search box is only as good as what it returns. Check these points:
- Place it where people expect it. Top right or in the header, with a visible icon or label.
- Make results readable. Show title, a snippet and ideally a category.
- Handle no results. Offer suggestions, popular pages and a contact link instead of a blank page.
- Cover the language people use. Customers search with their words, not your internal terms. Review the queries visitors actually type and add content or synonyms for common ones.
- Keep titles and descriptions clear. Search results reuse them, so thin or duplicated titles give poor results.
- Support keyboard use and screen readers. Label the field and announce results clearly.
- Measure it. Track popular queries and searches with no results, then fix the content gaps. That is closely related to a content gap analysis.
Performance and privacy considerations
Search adds weight to a page, particularly third-party widgets. Load it on demand rather than on every page where possible, and see our notes on JavaScript weight and third-party scripts. If a hosted provider records queries, mention that in your privacy policy.
A practical rollout
- Check your analytics and enquiries for evidence that people cannot find things.
- Improve navigation and internal links first.
- Pick the lightest option that fits your platform and update frequency.
- Test with ten real questions your customers ask.
- Review search queries after a month and fix gaps.
Where Radiance Impact fits
Radiance Impact’s Technology division builds and redesigns business websites, including content-heavy ones where findability matters. To discuss whether your site needs search, contact us or see the Technology page.
Sources
- Getting Started with Pagefind, Pagefind
- Programmable Search Engine overview, Google for Developers
