Information checked: 21 July 2026.
Site search is valuable when visitors know what they need but cannot predict the navigation. A search box is not complete until results are relevant, empty states are helpful and private content cannot leak into the index.
In brief: Search should help visitors recover from imperfect wording without exposing private content or creating an unmonitored data store.
Define what should be searchable
- Published pages and articles.
- Products, services or locations where appropriate.
- PDFs only when their text, ownership and update process are controlled.
- Exclude drafts, account pages, checkout, internal records and expired content.
- Decide how synonyms, spelling and UK terminology are handled.
Design useful results
| Element | Purpose | Common failure |
|---|---|---|
| Clear title | Shows the destination | Displaying filenames or internal IDs |
| Short excerpt | Explains relevance | Repeating boilerplate navigation |
| Content type or category | Helps disambiguation | Mixing products and help articles without labels |
| Filters | Useful on large mixed collections | Adding controls to a very small site |
| Empty state | Offers correction and navigation | A blank “no results” page |
Use search data carefully
Record aggregate queries and zero-result terms to improve content, but avoid storing unnecessary personal or sensitive searches. Explain analytics where required and restrict access to raw logs.
Protect performance and security
Escape and validate input, limit expensive requests and keep private content outside the public index. Search should not reveal unpublished titles, member records, server paths or fragments from protected documents.
Acceptance test
Test common queries, misspellings, synonyms, long input, special characters and zero results. Verify keyboard use, mobile layout, result permissions and response time with a realistic content volume.
Example: private titles appear in results
A search index includes draft client pages and returns their titles to signed-out visitors, even though clicking the result is blocked. Indexing permissions must be applied before content enters the search store, not only at the final page request. Rebuild the index after permission changes and test with several account roles.
What the business should retain
- Searchable content rules
- Synonym and spelling list
- Permission-aware indexing test
- Zero-result query report
- Log retention and access controls
Sources and date checked
Technical and product information was checked against the following primary sources on 21 July 2026. Plans, interfaces and provider terms can change, so recheck them before purchase or migration.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.