Multi-language semantic search

Semantic Search identifies product types from user queries and product data for the non-English languages mentioned below. This product type information is then used to optimize recall and ranking in various ways.

1674

Languages supported

Bloomreach offers multilanguage semantic capability in the following languages:

  1. Albanian

  2. Arabic

  3. Chinese

  4. Czech

  5. Danish

  6. Dutch

  7. Estonian

  8. Finnish

  9. French

  10. German

  11. Greek

  12. Hungarian

  13. Irish

  14. Italian

  15. Japanese

  16. Korean

  17. Latvian

  18. Lithuanian

  19. Maltese

  20. Norwegian

  21. Polish

  22. Portuguese

  23. Romanian

  24. Russian

  25. Serbian

  26. Slovak

  27. Slovenian

  28. Spanish

  29. Swedish

  30. Turkish

  31. Ukrainian

For a comparison of features available in English versus non-English search, please refer to the feature support table.

📘

Support for Bulgarian and Croatian catalogs is coming soon in January 2025.

Feature access

Multi-language semantic search is generally available starting September 18th, 2024. This feature is free to access and requires no extra integration steps.

If you wish to enable query relaxation to product type:

The above applies to all non-English languages. Note that Query relaxation to brand is not supported.

Semantic search examples


These examples show what Bloomreach’s semantic engine identifies as the product type.

Arabic

Danish

Dutch

French

904

German

904

Hungarian

Italian


Norwegian

Polish


Spanish

Search ranking optimization


Multi-language semantic engine optimizes search ranking in the following way:

  1. Product types are identified from the product feed and incoming user queries in real-time.
  2. Products that match the product type from the user query are boosted in ranking.
  3. This increases relevance near the top of the result set for all queries and especially benefits cases with less user behavior data, such as torso/tail queries.

French example

For example, a user searches for “blooma barbecue”. Without semantic understanding, some of the top products include barbecue accessories like “grilles”.

1883

With semantic understanding, the product type is identified as “barbecue”, so the products of product type “barbecue” are boosted above the other products.

1814

Polish example

For example, a user searches for “koldra” (comforter). Without Semantic Search, some top products may include other products with the “comforter” term in the product title.

With Semantic Search, the product type is identified as “comforter,” and the products with the “comforter” product type are boosted in the recall.

Search recall optimization


Multi-language semantic engine optimizes search recall in the following way:

  • If no product match is found for a user query, the query is relaxed to show other products that match the identified product type.
  • This helps reduce the null search result rate, improve user experience, and increase conversions by showing related products instead of a null result.

For instance, when a user searches for "fauteuil rio" and no or fewer than three matches are found, the semantic engine identifies the product type as "fauteuil" (armchair) and expands the search to display other armchairs.

1748

📘

The API response also includes information that the query has been relaxed so it can be displayed to the end user to avoid confusion when they see related products instead of exact matches.

Handling of compound words

Your shoppers might search for queries in a compound form, which are usually non-English queries. Multi-language semantic search uses a splitter to split such compound queries to find matches. This improves the recall precision for German and Finnish compound searches.

For example, without a splitter, a German query "klavier hocker" (piano stool) won't match a product titled "deluxe klavierhocker," leading to no results. However, with a splitter, "deluxe klavierhocker" is split into "deluxe klavier hocker," allowing it to match the query "klavier hocker."

Similarly, the splitter helps match Finnish compound words. For instance, it splits "urheilukuvaaja" into "urheilu kuvaaja" to improve the search recall.


Multi-language semantic search feature support


This table compares features available in English versus non-English search.

Feature English Non-English
Automatic Query Filtering Yes No
Autosuggest - Product Suggestion Yes Yes
Autosuggest- Query suggestions Yes Yes
Autosuggest - Right-hand suggestion Yes Yes
BOPIS Yes Yes
Content Search Yes No
Dashboard rules Yes Dashboard controls will be in English but will work for all languages - synonyms, facets, redirects, ranking diagnostics, etc.
Did you mean Yes Yes (not language specific)
Dynamic grouping Yes Yes
Facet Precision - High Yes Yes
Facet Precision - Standard Yes Yes
Keyword Precision - Text Match Yes Yes
Keyword Precision - Category Yes Yes
Keyword Precision - Product type Yes Coming soon in November 2024.
Keyword Precision - LLM based Yes Coming soon.
Lookups Yes Yes
Numeric Precision Yes Yes
Partial part number search Yes Yes
Query Relaxation Yes Yes, for Query relaxation to product type. Query relaxation to brand is coming soon.
Ranking - extract product attributes Yes No
Ranking - extract product type Yes Yes
Recommendations Yes Yes
SKU Select Yes Yes
Smart Sort Yes Yes
Spellcorrect - Closest Match Yes Yes (not language specific)
Spellcorrect - Term Frequency Yes Yes (not language specific)
Synonyms - BR generated Global Yes No language-specific global synonyms
Synonyms - BR generated Site Yes Yes
Synonyms - Canonicals Yes Yes
Synonyms - User-created Yes Yes