The new SCAYLE search
Functionality of the V2 search endpoints
- Search
- Business
Pia Nadolny
Junior Business Consultant
This guide focuses on the SCAYLE Search configuration in the SCAYLE Panel. To gain a better understanding of the search logic and technical implementation, refer to the Developer Guide.
The search consists of two main endpoints, the /v2/suggestions
and the /v2/resolve
endpoint.
While they have many similarities, there are also some differences between the two:
/v2/suggestions | /v2/resolve | |
---|---|---|
Use case | Giving the user suggestions as he types in the search bar | Bringing the user to the top result once he presses enter |
Results | Many results user can choose from | Only one result |
As a response to a search term, they may return categories, products, or navigation items.
Both endpoints rely on a good configuration to yield satisfying results.
On this page, you will find out how to define your SCAYLE Search in order to get optimal results.
SCAYLE offers a search module that allows you to adjust the output of frontend search results.
You can access the search configuration options in the Shops area through Shops > Shop Name > Storefront > Search
.
You can configure the following settings:
Any changes to the initial configuration will be visible with a time delay of up to two hours.
As our search is category-based, you'll need to manually set the visibility of pages that you want to be searchable, such as Shipping, FAQs, Article pages or SEO pages to include them in the search results.
Shops > Shop > Storefront > Navigation
.Customers can now retrieve this page by entering relevant keywords or synonyms in the search bar. Synonyms have to be added first. Find out how to add them in the section Navigation Synonyms.
SCAYLE uses attribute groups to define search result logic. Searchable Attributes only affect the Text Search of the Storefront API.
Understanding which attribute groups make for an excellent searchable attribute and which don't is essential. When an attribute group is set as searchable, the search will try to match against any of the words in the assigned attribute.
A good candidate for a searchable attribute is an attribute group with short values that users often search for. Here are some common examples:
A wrong candidate for a searchable attribute is an attribute group with long descriptions, full of words that will result in unexpected search outcomes. Here are some common examples:
The reason these are bad is that if any word in the user's search matches any word in the attribute value, the product will be returned in the search results.
As an example, if a user searches for "tongue brush", the search will also return products with the 3rd attribute value in the above example, as it includes the word "tongue". Even though the product has nothing to do with the user's search term.
Another common issue is when a searchable attribute includes unnecessary terms or search-unfriendly terms. Here are some examples:
These examples have a high chance of showing up in completely irrelevant searches.
As an example, if someone searches for "broom", products with the material "broom plant" will show up, regardless of whether they're brooms or not. Or if someone searches for "off season", then products with the color "off white" will show up.
It is strongly recommended that the searchable attribute groups have very straightforward, simple and commonly searched terms as values.
Use drag and drop to assign priorities to these groups to influence their order in the search results. Attribute groups with a higher priority affect the search results order significantly more than those with a lower priority.
The Synonyms area bundles various options for managing synonyms. Synonyms play an essential role in the output of search results, as the system can recognize which terms are considered equivalent. Use the tabs to define synonyms for single search words or combinations of words, categories, and attributes.
We support defining synonyms for your existing categories. The category synonyms work like alternative names for the specified category, as they are stored alongside the normal name of the category.
As a general guideline, we recommend adding category synonyms to applicable categories instead of word synonyms. Adding category synonyms will work seamlessly with other endpoint functionalities, such as autocomplete and typo tolerance.
As an example, if a category is called "Shirts", but users search for "T-Shirt" then this would be a good candidate to add "T-Shirt" as a synonym.
On our search endpoints, the category "Shirts" would then be returned when the user types in "Shirts" or "T-Shirt".
Shops > Shop Name > Storefront > Search > Synonyms.
CATEGORIES tab.
To find out how to add category synonyms in bulk, please see the documentation on imports & jobs in the User Guide.
We support defining synonyms for your existing attributes. Similar to the category synonyms, these are alternative names for your specified attribute and are stored alongside the normal name of the attribute.
As an example, if an attribute group "color" has an attribute "purple", but users search "lila" then this would be a good candidate to add "lila" as a synonym.
For attributes to be used for matching search terms to products, you must add these attributes to the Search Result Logic first.
Shops > Shop Name > Storefront > Search > Synonyms.
ATTRIBUTES
tab.To find out how to add attribute group synonyms in bulk, please see the documentation on imports & jobs in the User Guide.
Word Synonyms allow you to dynamically replace certain words and combinations of words from the user's search term.
Since word synonyms work on the search term itself, this means Typo Tolerance and Autocomplete are not supported.
Word synonyms are synonyms that apply across our search endpoints suggestions
and resolve
, but also work for product search through the products endpoint, which can be used as a fallback, when no matching category or navigation item is found.
The general guideline is to put existing categories, product names and attributes on the left and terms that users might search for (but don't have a matching category/product name/attribute) on the right.
Word synonyms work best for cases where a user searches for a single word, which is a combined term of an existing attribute and an existing category. This is quite common in some languages, like German.
As an example, if a user searches "leinenhose", but "leinen" is an attribute and "hose" is a category, then this is a good candidate for adding a word synonym, where "leinenhose" (the right term) would get mapped into "leinen hose" (the left term).
Word synonyms are also good candidates for improving search on product names.
As an example, the product is called "air max", but the users search for "airmax". This is then a good candidate for a word synonym, where "airmax" (right term) would get mapped into "air max" (left term).
Shops > Shop Name > Storefront > Search > Synonyms.
WORDS
tab.When searching, the searched terms on the right side (in the screenshot below) will be linked with the term on the left.
As an example, if there is a synonym set up for "denim => jeans" and the user searches for "denim", in the background we will search for "jeans".
Add a synonym of a navigation item at a local shop level.
Navigation item must be configured as Included in Search.
In the case of navigation items, there may be a lot of use cases for different wording. While a product usually has a given name, a page can be named in very different ways from website to website. Navigation item synonyms allow for you to cover those different wordings.
When you want your users to be able to search for navigation items, make sure to include some synonyms as well. Imagine you have a page called "Shipping", that informs user about expected delivery timelines, delivery cost, etc.
Once you define that navigation item as searchable, consider what synonyms users could also be searching for. An example for a good synonym in this use case would be "Delivery".
If you have an FAQ page, consider adding "Frequently Asked Questions" as a synonym.
Shops > Country > Storefront > Search > Synonyms
.For our previous endpoints /v1/typeahead
and /v1/resolve
it was allowed to configure the typo tolerance we apply; however, we recommend leaving this with AUTO
.
In the new V2 endpoints, /v2/suggestions
and /v2/resolve
, the setting is not considered anymore. The typo tolerance settings are explained more in detail in the Developer Guide.
In the Words area, you define "stop words". Stop words are those words that occur particularly frequently but do not have much meaning or are used as filler words (for example, "the", "that", "everything", "at", "on" or "in"). By excluding stop words from search queries, the quality of generated search results is increased.
When you exclude a specific category from the search results, they will not be returned through any of our search endpoints. You may use this functionality if, for example, you have a category for VIP products that should not be visible to every user of your shop.
Invisible or inactive shop categories are never included in the search so this option is hidden for them.
Excluding a product from search results will only affect our search endpoints /v2/resolve
and /v2/suggestions
.
Shops > Shop Name > Products > Categories.
GENERAL INFO > Category Configuration
, select the Exclude from Search checkbox.Result: Once indexers have run, this shop category will not be considered for the search in the Shop Storefront anymore.
When you exclude a specific product from the search results, it will not be returned through any of our search endpoints. You may use this functionality if, for example, you have some specific VIP products that should not be visible to every user of your shop.
Excluding a product from search results will only affect our search endpoints /v2/resolve
and /v2/suggestions
. If you want to have these products excluded from /v1/products
, too, you will have to adapt your request as described in the Developer Guide.
Shops > Shop Name > Products
and select the product you want to exclude from the search.Product > Product Attributes
, set the isExcludedFromSearch dropdown to true
.Result: Once indexers have run, this product will not be considered for the search in the Shop Storefront anymore.
The new SCAYLE search
Pia Nadolny
Junior Business Consultant
Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Answer:
@scayle/storefront-api
NPM package.Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Answer:
Leinen Hose
<= Leinenhose
Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Answer:
Question:
Brands/AboutYou
, rather than for Men/Brands/AboutYou
and Women/Brands/AboutYou
?Answer:
Brands/AboutYou
and only set the synonym here, the gender-specific brands will not be suggested.Question:
Answer:
Question:
Answer:
Question:
Answer: