Twelve languages by default: how multilingual sites rank
Serving a site in twelve languages is a translation problem for about a day. The part that decides whether it ranks is the URL and markup structure underneath.
Sample article shipped with the buildEvery site built on the platform ships with twelve locales available from day one. Translation is the visible part; the part that determines whether those pages earn traffic is structural.
One URL per language
Each locale needs its own crawlable URL. A site that swaps language client-side without changing the URL gives search engines one page where there should be twelve.
Declare the alternates
hreflang annotations tell a search engine that these pages are the same content in different languages, so the right one is served to the right visitor instead of them competing with each other.
Translate the metadata too
Titles, descriptions and structured data are content. A translated page carrying an English title is a page that will not rank in its own language.
Do not machine-translate and forget
The first draft can be generated. Someone who speaks the language should read anything that represents the business — service names and legal text especially.
This is a sample article included with the site build. Replace it with a real post before launch.