Multilingual search metadata

Documentation / Search visibility and sharing

Each translated page can have its own SEO title, description, and social image. The language version should describe its own visible content rather than relying on a main-language snippet.

Edit in the intended language

Select the page's target content language before opening the SEO tab. The tab identifies the language being edited. Save the SEO title, description, social image, and indexing choice for that version, then reload to confirm persistence.

Automatic translation includes several title, summary, and SEO text fields, but generated copy still needs review. A translated page identity does not guarantee that its current wording or social image suits the audience.

Site settings also allow a description for each content language. For secondary-language pages, the engine does not borrow the main-language site description when localized copy is missing. If no suitable page or localized description exists, it can omit description metadata.

Understand alternate addresses

Translations share the source pageId, allowing sitemap alternates to connect versions whose slugs differ. Public pages also emit language-alternate links, and Open Graph locales are normalized for sharing metadata.

The sitemap filters unavailable, future-dated, and explicitly excluded pages before grouping alternates. Do not expect every configured language to appear when corresponding public content is absent.

Validate a translation pair

Inspect the source and translated page for the document title, description, canonical URL, language-alternate links, and social image. Then inspect the sitemap group and follow its URLs.

Check a nested collection item as well as an ordinary page because localized collection prefixes and ancestor slugs can change the full address. Metadata does not compensate for broken translated navigation.

See Languages and translations and Collections and content trees.