Languages
A multilingual WordPress site without WPML: real addresses, thirty languages, every sentence yours to fix
A translation that only happens in the visitor's browser is in no search engine, cannot be linked to, and is gone on the next click. Here every language gets addresses of its own: /fr/chambres is a page Google knows, a page somebody can paste into an email — and a page where you can rewrite any sentence the machine got wrong.
What is translated
- Pages, posts, header, footer and every template
- Menu entries, categories and tags
- Title, slug, excerpt and the text for search results
- Forms, shop texts, memberships, newsletters
- Dates and numbers in the form each language uses
How it works
- Translated on first view, then stored — paid for once
- Sentence by sentence: change one, the rest stay
- Your correction survives every later translation
- hreflang, sitemap and a switcher block come with it
- Up to thirty languages per site
What you can skip
- No WPML, no Polylang, no second installation
- No duplicate of every page per language to keep in step
- No translation interface beside the builder
- No subscription per language, no licence per domain
- No third-party script in the visitor's browser
Real pages
Each language has its own addresses.
The difference from a translate widget is not the quality, it is the address. /fr/chambres is a page: search engines index it, a visitor can send it to somebody, a link from outside lands on it, and the next click stays in French. hreflang for every version and an entry in the sitemap come with it. The switcher is a block you place where it belongs — in the header, the footer, or both. The site you are reading runs that way itself: nine languages, and /fr/ is a page like any other.
Fix a sentence
What you write by hand stays written.
Machines are fast and sometimes wrong — with terms of the trade, with names, with tone. In the builder you switch to the language and see each sentence on its own, the original beside it. What you type becomes the translation from then on; the machine never touches it again. Because the store hangs on the sentence and not on the page, a new paragraph costs that paragraph only.
Visible in the menu
You can see what is still missing.
Every menu entry shows which languages it already exists in — small marks behind the name, and where one is missing, it is missing visibly. The same goes for categories and tags: they are called what you say they are called in each language, not what a machine guessed.
Questions
Do I need WPML or Polylang?
No. Languages are part of ambera. You do not end up with a second page per language to maintain twice — there is one page and its translations, sentence by sentence.
What does translating cost?
The machine charges per character, once: what has been translated then sits in your database. A medium site costs a few francs per language, one time. A monthly ceiling stops anything from running away.
Does Google punish machine translation?
What gets punished is auto-generated text with no use to anyone — not a translated page that helps a reader. What matters is an address per language, hreflang, and content somebody wants. ambera gives you all three; correcting by hand is what makes the difference.
What happens when I change a sentence?
Only that sentence is translated again. The store finds it by a checksum of the original; change it and it is new, while the others stay as they were.
Is it in the free version?
Translation in the browser yes, real pages per language no — those are Pro, and in every Pro plan.
The WordPress theme builder has a name.
Built in Switzerland. Built for WordPress.