Ecom Ideas
  • Homepages & nav
  • Category pages
  • Product pages
  • Cart pages
  • Checkout
  • Site search
  • Internationalization
  • Holiday ideas
  • Featured idea gallery
  • Topical articles
Subscribe

Get daily ideas

LinkedIn
šŸ’”
Ecom Ideas
/Site search
Site search
/
āŒØļø
Autosuggestion
āŒØļø

Autosuggestion

Tap any tip to open toggle ⚔ some gifs may take a moment to load

Featured ideas šŸ¦„Ā are rare ideas you may not have seen before ;-)

šŸ“¼Ā Videos

‣
Good Idea šŸ’” Bad Idea šŸ’£ Typeahead Edition Pt 1 (Widget behavior)
‣
Good Idea šŸ’” Bad Idea šŸ’£Ā  Typeahead Edition Pt 2 (Suggestion experience)

šŸ’”Ā Ideas and tips

Widget design and experience

‣
Consider disabling typeahead on mobile
šŸ”Ž
Leaving autocorrect enabled for mobile searchers presents a few usability challenges: šŸ”Ā It competes with autosuggest. If you’ve implemented autosuggest, you want customers to pay attention to this feature, not keyboard autocorrect. If autosuggest is doing its job, it will catch misspellings, whilst guiding your customer to suggestions relevant to your catalog.

šŸ”Ā It takes screen space. Enabling autocorrect makes the keyboard overlay larger, leaving less available viewport for your autosuggest menu.

šŸ”Ā The OS dictionary is not your search dictionary. The keyboard may attempt to autocorrect brand and product names that don’t exist in the standard English dictionary. All your hard work of tuning site search LINK is thwarted if autocorrect successfully hijacks the search.

šŸ”Ā It can apply without the customer realizing it. Ever send a text only to realize you entered the wrong thing after it’s sent? (Sometimes, quite embarrassingly?!) If you do enable autocorrect for the mobile keyboard, use inline highlighting to alert the searcher to the potential error (which may draw attention to the autocorrect suggestion). This works best when you’re not also showing autosuggestions.

‣
Place a ā€œView All Resultsā€ button below product suggestions
šŸ”Ž
In the West, we read left-to-right, top-to-bottom, meaning we scan search results the same way. Showing your View All Results link below results (rather than top-right position) ensures visitors can intuitively take the ā€œnext stepā€ when they’ve scanned visible results.
image
image
šŸ”Ž
Contrast the above examples with a top-right aligned link — blink and you’ll miss it!
image

šŸ‘‰Ā Be sure to use ā€œView all resultsā€ as your button copy, instead of ā€œView moreā€ — users want to know they’re exiting the mini-widget to a more usable ā€œpageā€ of results (complete with filters, etc).

image
‣
Apply a visual hierarchy to suggestion ā€œtypesā€
šŸ”Ž
Using bold headers and spacer lines helps customers distinguish between suggestion ā€œtypesā€ (keywords, categories and product hits), rather than simply stacking them on top of each other with little differentiation. Consider this stack order: Keyword suggestions > Categories > Products Why? It’s about what most helps the user. ⚔ Suggested terms will return all relevant matches ⚔ Suggested categories may not hit the right context ⚔ Suggested products represent a small set of potential matches — it’s hard to get these right

šŸ’ŠĀ RiteAid’s hierarchy makes sense. Show keyword suggestions first, then categories and products in their own lane

image

šŸˆĀ Dick’s Sporting Goods applies gray shading to its product and brand results, keeping the focus on keywords — which are the most relevant suggestions anyway

image

šŸ’”Ā 1st Dibs stacks several suggestion sections, limiting some to 3 hits to keep it easy to scan

image

🐟 Bass Pro Shops’ search and category sections are marked with icons — but they’re not as easy to decipher as headings and clear separation (still nice, though)

image

šŸ’”Ā Matalan uses a spacer line to separate search suggestions from product hits

image
‣
Label your product recommendations as Popular (for context)
šŸ”Ž
Customers assume the products that pull into the autosuggest widget are the most relevant to their search. They’re often not — personalization engines choose the most popular matches. Labeling them as such is more transparent (and arguably persuasive) to the customer ;)
image
image
‣
šŸ¦„Ā Show insta-results (bypass the page load)

šŸ›€šŸ½Ā Lush loads product results and filters directly into its search widget, without the need to jump to a results page (built with Algolia)

image

🪮 Amika does similar (using Searchspring), but lacks filters

image
‣
Consider mini descriptions with product suggestions

🄜 Depending on your catalog and industry, this could be a cool feature - but I suggest implementing this for desktop only, and keeping copy as tight as possible

image
‣
šŸ¦„Ā Consider including price filters in the widget (where appropriate)

šŸ’ŠĀ CVS knows its customer and which search filters to promote to its typeahead widget (this tactic won’t work for every site or brand — but could work great for grocery, travel, marketplaces and sites that sell in bulk)

image
‣
Consider including price detail with product results (where appropriate)

šŸ’Ā Ritani sells high ticket diamonds and understand that price tells more of a product story than thumbnails and product titles. Including this detail makes sense (though a redesign could make it easier to scan/read)

image
‣
šŸ¦„Ā Consider department scopes in the widget

šŸ‘—Ā Fashion Nova lets you scope typeahead suggestions by top-level department. While I suspect most shoppers won’t ā€œseeā€ the tabs, this does provide more precise recommendations for a better search results page

image
‣
Use large thumbnails for product results

🩳 Chubbies uses its typeahead real estate well with large and easy-to-preview thumbnails, rather than the tiny icons so many merchants use

image

🩳 Contrast the above with small images - which do you prefer?

image
‣
Nest category links under search suggestions

šŸ”ØĀ If your search app supports it, nesting category filters under specific search suggestions helps customers pull even more focused results. This example is Lowe’s, using Bloomreach

image
‣
Consider dropping product matches
šŸ”Ž
Showing product matches is so common on ecommerce sites — but does it really help users? When your widget pulls only a few results (but your search results page would show many more), customers can get the impression you only carry what they see in the widget. Naturally, this can lead to them choosing between the options in the widget, and then abandoning the site, rather than viewing your full range. For this reason, consider dropping product matches in favor of search term suggestions.

😬 This example shows 2 product hits in the widget when 8 matches exist in the catalog

image
‣
šŸ¦„Ā Consider showing variant swatches with product matches

šŸ‘–Ā Betabrand lets you preview and toggle thumbnails for color variants — I love the innovation (though larger thumbnails may make this easier to use)

image

Suggestion experience (matching logic)

‣
Show previously viewed searches on-click
šŸ”Ž
Showing search history on-click is useful and personalized — but ā€œrecentā€ searches can get stale. Consider setting a 30, 60 or 90 day reset on these terms, depending on your catalog, customer and the seasonality of buying trends

šŸ”Ā And don’t forget a ā€œClear Historyā€ link!

image

šŸ”Ā IKEA shows recent product views annotated with the search term used to find it — this is cool and innovative, but may not be as helpful as listing the searches themselves. This list can get long, and it’s really a ā€œrecently viewed productsā€ list vs recent searches

image
‣
Trigger suggestions after minimum 3 characters
šŸ”Ž
As mentioned in the Cautions section, triggering suggestions too soon rarely generates relevant results. Enable at least 3 (even 4!) characters before pushing suggestions — they’ll be more useful and cause less distraction and anxiety while typing
image
‣
Show hit counts

😁 This simple touch helps customers gauge how many results they’ll get for each suggestion — this goes both ways — some shoppers want to go wide, others to hone in on a tight set

image
‣
šŸ¦„Ā Show instant feedback when no results match
šŸ”Ž

The sooner you communicate no matches are found, the better. It saves the user submitting a search with disappointing results and gives them the chance to refine their query

image
‣
Highlight attributes, not character matches
šŸ”Ž
A common mistake found in approximately 40% of ecommerce search implementions is highlighting the characters the shopper input instead of the attributes you’re suggesting. This makes it harder to scan the suggestions!

šŸ”Ā Bold styling to suggested attributes makes them easier to scan, but…

image

šŸ”Ā ā€¦colored bold type is even better!

image

šŸ”Ā Contrast this with highlighting the input term — you’re reinforcing relevance but focusing on the wrong detail

image

🫣 Cautions

‣
Don’t pre-merchandize before the user types
šŸ¤”
Roughly 50% of top merchants auto-merchandize the search widget on-click, before the customer starts typing. BAD IDEA! Why? Visitors who use search: šŸ”Ā Have exactly what they want in their head already šŸ”Ā Are task oriented šŸ”Ā Want to complete their task quickly, without distraction Trending and even personalized recommendations are irrelevant to your visitor, unless you happened to magically predict precisely what they want — personalization engines are not mind readers! šŸ”® Rather, your pushy suggestions distract users at best, and outright irritate them at worst. There’s no reason to personalize off-the-jump before users start typing their query.

😬 Without any user input, this typeahead widget is pushing 18 (!) links in one mobile screen

image

😬 This widget resembles a full Collection page, complete with filtered nav

image

😬 This search box is hard to see sliding from the top with so much competing merchandising

image

😬 This widget looks like a main nav flyout menu

image

😬 Notice the suggestions below are all over the place, crossing every department and pet type. How are dog crates, aquariums, leak-proof dog pads and litter boxes ā€œrelated productsā€ to an empty search box?

image
‣
Don’t trigger autosuggestions after the first character
šŸ”Ž
Triggering suggestions too soon is a poor user experience. Your search tool will pull terms and products based on popularity, and the larger your catalog, the less likely your matches will truly be useful after the first 1 to 2 characters. You really need a 3+ prefix to get it going. What’s more, flickering suggestions are distracting. Just let the customer give you at least 3 characters in peace šŸ˜†

😬 Flickering suggestions are distracting with rarely-relevant matches

image

😃 After 3 — even 4 characters provides a more chilled out (and relevant) search experience

image
‣
Be careful with the full-screen takeover pattern
šŸ”Ž
A full takeover gives more space for typeahead merchandizing, that’s for sure, but it feels like you’ve flipped over to a new page — this can be disorienting for users, and it forces them to find that little Close link to exit. If you use this style, consider A/B testing this against a regular widget, and track ā€œCloseā€ events, product clicks, search submissions and site exits as KPIs (rather than simply conversions and revenue). And make sure to watch user recordings for both versions. You really need to observe behaviors for such a feature — it’s time consuming but will give you more insights than top level metrics.
image
‣
Avoid product thumbnails for category and search term suggestions
šŸ”Ž
Product thumbnails are fine for product hits, but are more confusing and less helpful for category and search term suggestions. They can easily be confused with product hits, and can also drag performance.
image
‣
Don’t show product titles without thumbnails
šŸ”Ž
Typeahead search originated as autocompletion to help customers navigate faster, which naturally evolved to autosuggestion of terms. Then it morphed to include product hits, and occasionally merchants replace search suggestions with just product hits :( When product hits are shown as title-only, without thumbnail images for context, they present a few problems: šŸ”Ā Longer line items are much harder to read and comprehend šŸ”Ā Without images, titles can be quite esoteric šŸ”Ā They often don’t match the search term input well, instead are matching attribute fields (which can throw off the customer, who can’t see what the matching logic is under the hood) šŸ”Ā You can’t list all product matches in the list, users may assume what’s shown is all you have There are some industries and use cases where product titles may be better than search terms or image thumbnails — think B2B products with part numbers, books and articles, etc. But these cases are rare.

😬  It’s impossible to choose from such a list without visual context, plus no title keywords match the input query

image

šŸ¤”Ā It’s possible that product titles give enough context for books — but this must be validated with data and real users

image
‣
Don’t show banners in typeahead widget

šŸ¤”Ā Banners are uber-popular in menu flyouts, but rarely add value to the typeahead experience. Again, users are focused on a specific task and less receptive to ads, merchandising and other calls to action

image

šŸ¤”Ā At worst, they can compete so much with suggested results that users don’t understand what’s happening

image
‣
Avoid showing categories instead of search terms
šŸ”Ž
Search suggestions are intended to provide more granular, focused results. But category suggestions go wider than the search term if they’re not scoped to ā€œkeyword-within-category.ā€ This means search results will actually be less relevant to the user’s intent

šŸ‘—Ā Here you see a specific term ā€œslip dressā€ suggesting broader categories. None of the suggestions are search terms, and none match the contextual keyword ā€œslipā€

image

āœ‚ļøĀ Here it’s unclear whether results are for search terms or categories — they sure look like categories due to the Capitalization

image
‣
Always include a ā€œView Allā€ link!
šŸ”Ž
Without a View All link, your product hits look like all you’ve got!
image
image
‣
Avoid pill-style chips for list items

šŸ˜‘Ā Chip-style links are popular but muuuuuch harder to read due to lower-contrast type-to-background and ragged alignment

image

šŸ˜‘Ā Horizontal aligment is also harder to scan and requires a scrolling action. Is it ironic that eye-care brands make autosuggestions so hard to read?

image
‣
Don’t suggest everything BUT search terms

šŸ˜‘Ā Remember, autosuggestion began as autocompletion of search terms to help users hit the most relevant set of results faster. Make sure you stay true to the spirit of the search widget — give customers search term suggestions, and prioritize them above other suggestion types

image
‣
Avoid displaying the search term on the submit button

😬 I admit this is a clever idea, but it falls apart when queries get long

image
‣
Don’t force your customer to select a suggestion (aka ā€œno Submit buttonā€)

😫 This merchant forgot the Go / Search / Submit / See results button, meaning customers must select a matching product hit. This is unexpected and confusing to customers, and doesn’t enable them to browse results together

image
‣
Avoid semi-opaque dropdowns

😫 It’s just harder to read — especially when hero banners are dark

image

Back to Site search ideas

šŸ‘‰Ā Follow on LinkedIn for daily ideas šŸ’”