How to build scoped search suggestions and search query corrections

You get one shot to keep shoppers on your ecommerce website with relevant search results. According to Harris Poll, 76% of online shoppers abandon a retail website after an unsuccessful search.

Therefore, it’s critical to optimize your search experience so buyers can find what they need fast. That’s the theory behind a modern search experience: Nowadays it’s not enough to simply provide a search bar that returns matching products. Your ecommerce site must include a complete set of search tools that personally guide users to the products they want.

In this blog, you’ll learn how to start improving ecommerce search by adding two common features: scoped suggestions and query corrections, also known as “Did you mean?”

Note the following examples have been tested using Elastic 8.5. 

Scoped suggestions 

One common challenge among ecommerce retailers is large product catalogs with many different categories. In this scenario, it’s difficult to parse a simple query to understand what domain or category a user might be interested in. For example, if a user searches for “flat screen” on an electronic retail store, they may see results under TVs, TV stands, computer monitors, and so on. Presenting flat screen TV stands while the user is looking for a TV might not be relevant at this stage in their buyer journey.

Scoped suggestions help your users narrow down their searches on topics they are most interested in by suggesting queries within specific categories or brands.

This is a powerful feature to help users see a refined result set quickly. Implementing scoped search suggestions using Search UI and Elastic is simple, too. The next section walks you through how to build it. 

Gather data for suggestions

As described in the example above, as users type, they’ll be presented with suggested queries and associated scopes. To build those suggestions, it’s a common practice to use analytics data to gather the most common queries and scopes they’re commonly associated with by customers.

For example, let’s say that upon reviewing the analytics data for our ecommerce website, we found that the top query is “lcd tv” and products that users click on most often are found in the category “TV & Home Theater.”

Using this data we can build a document that represents a corresponding scoped suggestion, like this: 

This document contains a query and an associated category. This can be made more complex  if required; for example, we can have a list of categories or add another scope, like “brands.”

We then create a dedicated index in Elasticsearch, in our case we name it “suggest”, to store a list of scoped suggestions that we built using the analytics data. This can be done using data transforms or using custom code, such as a Python script. The index mapping example for our index “suggest”  can be found here. 

Autocomplete suggestions

Now that we have our list of suggestions ready to be consumed, we need to add it to our search experience.

Using Search UI, it takes only a few minutes to build a search experience on top of Elastic. We can then use our newly built interface as a basis for our scoped suggestions.

Search UI uses a configuration object to tailor search to your needs. Below is a snippet of the configuration object that corresponds to the suggestion configuration. In this case, we specify the index and fields to query and the fields to return as part of the results:

Then we configure the SearchBox component to pass the category as part of the query when navigating to the search result page:

Note that we pass an AutocompleteView function to customize the autocomplete view so we can display the category alongside the suggested query. 

Below is a code snippet of the AutocompleteView function that shows how to display a query with the associated scope: 

Then on the search result page, we simply need to process the query parameters and filter the result set: 

Once we put everything together, the result looks like this:

Query corrections, aka “Did you mean?”

Shoppers can get frustrated when they miss out on seeing relevant search results due to a poor choice of query terms or a typo. To avoid returning no search results or very few, it’s a best practice to suggest a better query, commonly referred to as “Did you mean?”

There are many different ways of implementing this feature, but this is the most straightforward way to build it using Search UI and Elastic. 

Analyzing the data

The dataset we’ll use to build the “Did you mean?” feature is similar to the one we used for scoped suggestions, so you can suggest a popular query to the users in case their query didn’t return results.  

Use a similar document structure for “Did you mean?”

The key to this step is the way data is indexed in Elasticsearch. To provide relevant suggestions, you’ll need to use specific features offered by Elasticsearch such as custom analyzers.

Below are the index settings and mappings used in our example: 

Refer to the suggesters documentation for more depth on why to use specific settings and mappings to retrieve relevant suggestions. 

Preparing the search

Now that your index is ready, you can work on the search experience. To retrieve suggestions based on a query, leverage the Elasticsearch API. If you don’t want to add too much complexity on the client side, create a search template in Elasticsearch that will contain the query. Then from the client side, you just have to execute that search template:

Getting suggestions from the application

In order to get suggestions from Elasticsearch, we’re adding a backend API that the client can consume on /api/suggest. This new API calls Elasticsearch, executes the search template, and passes along the query you want suggestions for, then returns a query suggestion. The backend API allows us to reduce complexity on the front end part.

For example, if the query is “spakers,” the API will return the suggestion “speakers.” This is based on the data previously ingested that contains the most popular queries. The suggest API will return a term that is the closest syntactically to the query. 

Adding “Did you mean?” to the result page

Now we can add the “Did you mean?” feature on the front end application. For that we’re going to continue working on the same React application we used for the scoped suggestions part. 

The new API we added can be consumed from the React application and display a suggestion in case there are no results for the current query. 

The idea here is to get a suggestion for each query entered by the user. If there is no result, then the user will see a suggestion. Alternative implementations are also possible: You can display suggestions in case there are few results, or you can execute the suggestion automatically in place of a user’s query.

In our application, we have a React component named SearchResults that displays our search results. There we can add a function that fetches the suggestion from our backend API /api/suggest.

Then as the query changes, according to user refinement, you can refresh the suggestion by calling the API:

Finally, display the suggestion in case there is no result for the user query:

The final result looks like this:

Conclusion

In this blog post, you learned how to easily build “Did you mean?” and scoped suggestions features using Elastic Enterprise Search. These features can be easily integrated into your existing search experience so that your users can find what they are looking for faster. If you want to review the code used to build these examples, find it in this GitHub repo.

Delivering a modern search experience is critical for ecommerce websites and for many other use cases, such as customer support, website search, internal workplace search, and custom search applications. The steps in this blog post can be followed to accelerate building a better search experience for all of your end-users.