Translate term names
The term name is the readable label used in archive headings, post metadata, breadcrumbs, filters, selectors, and many menu items. POM Translate stores one name row per parsed term and substitutes its translation for the active non-base locale.
Edit a name
- Save the source term in its normal WordPress taxonomy screen.
- Open Translations → Translate contents.
- Select an additional language.
- Choose Term under All objects.
- Narrow the table with Object ID, Taxonomy (terms only), or Search strings.
- Find the row whose field is
name. - Enter only the visitor-facing label.
- Select Save translations and confirm Translations updated.
A manually entered non-empty name receives Human status. Clearing the translation and saving leaves it Pending; the frontend then uses the source name.
Keep names distinct from slugs
Spaces, accents, punctuation, and capitalization belong in the translated name when linguistically appropriate. The path-safe form belongs in Translate URLs. Editing one does not derive or overwrite the other.
For example, a target name may be Diseño de interiores while its localized slug is diseno-interiores. Enter each value in its own workspace.
Check every display context
Review more than the archive heading. The same term object may appear in:
- a post's category or tag list;
- a filter control;
- breadcrumb output;
- related-content cards;
- a menu linked directly to the term;
- a REST or Store API response supported by the integration.
POM Translate preserves the term ID, taxonomy, parent, and object relationships. Only its readable values are replaced. If one component still shows the source label, confirm that component retrieves a normal WordPress term rather than using a separately stored static string.