Translate a tag
Tags are flat editorial labels: they group related posts but have neither parents nor children. Localizing one changes its readable label and archive segment, while the original membership and post counts remain attached to the same term.
POM Translate includes post_tag permanently. Its eligibility is not controlled by an optional taxonomy checkbox.
Choose the target wording
Decide whether the concept is normally translated in the destination language. Product names, acronyms, and established loanwords may stay unchanged even though their translation row is completed.
Keep these values separate:
| Value | Purpose |
|---|---|
| Name | Label shown beside posts, in clouds, and in the archive heading |
| Description | Optional explanatory text rendered by some templates |
| Slug | URL-safe archive segment |
Publish the localized tag
- Under Posts → Tags, update a tag that already has published content.
- Visit Translations → Translate contents and select the destination locale.
- In the table controls, choose Term, type
post_tagin Taxonomy (terms only), and select Filter. - Complete the
namerow and thedescriptionrow if one exists. - Select Save translations.
- Switch to Translations → Translate URLs.
- Choose Term, locate the tag with Search for an item, and select Load slugs.
- Fill Slug for locale, select Save slugs, and follow the generated public link.
Inspect the archive title, tag cloud, post byline or metadata, breadcrumbs, feeds, and menu entries. The route contains an optional language prefix, a taxonomy base, and one tag segment—never a chain of ancestors.
Preserve the editorial grouping
Creating a second tag for another language would split queries, counts, feeds, and assignments. Leave an unfinished target row blank so the source label acts as the fallback instead.
If the wording switches but its archive does not resolve, use Troubleshoot taxonomy translations.