Search that speaks
your customers' language
Shoppers type without accents, in the wrong keyboard layout, in Greeklish, with a typo, and with English brand names inside a Cyrillic sentence. SearchX is built for all of it.
Start Free TrialEnglish
The SDK's default language and the fallback behind every other locale — and still full of ways a shopper's spelling misses your catalogue.
Spanish
One catalogue, two continents, and a keyboard that quietly drops every accent.
Italian
A language where the accent falls on the final vowel, and the final vowel is the first thing a keyboard drops.
Greek
Greek shoppers move between Greek, Greeklish and English inside a single query.
Bulgarian
A Cyrillic catalogue, Latin brand names, and shoppers who type both in the same query.
Romanian
Romanians rarely type diacritics. Your catalogue is full of them. That mismatch is where results go missing.
What makes a search engine multilingual
Script-native indexing
Greek, Latin and Cyrillic live in the same index. Accents, diacritics and letter case fold away before matching, so the way a shopper types is no longer the reason they lose the result.
Built for how people type
Greeklish, wrong keyboard layouts, missing accents and one- to two-character typos are handled by the engine itself — not by a synonym list you have to maintain.
A widget in their language
Six translated interfaces ship with the SDK and load from our CDN at runtime, so extra languages cost nothing in bundle size. Any other language works through a custom locale file.
Language coverage at a glance
The search engine and the widget interface are separate questions. The table below covers both.
| Language | Code | Script | Widget interface |
|---|---|---|---|
| English | en | Latin | Bundled with the SDK |
| Spanish | es | Latin | Built in |
| Italian | it | Latin | Built in |
| Greek | el | Greek | Built in |
| Bulgarian | bg | Cyrillic | Built in |
| Romanian | ro | Latin | Built in |
Bundled languages load with the SDK; the rest are fetched from our CDN the first time they are needed.
Need a language that isn't listed?
Coverage of your language is a question about the interface, not the index — the engine already handles any Latin, Greek or Cyrillic catalogue. Point customLocaleUrl at your own JSON file and the widget renders in whatever language you supply, with English filling any key you leave out.
Read the localization docsRight-to-left languages such as Arabic and Hebrew are on our roadmap and not supported yet.