Lithuanian inflects nouns through seven cases and two numbers, so the word a visitor types is usually not the form you published. Exact-match search finds nothing.
The difficulty is grammatical rather than geographic. A search box that only matches the exact characters typed is useless in a language where every noun has a dozen forms.
A visitor searching the nominative will not match text written in the genitive. Without stemming, the same word in two grammatical forms is two unrelated strings.
Č, Š, Ž, Ų and Ė have defined positions in the alphabet, and a default collation puts them somewhere else entirely — visible immediately in any A-to-Z list.
Lithuanian slugs strip diacritics. Applied inconsistently between publishing and importing, one article ends up live at two addresses.
Data stays inside the EU, close enough to Vilnius that residency and speed are not competing concerns.
Lithuania joined the eurozone in 2015. Prices held in euros avoid the rounding artefacts a conversion layer adds to a checkout total.
The signs of a foreign-built Lithuanian site are grammatical: a search that fails on a declined noun, and a sort order that puts Ž in the wrong half of the list.
The Baltics route well into central Europe, so what remains is origin distance and whether the page was cached before it was asked for.
These differ from a standard WordPress site on the same plan, and each follows from the grammar rather than from the map.
| Setting | What we do | Why |
|---|---|---|
| Search index | Stemmed for Lithuanian so declined forms match their root | Seven cases across two numbers means a noun appears in about a dozen written forms, and exact matching treats each as an unrelated word. |
| Database collation | Lithuanian-aware, with accent-tolerant comparison | Č, Š, Ž and the rest have defined alphabet positions that a default collation ignores, which is obvious in any list a reader expects in order. |
| Slug transliteration | A single rule applied identically at publish and at import | Diacritics stripped one way by the editor and another way by an importer leave the same article live at two competing URLs. |
| Data residency | EU region only, with no replication outside the bloc | For a Lithuanian audience the nearest EU region is also the fastest, so keeping data in the bloc costs nothing and simplifies every GDPR answer. |
| Currency storage | Euros held natively rather than converted on render | Lithuania has used the euro since 2015, and converting at display time introduces rounding differences on the total a customer is asked to pay. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, search that matches declined words, and EU residency at no latency cost.