Autocomplete design and behavior – UX best practices

Autocomplete is implemented on your website by your development team or implementation partner. The way it’s set up plays a key role in how easily shoppers can find products. In this guide, you’ll find best practices to help you design a smooth and effective search and autocomplete experience with Voyado Product Discovery.

Purpose

Ensure the search feature is easy to find, easy to use, and sets clear expectations for the shopper.

Visibility & placement

  • Place search in a highly visible, persistent position
  • Desktop: Visible search field in header
  • Mobile: Visible search icon that expands into input field

Principle: Search must never be hidden or hard to find

Input field design

  • Desktop: Use a wide input field to support longer queries
  • Mobile: Expand input to full width on focus

1-2 Input Field Design.jpg

Placeholder text

  • Use clear guidance:
    • “Search for products, brands or inspiration”
  • Avoid vague placeholders like “Search”

1-3 Placeholder Text.jpg

Visible search queries

  • Keep the user’s query visible after search

Principle: Users must be able to refine queries without retyping

Trigger

The shopper taps or clicks into the search field

Show a structured empty state

Never show an empty dropdown. Instead, you can make use of Recent or Trending searches.

A. Recent searches (Product Discovery feature)

  • Display previously searched queries
  • Include:
    • Clear all option (mandatory)
    • Optional: remove individual items

Principle: Users must be able to fully control and clear search history

B. Trending / Popular searches (Product Discovery feature)

  • Display high-performing or trending queries
  • Use the built-in Trending searches feature in Product Discovery

Principle: Guide users who don’t know what to search for

2-1 Show a Structured Empty State.jpg

Design & behavior rules

  • Clearly separate sections:
    • “Recent searches”
    • “Trending searches”
  • Limit each section to 5–10 items
  • Clicking any item: → Executes search immediately

2-2 Design Rules.jpg

Autocomplete results

Layout & styling

Grouping of suggestion types

Group autocomplete into:

  1. Search suggestions (queries)
  2. Product suggestions
  3. (Optional) Content suggestions

Principle: Each group must be visually distinct

3-1-1 Grouping of Suggestion Types.jpg

Visual separation

Use:

  • Section headers (e.g. “Suggestions”, “Products”)
  • Spacing or dividers

Principle: Users must be able to scan groups instantly

Number of suggestions

  • Queries: 5–10 items
  • Products: 3–8 items
  • Keep total visible items under ~15

Principle: Do not overload users with too many options

3-1-3 Number of Suggestions.jpg

Product suggestion design

Each product must include:

  • Image
  • Title
  • Price
  • (Optional: brand)

Principle: Product suggestions must be visually scannable and informative

3-1-4 Product Suggestion Design.jpg

Highlighting (Critical)

Rule:

Highlight the autocompleted (predicted) part of the query

Example:

dress → dress black

dress → dress long sleeve

Why highlighting is important:

  • Enables fast comparison between suggestions
  • Improves scanning speed
  • Makes system suggestions explicit

Rule of thumb: Do NOT highlight typed text: users already know what they typed

3-1-5 Highlighting (Critical).jpg

Interaction behavior

Allow free search submission

Key principle

Users must always have a clear, explicit way to execute their query without selecting a suggestion

Desktop

  • Support submitting the query via Enter key (mandatory)
  • Provide a visible submit option in the UI

Best practice:

  • Include a “Search for ‘[query]’” option as the last item in the autocomplete list

Example:

Search for “dress”

Principle: Users must always have a clickable way to submit without selecting a suggestion

Mobile

  • Use a search-optimized keyboard (Enter key labeled “Search”)
  • Support submission via:
    • Keyboard “Search” button (primary)
    • Visible submit option in the UI (required)

Best practice:

  • Include a “Search for ‘[query]’” option in the autocomplete list
  • Optionally include a submit button/icon inside the input field

3.2.1 Allow Free Search Submission.jpg

Clicking suggestions

  • Query → navigate to search results
  • Product → navigate to product detail page

Keyboard navigation (Desktop)

  • ↑ ↓ Navigate between suggestions
  • Enter (after navigation) → navigate to highlighted suggestion
  • Enter (no navigation) → Submit typed query
  • ESC → Close autocomplete

Principle: Navigation must match the vertical structure of the UI

3-2-3 Keyboard Navigation (Desktop).jpg

Mobile interaction

  • Use large tap targets
  • Ensure clear spacing between items
  • Avoid dense layouts

Principle: Prevent misclicks and frustration

Was this article helpful?

/