Publish a blog post in multiple languages

Guides

Start with an approved source post

Publish language variants of one post rather than creating unrelated posts that merely resemble each other. Beeboo uses shared page identity to connect translations even when their titles and slugs differ.

You need an existing dated collection, an approved source article, configured target languages, and a reviewer for each language. Confirm administrator access and the exact website, blog root, source page ID, and source language. Record the article's date, summary, image, and current availability before generating anything.

Finish factual corrections in the source first. A translation should not quietly introduce new offers, dates, guarantees, or claims. Agree on terminology for names that should remain unchanged. The instructions below explain publication steps in English; they do not supply or create another language's text.

Translate and review deliberately

1. Open the source post in Pages and inspect Page Translations. If the intended language is absent, add it through the website language settings before proceeding. Do not change the main language or create a second blog collection solely to hold the translation.
2. Choose Translate to for one target language. In the CMS, this requests generated translated content. With MCP, create_translation creates a structure shell instead, so an assistant must not report a finished translation until reviewed text has been written and read back.
3. Use Open for the resulting translation. Check the title, subtitle, body headings, quotations, links, button labels, image descriptions, and summary against the source. Preserve actual publication facts. A translated summary should explain the same article without adding claims absent from the source.
4. Inspect the translated slug and resolved public URL. Blog item slugs are relative to the collection's configured base path and language settings. Check the collection's localized name or base path where applicable instead of constructing a URL from a guessed prefix.
5. Review the translation's Date, Availability, and SEO fields. A future date can hide an item from listings while leaving direct access possible. Do not use scheduling or missing navigation as a substitute for confidentiality. Save the reviewed language variant explicitly.
6. Repeat for each approved language, then enable Translation protected where editorial review should be preserved against bulk automatic translation. Treat Re-translate as a possible replacement operation, not a harmless refresh button.

Check the article and its discovery routes

Open each normal public article URL outside the editor. Switch languages from the post and confirm that the destination is its corresponding translation. Follow internal links, inspect the sharing image, and read the article on a phone.

Also open the blog listing in each language. Check the title, summary, date, and link destination there; a correct article can still be hard to find through a misconfigured listing. If a translation is missing, verify page identity, language configuration, availability, and collection settings before creating another copy.

Sending a subscriber message is a separate action and is not part of translating or saving the post. See blogs, languages and translations, and search visibility.