Multilingual websites
Every language is a page,not a plugin.
A second language is usually bolted on: a translation layer over pages that were never meant to have one, a menu that stays English, a cookie notice in German on the Polish page. In castomUI language is a property of the page, the block and the menu from the start, so each version is a real page you can open, check and fix.
Switch it on,
then set it where it matters.
Turn on the multilingual switch in project settings. From then on every page has a language, every block can have its own, and menus are made per language. The page tree shows a language flag beside each page, so a missing translation is visible rather than discovered.
The short strings that do not belong to any page — "Read more", "Send", "Opening hours" — go into dictionaries and phrases: named keys with default text and a dictionary per language, used in templates. Change a phrase once and every page in that language follows.
Clone and translate.
Clone and translate a page into a target language, fully or shallowly, with the model you choose — DeepL when speed matters, an LLM when tone does. Blocks translate the same way, with or without a clone, and so do menus. See AI generation.
Content from datasets translates through translatable fields, so a product or a team member has a name per language without a second record.
Each language version keeps its own URL, canonical address and META, which gives you the separate, clearly addressed pages that hreflang annotations expect. Add those annotations in the head where you need them.
- ENHomeSource language. Written by hand.
- PLStrona głównaCloned and translated with DeepL, then read by a person.
- DEStartseiteTranslated with an LLM for a warmer tone.
- ·Dictionary"Book a visit" key, three phrases, used in the template.
- ·MenusMain menu cloned and translated per language.
- ·PublishersGerman site to its own target, limited to DE.
Three languagesOne project
Same city,
several languages on the street signs.
Publishing by language
One project,
one or many sites.
All languages together
Publish the whole project to cstmui.com or your domain, every language under its own paths.
One language per target
A custom publisher can be limited to a single language, for a separate domain per market. See publishing.
META per language
Generate META for all pages, then check each language's titles in the META table. See SEO and migration.
Which plan
Regular, €100 a month, includes multilingual pages, blocks and menus, dictionaries, and translation with DeepL or LLMs. PRO at €300 adds translatable dataset fields and custom publishers, which is what a separate domain per language needs. Compare plans.
Questions
Is machine translation good enough to publish?
Often close. Have somebody who reads the language check it before the page leaves draft — that is what the draft flag is for.
Does a translation update when the source page changes?
No. A translated page is its own page. Translate the changed block again when the source moves on.
Does castomUI add hreflang tags for me?
castomUI gives each language its own URL and canonical; add hreflang in the page or project head code where you want it.
Linguistic hazard: German buttons are roughly a third longer than English ones. Test the menu in German first and the other languages will fit.
Your website next.
Start it today.
Open the editor, describe the website, and publish the first version to a cstmui.com address.
Open castomUI See pricing