A multilingual website:three languages in the plan,each one with its own copy.
A site on the platform runs in three languages at once: Russian, Kazakh and English. All three are already in the plan, with nothing extra to pay per language. Each version holds its own content: headings, service descriptions, button labels, questions and answers. Russian copy is never quietly served as a translation. The language switcher appears in the header by itself the moment there is more than one language.
3
site languages: Russian, Kazakh and English
0 ₸
extra per language — multilingual is in every plan
kz → kk
the internal locale code, and the code that goes into hreflang
0
machine translations layered over the main language
What "a site in three languages" actually means
Multilingual sites break in an unexpected place. It is almost never the layout — it is whose text a visitor reads after switching to Kazakh, and whether a search engine understands that these are the same page.
Three languages, 35 sections and no surcharge for localisation
3
languages already in the plan
Russian, Kazakh and English come with the subscription from 12,800 ₸ a month — the multilingual module is not bought separately
35
kinds of section in the builder catalogue
Text in any of them is authored separately for each language
19
tools the AI assistant has
One of them shows where a translation is missing and drafts it. The AI assistant is included in the subscription
2
languages — the minimum for a switcher
On a single-language site the header control is not rendered at all
Five steps, and the technical one takes a minute
A language switches on in a minute, the header switcher appears by itself, and the platform writes hreflang without you — the sitemap is assembled by the SEO Advanced module, 4,900 ₸ a month. All that is left is the text. That is why the Kazakh version reads as written rather than translated.
You enable the language in the admin panel
Language versions are a site setting, not a support ticket. You mark which languages you need and which one is the main one.
A second language version exists
The switcher appears in the header
It arrives with the second language and disappears if only one language is left. There is nothing to enable or configure separately.
Visitors can switch
You fill in the text — yourself or with the assistant
The assistant drafts translations taking into account what is already translated, and before you confirm it shows, per language, what is missing and where a row exists but holds Russian. You apply it.
Real Kazakh text in the fields
You check where the main language still shows
The catalogue, the menu, the buttons and the footer are walked separately — those are the places a foreign language survives longest and a customer notices first.
The list of untranslated places approaches zero
You publish, and search engines get the link between versions
Once published, each language version references the others. Nothing extra has to be written by hand, and all of them enter the sitemap together with the SEO Advanced module, 4,900 ₸ a month.
Three addresses that reference each other
What is authored separately per language
What the platform handles, and what an evening covers
The platform closes the entire technical half of a multilingual site with no configuration — including the parts other platforms bill a contractor for. What remains is the editorial half, and it has an assistant in the same admin panel.
The platform does this itself
Everything that needs no knowledge of your business
- Puts the language code into the page markup and into hreflang
- Points x-default at your main language rather than at Russian out of habit
- Keeps the main language on the short address and the rest behind a language prefix
- Shows the header switcher as soon as there are two languages
- Remembers the chosen language in the visitor's browser
- Lists every language version in the sitemap, each referencing the others — in SEO Advanced, 4,900 ₸/mo
- Serves the main language when a translation is missing, instead of an empty page
Yours to do — and not alone
The editorial half, with an AI assistant in the same admin panel
- Your own Kazakh copy — the words your customers use for your service
- A per-language draft prepared by the AI assistant, which is included in the subscription
- The list of untranslated places is compiled for you — no manual walk of the site
- Catalogue names and descriptions are edited where you entered them
- Change the Russian text and the assistant shows which translations went stale
- Three languages from the start: Russian, Kazakh and English, all in the plan
Machine translation over Russian gives you a site that looks Kazakh right up to the first sentence somebody reads.
A machine will render "Book now" and "Send an enquiry" identically and almost correctly. It will not name your service the way your customers name it, and it will not grasp that half of the Kazakh version should be different copy rather than a translation. That is why each locale here owns its own record instead of a layer on top of the main one: you get a Kazakh version you can show a customer, not a machine translation they close on the first paragraph.
Three ways to put a site into Kazakh — and what each one costs
One column tells the story: here three languages are already in the plan from 12,800 ₸ a month, and the technical side runs with no configuration. A widget translates the page inside someone else's browser; two separate sites mean two subscriptions and two places to remember to fix the same thing.
| INIT | Auto-translate widget | A separate site per language | |
|---|---|---|---|
| Its own text for each language | Yes, in one admin panel | Yes, but across two separate sites | |
| Cost of all three languages | In the plan from 12 800 ₸/month | A separate service subscription | A second subscription and second hosting |
| One site and one admin panel | |||
| hreflang between versions, with no setup | |||
| x-default points at your main language, even when it is Kazakh | Configured by hand | ||
| A translation draft is prepared in the admin panel and waits for your approval | |||
| The platform lists the untranslated places for you | |||
| A section edit applies to every language at once | Yes, but the text stays machine-made | ||
| The language version is indexed as its own page | Yes, with the versions already linked | Yes, but you link the versions by hand | |
| Enquiries from every language land on one board |
"Auto-translate widget" here means the tools that translate the page inside the visitor's browser; "a separate site" means two independent copies that then live their own lives.
What actually reaches the browser and the search engine
This section matters only if you or your contractor check such things by hand. It changes nothing about how the site behaves — the platform does all of it without configuration.
Addresses and markup
Behaviour
What people ask about languages
Short and specific: the main language, the price, the assistant and the markup.
Turn on the Kazakh version and watch it appear in the header
A 3-day trial, no card required. A technical address is issued immediately — enough to enable the Kazakh version, see the switcher in the header and check hreflang against your own content. After that a site in all three languages runs from 12,800 ₸ a month.
- A your-name.shardit.app address is issued immediately
- All three languages are available from day one of the trial
- Multilingual is included in the plan — nothing extra per language
- Enquiries from any language version land on one board
Read next
Neighbouring sections that answer the question this one raises.
