Search

Relewise supports searching in products or content. The search engine uses the same personalization features as our recommendations. Relewise is a fully fledged search engine, meaning that we support all the standard features of a search engine that can be expected today, such as facetting, sorting, and paging.

In addition, Relewise offers batching of search requests, predictive search results, automated stemming and decompounding of search terms, and a highly customizable engine for tuning and adjusting the algorithms - resulting in fast, flexible and tailor-made searches.

We support the following type of Searches

• Product Search
• Product Category Search
• Content Search
• Search Term Prediction

Implementation details for Developers

See how to create searches via the API here

Product Search

Product search is used to find products that match a given search term, or is used with a filter to show products by i.e a category or brand, or any other given product property.

Example of usage of the product search

Product Category Search

Product category search helps users find product categories that match a given search term.

Content Search

Content searches find content elements that match a given search term.

Example of usage of the content search used to find content pages

Search Term Prediction

This is used with typeahead searches to inspire users on what could be relevant search terms related to the term they have already typed into the search field. This can help the user narrow down what they are looking for. For example when searching for a towel, then relevant predictions could be a beach towel, kitchen towel, or yoga towel.

Example of usage of the search term prediction

For examples of how to implement Search Term Prediction, refer to our examples page.

Typical use case

Used in the global search field on your store to help users find relevant products, categories and/or content.

Batching Searches

Batching is an option that allows for the grouping (batching) of multiple searches into a single request. Batching ensures faster response and load times, and ensures that the result of multiple searches displayed on the same page will be delivered at the same time, thus making sure that all search-related objects display simultaneously.

Specifically, you may use SearchRequestCollection, which has the Requests property. Here, you can add a number of different SearchRequests to be served back to you in one go.

Using this method will return a ResponseCollection with a Responses collection. The index of this collection is automatically aligned with the index of the request to ensure ease of use.

Unlike batched recommendations, batched searches can return both product and content results without issue.

Search Batching Use Cases

For instance, you might want to execute both a ProductSearchRequest and a ContentSearchRequest at the same time, to present users with both product and content results to their query. Batching them ensures that the results are delivered simultaneously on the page, which makes for a better user experience.

Another use case might be to batch ProductSearchRequest with SearchTermPredictionRequest, so that your search results provide product results as well as proactive search term predictions.

The Search Live View

Batching is reflected in the Search Live View, where batched requests are displayed as a single request instead of multiple. To see if a request is batched, and to inspect the details of the batched request, you can click on the Details icon next to the request on the Live View page.

To see if a search request is batched, click the Details icon on the Live View page