Three built languages: Finnish, English and Swedish
Your English site is not your site run through a translator.
It is another page, with its own address, that Google indexes separately and that can rank for words that do not exist in Finnish.
You put in the automatic translation widget and thought it was handled. It is not. Google indexes only one version, the Finnish one, because it is the only one that exists as a page. The foreign buyer searches for the component by its English name, and you do not show up in that search. You have not even lost, you have not played.
And the worst part comes after you are found. When that buyer arrives from a link a colleague sent, clicks the flag and reads a machine translation of your product description. In industry that matters more than it sounds, because the buyer is judging at the same time whether you are serious, whether you answer emails, and whether you will still be there in five years. One badly phrased sentence on a technical page answers those three questions before you do.
Six pieces, already built
Its own address per language
Correct hreflang tags
A visible language switcher, on mobile too
Editing language by language from the same panel
Already applied in 13 demos
Four steps
The language map gets decided
Which languages, and which one is the main one.
The address structure gets defined
One route per language, stable.
Each version's content gets prepared
This is where you decide what gets translated and what gets rewritten.
hreflang gets wired up
Every page points to its siblings and to itself.
Frequently asked questions
What exactly is hreflang?
A tag in the code of each page that tells Google the same page exists in another language.
Can I start with two languages and add the third later?
Yes. The address structure is left ready from the start.
What happens if a page exists in Finnish but not yet in English?
The switcher does not lead to a blank page. It resolves to the closest equivalent.
How many times has this been done?
In 13 published, navigable demos.