Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. What each operation changes
  2. Keep conditions and results connected
  3. Separate no matches from failure

Search, filters, and results: help customers narrow choices

Distinguish search, filters, sorting, and pagination, decide when they are useful, and keep results understandable.

A large collection of services, projects, or resources can need ways to narrow the choices. Search and filters help, but add interaction and maintenance work. A few services may be better served by clear categories first.

What each operation changes

Operation Purpose Example
Search Find content using words Enter a service name
Filter Restrict the scope Show a particular area or service type
Sort Change result order Order by date or price
Paginate Show a section of the same results Open the next page of projects

Use customer language. Internal categories may make selection difficult even when the controls function correctly.

Keep conditions and results connected

Customers should see their current choices and know how to remove one condition or clear all. When conditions change, results, page position, and selections need clear behavior. Users should not remain on a result page that no longer exists.

If displaying counts, explain whether they refer to all items, matching items, or the current page. Sorting mainly changes order; filtering changes scope. Do not confuse them.

Separate no matches from failure

With no matches, retain the conditions and suggest changing the search or removing restrictions. If loading fails, explain that results could not be retrieved and offer retry. Do not label failure as “no services.” See the shared state guidance .

For example, a customer chooses an area and searches a service name, finding no matches. They should be able to remove the name and continue. Clearing every choice and losing their reading position can make searching harder.

You supply real categories, common wording, and customer search habits. The team handles result logic, mobile operation, keyboard access, and data tests. Agree whether the project needs these features in the design scope .

For a product with substantial search or filtering, our product and UX design service can define the customer flow and browser prototype. Agree the real data and search implementation separately before development.