Article6 min readUpdated
Search UX Design: Search, Filters and No Results Pages
Search UX design for shopping, listings and directories: search bar, product filter UX, sort options and no results page, with exact examples.
By Tithi Mondal, UI/UX Designer
Suppose a user opens a directory of electricians in Siliguri. She types "electrician" and gets 140 results in a random order. There is no way to narrow by area, no way to see who is available today, and no way to tell the most reviewed from the least. She leaves and calls a cousin. Search UX design is the work that prevents this. It covers the search bar, the filters, the sort options and the page you show when nothing matches.
Decide who is searching and who is browsing
Two kinds of people use a listing. Searchers know the word for what they want, such as "blue kurta" or "plumber". Browsers do not know yet, and they want to look around.
Searchers need a strong search bar. Browsers need categories and filters. A good screen serves both, but you must choose which one leads.
- A shop with 30 products: lead with categories. Search is a small extra.
- A shop with 3,000 products: lead with search. Categories support it.
- A directory of local services: lead with search plus location, since "near me" is half the question.
Put this decision into your wireframe before you pick colours. My wireframe vs mockup vs prototype guide explains why that order saves rework.
Search bar design
The search bar is the front door. Make it easy to see and easy to use.
Do this:
- Place it at the top of the screen, full width on mobile.
- Use the magnifying glass icon plus a placeholder that says what can be searched: "Search kurtas, sarees, shirts".
- Make the field big enough for a thumb, at least 48 pixels tall.
- Open the keyboard with a "Search" key, not a "Return" key.
- Keep the typed words in the box after the results show, so the user can edit them.
Do not do this:
- Do not hide the search behind an icon on a site where search is the main task.
- Do not use a placeholder such as "Search" and nothing more.
- Do not clear the box when the user goes back.
Suggestions while typing help a lot. After 2 or 3 letters, show 4 to 6 suggestions below the box. Include recent searches for returning users, with a small cross to remove each one. Support common spelling mistakes and mixed English and Bengali or Hindi words typed in English letters, such as "sari" and "saree". For wider language choices, see regional language app design.
Product filter UX: what to offer and in what order
Filter design is about giving people the few questions that really help them choose. Not every field in your database is a filter.
For a clothing shop, a sensible filter order is:
- Category
- Size
- Price range in rupees
- Colour
- Brand
- Delivery speed
For a directory of tutors or electricians:
- Area or PIN code
- Available today
- Rating
- Price per hour or per visit
- Language spoken
The order follows what most reduces the list. Put the strongest filter first.
How filters should behave
- On mobile, put filters behind a single button labelled "Filter", with a count when active: "Filter (3)". Open them as a full screen sheet with an "Apply" button at the bottom.
- On a desktop site, a left column of filters is normal, and results update when a filter changes.
- Show the number next to each option: "Cotton (42)", "Silk (9)". Hide or grey options with 0 results.
- Show chosen filters as small removable chips above the results: "Size M x", "Under ₹1,000 x". One tap removes one filter.
- Add a clear "Clear all" link.
- For price, use a slider with two typed boxes, since sliders are hard to use precisely on a small screen.
Do not let a filter combine into zero results without warning. If a user picks "Silk" and "Under ₹500" and nothing exists, tell them before they press Apply, or show "0 results" on the button.
Sort options
Sort answers a different question from filters. Filters decide what is in the list. Sort decides the order.
A short, clear list works best:
| Label | When it fits |
|---|---|
| Relevance (default for search) | After a typed search |
| Price: low to high | Shopping |
| Price: high to low | Shopping |
| Newest first | Fashion, listings, jobs |
| Rating | Services and directories |
| Nearest | Local services, restaurants |
Rules I follow:
- Pick a default that makes sense, and say what it is: "Sorted by: Relevance".
- Keep the sort control separate from filters. Two small buttons side by side, "Sort" and "Filter", is a familiar layout.
- Keep the user's sort choice when they open a product and come back.
- Do not offer 10 sort options. Four to six is enough.
Be honest about "Relevance" and "Featured". If paid listings rank first, mark them with a clear "Sponsored" label. Hiding that destroys trust, which is why honest labels matter.
The no results page
A no results page is not an error. It is a moment where a user is close to leaving, and you can still help.
A weak page says: "No results found." Nothing else.
A useful page says:
- What was searched: "No results for 'kurtha'".
- A likely fix: "Did you mean 'kurta'?" with a tap to search again.
- What to try: "Check the spelling, or search a shorter word."
- A way out: popular categories, or a few best sellers, or the closest results with a note: "Showing similar items".
- If filters caused the empty list: "No items match all your filters. Remove 'Under ₹500'?" with a button that does it.
- For a directory with no listing in the area: "No electricians in 735101 yet. Show nearby areas?" or "Get a message when one joins".
Write this in the tone of a helpful shopkeeper, not a system. More guidance is in UX writing and microcopy for apps.
Also log what people search and find nothing for. That list shows you what stock or listings you are missing. It is free research.
Loading, speed and small details
Results need to appear fast. On slow networks, show a skeleton, which is grey placeholder blocks in the shape of the results, instead of a blank screen. Load the first 10 to 20 results and add more as the user scrolls, or use a "Show more" button when the footer matters.
Small details that add up:
- Show a result count: "42 results for 'kurta'".
- Show the same card layout across results, with image, name, price and one key fact.
- Keep scroll position when the user goes back from a product page. Losing it is very annoying.
- Make sure the filter button and chips can be reached by screen readers and keyboard, as described in my accessibility guide.
Check your search before you ship it
Here is a quick test I run on any search screen:
- Search a word with a spelling mistake.
- Search for something you do not sell.
- Apply 3 filters, then go back and forward.
- Change the sort, open a result, and return.
- Do all of it on a small phone with a slow connection.
If any step leaves you stuck, users will be stuck too. A UX audit checklist covers the wider screens around search. If your shop or directory needs search and filters designed properly, see my UI/UX design service or write to me through the contact section.
Frequently asked questions
How many filters should a product page have?
Show the 4 to 6 filters that most help people decide, such as category, size, price and brand. Hide the rest behind a 'More filters' option.
Where should the sort option go on mobile?
Put a 'Sort' button next to a 'Filter' button above the results. Each opens a bottom sheet, and the current choice is shown on the button.
What should a no results page include?
It should repeat the search term, suggest a spelling fix, offer a way to remove filters, and show popular or similar items. It should never be a blank page with only 'No results found'.
Should search suggestions appear while typing?
Yes, after 2 or 3 letters. Show 4 to 6 suggestions and recent searches, so users type less on a small keyboard.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.