Catalogue search: filters and empty results

Catalogue search helps the client move from a general request to a suitable item. But the search bar itself does not solve the problem: the name of the product may differ from the usual word, filters may exclude the desired option, and an empty search result may not explain what to do next. As a result, the visitor does not understand whether there is no product at all or whether he simply could not find it.

Customization should begin with the content of the catalog and real selection methods. Some characteristics are important for real estate, while others are important for equipment. Below is the procedure for working on search, filters and interface states. It is suitable for both a new project and for updating an existing website without completely changing the design.

1. Understand how customers search

Make a list of typical requests: category name, brand, model, article, task or characteristic. For each example, state in advance the expected eligible items and the clearly unsuitable options. This will make the search discussion concrete: instead of “works poorly,” there will be a testable set of scenarios. Use impersonal appeals and wording from conversations with managers if such information is already available.

Define boundaries: product search does not have to simultaneously search for articles, documents and services. If these sections are needed in the overall search results, separate the results by type. Separately, decide how to display discontinued items and pre-order options. It is better to include these rules in technical specifications for the site, in order to then check them upon acceptance.

2. Prepare consistent catalogue data

Filters will not correct chaotically filled cards. The same characteristic should be stored in a consistent field, not sometimes in the title, sometimes in the description. Convert units of measurement to accepted formats, separate numbers from explanations, and check brand names. If an item has an unknown size or material, do not replace missing data with a random value.

Keep the original information for review and assign someone responsible for new cards. Characteristics directories must be updated along with the catalogue: otherwise, after import, values ​​that are close in meaning but different will appear. Before running a search, check the selection manually. The problem found may be related to the data and not the search engine; fixing it only by adjusting the ranking will be unreliable.

3. Agree search and sorting rules

Decide which fields to search and which matches to consider more meaningful. The exact article usually requires a separate workflow: you should not mix it with long descriptions without checking. For word searches, discuss word forms, acceptable misspellings, and synonyms. Don’t add automatic term replacement if it might change the meaning of the query or hide the exact match.

Relevance and sorting are different things. After choosing a price in ascending order, the visitor expects a consistent order, and not an unobvious promotion of individual items. Determine the behavior of equal values ​​and missing price. If part of the results is advertising, it needs to be indicated. Test rules against approved requests, not just one example that conveniently shows the chosen mechanism.

4. Show useful filters

Select the characteristics that really make the client narrow down their choice. It is not necessary to show all fields of the card. Filters must correspond to the category: the amount of memory is useful for one group of products, but meaningless for another. Indicate the active conditions next to the results and give the opportunity to remove an individual condition or reset the entire set.

Describe the logic of the combinations. For example, several selected brands can expand the choice within one group, and a price limit can narrow it down at the same time. The user must understand the result without reading the instructions. Empty and unavailable filter options should not appear as normal operational values. Controls need clear labels: this follows the approach from the W3C Form Field Labeling Guide. A disappearing tooltip inside a field is often not enough.

5. Handle empty results and errors

The “Nothing found” message should provide context: what request was executed and what restrictions were applied. Suggest removing a specific filter, correcting the query, or returning to a category. If you show similar items, explain that they do not fully correspond to the original conditions. You cannot quietly replace the exact search results with arbitrary products and call it a search result.

Distinguish between an empty search result and a loading error. If the server request fails, the site doesn’t know if there are any matching items, so the message that there aren’t any is incorrect. Leave the parameters as they are and show the option to repeat the request. If results are updated without reloading the page, provide an accessible message about completion and the number of items found; the approach is described in W3C explanation of status messages.

6. Preserve state and check speed

After opening the card and returning back, it is useful for the client to see the previous request, sorting and filters. Decide in advance which parameters are saved in the page address and which are valid only in the current session. The link to the collection should open a consistent set of terms. Do not place personal data and internal information of the client in such an address.

When quickly entering text, responses may come in a different order: the old result should not replace the new one. The interface needs loading states and protection from unnecessary repeated requests. Test performance on a data volume and device close to working, including a weak connection. Don’t promise speed on a single check of an empty catalogue. The reasons for the overall slow loading are discussed in the article about the speed of the site.

7. Plan URLs and launch tests

Filter combinations can create multiple addresses with similar results. Determine which pages are needed as independent landing pages, and which ones only serve the convenience of the visitor. Google’s documentation on faceted navigation describes why uncontrolled proliferation of such URLs wastes crawl resources. The choice of crawling and indexing rules depends on the site structure; each set of options cannot be automatically considered a separate useful page.

Check the exact SKU, common word, typo, empty query, and incompatible filters before releasing. Add return from card, reset conditions, sort and repeat after network failure. On a phone, make sure the filter panel closes, your selections are visible, your keyboard isn’t obstructing your actions, and your results remain accessible without scrolling horizontally.

Where to start improving the catalogue

For the first iteration, a consistent set of queries, well-filled characteristics and clear issuing rules are sufficient. You can then test basic filters, empty states, and return to list. Evaluate the result by completing specific scenarios: whether the desired item is located and whether the visitor understands how to change the conditions. The mere appearance of a search bar does not mean that the catalog has become more convenient.

In SkyCode portfolio you can see examples of completed interfaces. Describe in the brief your catalog, important characteristics and examples of requests that are currently not working – this will help determine the composition of the improvement and the criteria for checking it.