Languages and translations
Website languages determine which content versions visitors can read. The main language provides the source pages; secondary languages have translated versions with their own text and metadata. The CMS interface language is a separate preference.
Translations share the source page identity. Their language and localized slugs distinguish them, so the language selector can connect versions even when their addresses differ. Collection prefixes and ancestor slugs also contribute to the final public URL.
Adding a language does not translate the website. Create the needed page versions, review their copy and metadata, and include shared content such as footers. Automatic translation requires a configured provider, and reviewed translations can be protected from global retranslation.
Check missing translations as a visitor. The language selector omits unavailable targets, while some navigation links may retain a source-language destination. These are not a promise of automatic translated content.
Use Pages and navigation, Blogs, and Search visibility and sharing alongside this topic when checking multilingual structure and publication.