Grab your phone, open your store and type "hik" into the search bar. If nothing happens until you have typed "women's hiking boots" in full and pressed Enter, your visitors are going through exactly the same thing.
Something important happens between the first letter and the moment the search is submitted: it is when purchase intent is at its clearest and patience at its shortest. Autocomplete is there so you don't waste those few seconds.
- Autocomplete shows suggestions while the visitor types: queries, categories and, in its useful form, products with a photo and a price.
- It converts when it shows products, tolerates typos, ranks by relevance rather than alphabetically and learns from real searches.
- It has to respond in under one second: beyond that, visitors lose their train of thought (Nielsen Norman Group).
- Badly tuned, it does more harm than no autocomplete at all: by the third letter, it shows that the site doesn't understand.
- Measure it with three signals: clicks on suggestions, zero-result searches, time to the product click.
Autocomplete, autosuggest, instant search: three different building blocks
The three terms get mixed up in quotes and plugin descriptions all the time. The distinction is simple, though, and it keeps you from buying one building block while thinking you are buying another.
| Building block | What it shows | Example |
|---|---|---|
| Autocomplete (strictly speaking) | The end of the word being typed | "guit" becomes "guitar" |
| Autosuggest | Full queries, categories, sometimes products | "electric guitar", "Electric guitars", three models with photos |
| Instant search | The full list of results, without reloading the page | The product grid updates as the visitor types |
In practice, the first two blend together under the name "autocomplete", and the enriched version is the one that matters: a dropdown that shows, after a few letters, products with a photo and a price, relevant categories and sometimes the most frequent searches of the moment.
Instant search often works alongside it, but it is a different building block. This article focuses on autocomplete, the one at play in the very first seconds.
Why it all happens before the Enter key
A visitor who starts typing has already made a decision: they no longer want to browse menus, they want to be shown. And they are not alone. According to the Baymard Institute (2026), nearly one user in two prefers search over navigation to find a product.
Every letter typed without visual feedback adds a doubt: does this site even sell what I'm looking for? Seeing relevant products appear from the third letter removes that doubt. The site has understood, the catalog exists, the search will lead somewhere.
Around 70% of e-commerce traffic comes from mobile. On a phone keyboard, every clickable suggestion saves several keystrokes, and every typo is more likely.
Autocomplete also plays a corrective role. A typo caught and fixed in the suggestions keeps the visitor away from a zero-results page, the moment when even the most determined shopper leaves thinking you don't carry the product.
Imagine a shopper looking for "high-top sneakers" on mobile who types "sneakres". Without typo-tolerant autocomplete, she submits, lands on zero results and has to type everything again. With it, the menu shows "high-top sneakers" and two models from "snea": one tap, and she is on the product page.
The 4 ingredients of autocomplete that converts
Four things separate autocomplete that genuinely helps from a field that completes words at random. The diagram below shows where each one sits in the menu.
1. Visual suggestions, not just text
A list of plain-text keywords forces the visitor to guess what lies behind each suggestion. Showing the product itself, with its photo, name and price, removes the guesswork: the visitor sees the item before even reaching a results page.
A visitor types "electric gu". The menu shows three models with photo and price, plus the "Electric guitars" category. They click straight on the model they want, without ever seeing a results list: one click fewer between intent and product page.
2. Typo tolerance from the first keystroke
Most out-of-the-box engines only suggest what starts exactly with the letters typed. A typo at the very start of a word ("giutar" instead of "guitar") is enough to empty the menu, which is precisely where the visitor needs help.
Typo-tolerant autocomplete shows the right suggestions despite a swapped or missing letter, without waiting for visitors to correct themselves. For vocabulary gaps ("hoodie" versus "hooded sweatshirt"), your synonyms take over.
3. Ranking by relevance and popularity, not alphabetical order
Sorting suggestions alphabetically treats every query the same way, regardless of what visitors actually look for. An engine that learns from past searches puts first the queries and products that matter for your store, not just the ones whose name starts with the right letters.
In practice, autocomplete that learns looks different on day one and six months later. Static autocomplete, on the other hand, puts "amp" at the top because "a" comes before "g".
4. Something useful on an empty or very short field
A visitor who clicks in the bar without knowing what to type, or who has typed a single letter, shouldn't face an incoherent menu. Two sensible options: show nothing until the query makes sense, or display the most frequent searches and a few key categories.
The second turns the field into an entry point to the catalog, useful for visitors who arrive without a precise idea. The worst option is a menu full of unrelated products after a single letter.
For your popular searches, start from real data rather than gut feeling. The site search terms report in GA4 gives you the list in a few minutes: our GA4 tutorial explains how to get it.
Speed: under one second or nothing
A suggestion that arrives after the visitor has finished typing is useless. The reference thresholds come from Nielsen Norman Group (1993), and they are still the ones used today:
- 0.1 second: the response feels instant, as if the visitor were handling the menu directly.
- 1 second: the limit beyond which the train of thought breaks. The visitor notices the wait.
- 10 seconds: the limit of attention. Autocomplete should never get anywhere near it.
The technical catch is that you can't query the engine on every keystroke either. A fast typist would fire a dozen requests and only see the last one. The usual fix is a short wait (the debounce): the engine is only called once typing pauses for a fraction of a second (150 milliseconds at Vectail for suggestions).
Noticeable latency shows immediately: letters appear before suggestions, and the menu "jumps" once typing stops. Test on a phone over 4G, not just on an office computer plugged into fiber.
The mistakes of out-of-the-box engines
These mistakes show up on most engines that ship with e-commerce platforms. A single one is enough to make autocomplete counterproductive: by the third letter, it tells visitors the site doesn't understand their request, before they have even finished typing it.
- Show products with photo and price
- Fix typos from the first letters
- Rank by relevance and real popularity
- Let the engine learn from searches
- Respond in under one second, mobile included
- A list of plain-text words
- Strict matching on the start of the word
- Alphabetical ranking
- A menu that is the same on day one and a year later
- Suggestions that arrive after typing
Test your autocomplete in 5 minutes
You don't need an audit to know where you stand. Grab your phone, open your store and type the queries below, replacing the examples with products from your catalog.
For each one, note three things: does the menu appear, does it show products, and does it arrive before you finish typing. A "no" on the typo at the start of the word or on mobile speed is the one that costs the most sales.
Measuring the impact of your autocomplete
Autocomplete lends itself well to measurement, as long as you track the right signals instead of judging it by eye. These three metrics live in the same tools as your regular search queries.
- Suggestion click-through rate. Out of all searches, what share ends with a click in the menu rather than submitting the full text? A high rate means autocomplete is anticipating visitors' intent.
- Zero-result search rate. If autocomplete does its job, it drops over time: fewer visitors get to the end of a misspelled query without being caught along the way.
- Time from first keystroke to product click. The shorter it is, the more autocomplete actually shortens the path to purchase.
Imagine a store that logs 8,000 searches a month. Before working on its autocomplete, 400 end with a click in the menu, or 5%. Three months later, there are 2,000: 2,000 ÷ 8,000 = 25%. If the zero-result rate dropped at the same time, the improvement is real, not just curiosity clicks.
What Vectail's autocomplete does (and what it doesn't)
Since we're talking settings, here are ours, without any polish. Vectail runs on Google Vertex AI Search for Retail and displays its results in a search window that opens on your site. With us, the two building blocks are separate: query suggestions come from autocomplete, products from instant search.
- Query suggestions from 2 characters, requested 150 milliseconds after the last keystroke.
- Products with photo and price from 3 characters, displayed by the instant search of the same window (not by query suggestions), with typo tolerance.
- No calls while deleting: when a visitor erases their query letter by letter, suggestions are hidden and come back with the next typed character.
- Automatic learning: Vertex AI auto-learning is switched on at setup, free of charge. Suggestions get closer to what your customers actually type.
Two things to know before choosing. Displaying query suggestions in the widget is an option: each suggestion request uses credits from your plan, which is why it is enabled on request (the learning itself costs nothing). And Vectail doesn't show popular searches on an empty field: until something is typed, the menu stays closed.
If your catalog runs on Merchant Center, Vectail imports it directly, with no second catalog to maintain. For the placement and size of the bar itself, see our search bar guide, and for phone-specific constraints, our article on mobile search.
Your checklist
- The menu shows products with photo and price, not just words
- A typo at the start of a word ("giutar") still returns suggestions
- Suggestions are ranked by relevance, not alphabetically
- The engine learns from your visitors' real searches
- The empty field shows nothing incoherent (nothing, or popular searches)
- Suggestions arrive in under one second on a phone over 4G
- The engine isn't called on every keystroke (debounce)
- Suggestion click-through rate and zero-result rate tracked every month
Frequently asked questions
What is the difference between autocomplete and instant search?
Autocomplete offers to complete what the visitor is typing: queries, categories and sometimes products, in a menu below the field. Instant search displays the full list of results without reloading the page. The two often work together, but they are separate building blocks.
After how many characters should suggestions appear?
A common setting is to show query suggestions from 2 characters, then products from 3, once the query becomes specific enough. Below that, results are too vague to help. On an empty field, it is better to show nothing or to display popular searches.
How do I know if my autocomplete is working?
Track three signals: the share of searches that end with a click on a suggestion, the trend in your zero-result rate, and the time between the first keystroke and the click on a product. Add a manual test: a typo at the start of a word, a plural, a brand name on its own, a query on mobile.
Does a small catalog need autocomplete?
Yes, especially on mobile, where typing a full query is tedious. With a few dozen products, showing the matching products directly in the menu is often enough. The bigger the catalog, the more query and category suggestions are worth.
Sources
- Baymard Institute, Ecommerce Search UX Best Practices, 2026 (share of users who prefer search).
- Nielsen Norman Group, J. Nielsen, Response Times: The 3 Important Limits, 1993 (0.1, 1 and 10 second thresholds).
- Contentsquare, Digital Experience Benchmark, 2025 (share of e-commerce traffic on mobile).
Your products shown from the first letters, not just words
Vectail shows your products with photo and price from the first letters thanks to its instant search, tolerates typos and learns from every search. One line of code, powered by Google Vertex AI.
Start free - 14 days, no credit card