Blog templates and translated posts
A blog template supplies reusable page structure, such as a consistent header arrangement or a shared listing beside editable article content. A translated post supplies another language version of the same page identity. Neither removes the need to review each post's metadata.
Use a template deliberately
Apply an available page template through the page's template settings. Collection configuration can also support a default template, although the basic collection form does not expose every advanced setting.
Template-bound rendering combines shared template content with the page's editable content. Locked template areas stay sourced from the template. Edit those shared areas in the template rather than trying to overwrite them in one post. Keep article-specific copy and media in the editable areas.
Page-level SEO metadata belongs to the post. It is not inherited from the template, so check the title, description, and social image separately.
Translate the post
Configure the target language, then use the page's translation controls. A translation shares the source pageId; its language and localized slug distinguish the version. Blog addresses combine the locale prefix, localized collection base path when configured, and the translated item slug.
Automatic translation requires a working provider connection. Review generated text, links, header content, summary, date, and metadata before treating the translation as ready. Protect reviewed translations from global retranslation when appropriate.
Validate both versions
Open the source and translation, follow their language-selector links, and inspect the blog listing in each language. Listings select posts for the current language rather than filling missing translations with source posts.
See Templates and reusable content, Languages and translations, and Search visibility and sharing.