A multilingual website: RU, KY, EN
“Make the site in three languages” sounds simple — until the menu is translated and forms, emails, and SEO stay Russian-only. A multilingual site in Bishkek is not a language toggle. It is separate content, URLs, and a check of every lead flow.
When a second and third language are already worth it
- regional or government clients expect Kyrgyz;
- tourists, export, or investors need English;
- ads target different audiences from one landing page;
- staff and partners work in different languages inside one cabinet.
If 95% of leads come in Russian and content is small, start with RU plus one language “on demand”. Hotels, clinics, export B2B, or public tenders should plan KY/EN early — rebuilding the structure later costs more.
How to do it right
- Separate URLs:
/en/...or a subdomain — not one address that swaps text. - hreflang and canonicals so Google does not treat versions as duplicates.
- Translate more than the header: forms, errors, emails, PDFs, chatbots.
- Adapt copy, don’t machine-calque: offers and CTAs sound different in KY/EN.
- Give the admin clear per-language fields, or content will stick on RU again.
For a brochure site, a careful switcher on a corporate website or landing page is enough. For cabinets and SaaS, languages touch roles and emails — closer to a web service.
Timeline and budget
Adding a second language to a ready site often takes a few days to 2 weeks if the structure is ready. Three languages from scratch should be in the quote from day one: copy, form checks, SEO. The expensive path is translating after launch, when URLs and templates are already locked.
Typical order: list pages and flows (lead, payment, cabinet), then translation volume, then engineering. Without that list, “three languages” is always underestimated.
Common mistakes
- a toggle exists, but 404s and emails stay in Russian;
- raw machine translation in the public UI;
- one URL for every language — bad for SEO and sharing;
- no admin support: managers cannot edit KY/EN themselves;
- mixing UI language and catalog content language.
A working start: a table “page → languages → who writes”. It shows immediately whether two languages are enough or you need the full set.
Need a multilingual site?
Tell us which languages are required now and which are “for later”, and whether copy already exists. We will suggest a URL scheme and a timeline — without translating everything blindly.