![]() ![]() Users become overwhelmed when their search terms result in seemingly irrelevant results, or too many results to process. It stands in sharp contrast to the page that had contextual category or search query suggestions at the no-results page, as seen in the Amazon example. For products like appliances, where details like model numbers, ratings and dimensions are major factors in the user’s selection process, list view makes most sense.Ī “no results” page as seen at HP example is essentially a dead-end for the user. A key factor in selecting list view versus grid view is how much information a user needs in order to choose between products. Let’s examine this rule in context of product page. A rule of thumb: Details in lists, pictures in grids. Two basic layouts for content presentation are list view and grid view. One of the challenges of displaying search results is that different types of content require different layouts. To make it easier for them, leave the initial search term in the search box so they don’t have to re-type the entire query again. Query reformulation is a critical step in many information journeys: if users don’t find what they’re looking for then they might want to search again using a slightly modified query. ![]() ![]() Don’t erase users’ query after they hit the Search button The results page is a crucial piece of the search experience: it presents an opportunity to engage a dialogue that guides users’ information needs. Up to 30% of visitors will use the site search tool and these will be highly motivated shoppers who know exactly what they’re looking for.Īfter adding image previews to their auto-suggestion, the LED HUT increase their search conversion Results PagesĪfter helping users input their search data as quickly, easily and accurately as possible, your goal should now be to deliver the most accurate search results in a legible and easy-to-digest fashion. In large e-commerce websites, search bars move out of the header and take on a central role in the UI. E-commerce sites are probably the most common use cases for utilizing search because users are searching for detailed products. Search becomes increasingly central as websites grow in size and complexity. fewer than 100-200 pages), there’s no need for search. ![]() When a site has a limited amount of content (e.g. Smaller websites are better without search. But before we start our journey, let’s answer one important question - when do you need search? When you should (or should not) have search on your site search might be primary/secondary feature for your site it might be simple drill down or advanced with parallel selection), there are a few general tips that work for multiple different types of apps and websites. Although the exact recommendations may be subjective based on your needs and goals (e.g. For ease of reading, I’ve broken this article down into two key areas: search box design and placement result page. There are a number of things to think about when designing the UI behind search and results. Users expect smooth experiences when searching and they typically make quick judgments about an app’s value based on the quality of one or two sets of search results. 1 // In is like a conversation between the user and app or website: the user expresses their information need as a query, and the app or website expresses its response as a set of results. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |