Search (Frontend)

Search Features

  • Product captions, keywords, manufacturer and category names are searchable
  • Search results automatically weighted
  • Partial terms also lead to search results
  • Top-performing search engine. Through indexing and caching, high search performance is realised
  • In-house development, no additional third party costs
  • Search suggestions available in the storefront

If you're still looking for even more capabilities, be sure to read more about our premium plugin called Smart Search. You can test and purchase this plugin directly in our store.

General Settings

In the general settings (default settings), you can adjust the search configuration. Here you can optimize search results based on values entered.

The general settings are displayed in the screenshot below:

Explanation of General Settings

  • Minimum search term length
    The values entered dictate how the results are displayed in the frontend. For example, with a value of 3, search suggestions are given after 3 or more characters are entered (the value should not be set at less than 3).
  • Blacklist for keywords:
    All values entered here will not be considered in searches.
  • Number of live search results:
    The number of search results suggested. Example: If a value of 6 is entered, then 6 item suggestions are generated, as seen below.
  • Factor for accurate hits:
    Multiplication value for calculating the scoring of exact matches based on the relevance setting entered. Example: If the client enters the word "photo", and this term is consistent with the results, the entered value for the factor of exact matches is multiplied by the relevance setting.
  • Factor for inaccurate hits:
    Multiplication value for calculating the scoring of spelling mistakes based on the relevance setting. This setting is designed for fault-tolerant searches. Results may be displayed even though the search term does not match the keywords. Example: keyword: iPat, result: iPad. This is only included with the Smart Search Premium .
  • Nevertheless, if your search does not return any results, you can adjust the values accordingly.

  • Minimum relevance for top items (%):
  • The value entered here defines the condition for the consistency of the results of a search, with the highest scoring results displayed first. Example: If a value of 80 is entered, the results must be 80% consistent or else they are excluded.
search querycomparison keywordresult
salmonsalmon === salmon100% Hit
  • Maximum distance for partial names (%)
    This value defines the number of search results returned which contain partial matches. Example: If a value of 60 is entered, this corresponds to a 60% consistency of the search term with the results.
search querycomparison keywordresult
salmonsalmon==? salmon fillet50% = No hit, because value smaller than maximum distance.
salmosalmo ==? salmon83% = Hit, because value is greater than maximum distance.
  • Factor for partial hits:
    Multiplication value for calculating the scoring of partial matches based on the relevance setting. Example: The customers searches for "photo", and so all results containing the term "photo" are multiplied by the relevance setting (i.e., results containing "photo album" would also be considered).
  • Selection results per page:
    Here you can choose the number of results displayed per page. You can define the distances yourself. Example: instead of 12|24|36, you could also enter 8|16|24|32.
  • Results per page:
    Here, you specify the number of results per page.
  • Use "and" search logic:
    You can define, whether the "AND" or "OR" logic will be used in searches. Thus, a more precise result can be provided because "Apple" AND "iPod" gives more precise results than "Apple" OR" "iPod".

Relevance/Fields Tab

The calculation of results is based on the search criteria set in the "Relevance / Fields" tab as well as the general settings. The higher a value is, the higher the overall scoring. The following overview shows the fields with your values:

Do not delete any fields or tables as there are dependencies between them. Changes can lead to search malfunctions.

Explanation of Relevance/Fields

  • Item keywords:
    The keywords are set in the basic information of each item. Depending on the value, you can define which keywords have relevance regarding search results.
  • Name:
    The item name is defined in the basic information of the item. You are able to set how much relevance the item name should have.
  • Category overview:
    The category heading is used when creating categories. For this field, you can also define the desired relevance regarding search results.
  • Manufacturer:
    The manufacturer name is entered as the item name when creating articles in the shop in the basic information. Again, the relevance level can be assigned.
  • Item order number:
    This is similarly managed in the basic information. You may also define how much relevance the item number has.
  • Item keyword overview:
    This setting applies only to the translation of keywords in subshops. The keywords in each subshop can be entered in the basic information by clicking on the flag of the item. Once again, a relevance value can be assigned.
  • Item name translation:
    The item name for the subshop is also defined in the basic information. Naturally, you can freely set the relevance level.

If you are working with your own items in a subshop, the setting for "AItem keyword translation" and "Item name translation" do not need to be filled out, as they are not considered.

This example shows you how to add free text fields in the frontend search.

Step 1: Add the field and the relevance

In Configuration > Basic settings > Frontend > Search > Relevance/fields (Tab) You can add a new field using the Add entrybutton. In this example, we add the free text field attr1 to the search.

  • Name: Attribute1 (You can choose the field name by yourself)
  • Relevance: 20 (Desired relevance of the field in the search)
  • Table field: attr1 (Attribute field in the database)
  • Table: s_articles_attributes
  • Do no Split: Optional.

Step 2: Clear the Cache

If you want the free text field to be available immediately in the frontend search. You must empty the cache and rebuild the search index.

Was this article helpful?