The normal case, and the one this site uses: one build, every language. One address, one deploy, one search, and the switcher jumps between the versions without a detour.
What works properly:
- Switcher,
hreflang, redirects, notices — all of them know all languages - A link from a German to an English page stays an ordinary link
- The explorer shows both language trees
The one place where it grates
The interface texts follow the site-wide locale: “Backlinks”, “Last updated”, the label on the
search, the date format. On a German site that is what the English pages say too.
Two things help without splitting the build:
localizeDates: true— at least the dates then follow the page’s language (7.2).- Filter the explorer — it can show one tree per language. The helper for that is in 9.2.
For everything else: anyone needing a fully translated interface builds once per language — 8.2.
The search index covers every language
A search for “coffee” also finds the German page if the word appears there. That is rarely a problem and sometimes wanted; in a shared build it cannot be turned off.