Blog Post translations cover the title, slug, content, excerpt, SEO title, and SEO description. The title and content are what shoppers read on localized post pages, and the slug is used in the localized post URL.
On the web
- In your store admin, go to Translations.
- Choose the language you want to translate into.
- Select Blog Posts.
- Enter the translated title, content, and other fields, and optionally a translated slug.
You can also translate blog posts with per-language CSV import and export or AI translation jobs. Changing the original blog post title or slug can mark existing translations as outdated.
If a field already has translations in any language, you cannot clear that field on the original blog post until those translations are removed. The same backend rule applies to forms, translation imports, and any other source edit path.
Translation CSV imports are row-atomic. If any translated field in a row is invalid, references a missing blog post ID, duplicates a localized unique value, or tries to translate a field whose original value is blank, that row is rejected and none of that row's translated fields are saved. Other valid rows in the same file can still be imported.