Blog Tag translations cover the name and slug. The name is what shoppers see wherever blog tags are shown, and the slug is used when localized blog post data references that tag.
On the web
- In your store admin, go to Translations.
- Choose the language you want to translate into.
- Select Blog Tags.
- Enter the translated name and, optionally, a translated slug.
You can also translate blog tags with per-language CSV import and export or AI translation jobs. Changing the original blog tag name 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 tag until those translations are removed. The same backend rule applies to forms, update 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 tag 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.