Route translated term slugs

A localized taxonomy archive combines its language prefix, taxonomy rewrite base, term ancestry, and final term slug. POM Translate maps that route back to the original WordPress term.

Store the term slug

1. Save the term in its standard WordPress taxonomy screen.
2. Open Translations → Translate URLs → Content URLs.
3. Select Term.
4. Search for the term and choose Load slugs.
5. Confirm the correct taxonomy and Base slug.
6. Enter Slug for locale for each required language.
7. Select Save slugs.
8. Open the generated term archive from a post, menu, breadcrumb, or term list.

The slug editor needs the taxonomy as well as the term ID. Keep the plugin or theme that registers a custom taxonomy active while managing its routes.

Account for hierarchy and suffixes

For a hierarchical taxonomy, POM Translate builds every ancestor segment in order. Each ancestor uses its target-locale slug, then its base-locale slug, then the current WordPress term slug.

Supported archive suffixes such as pagination or feed segments are separated from the term hierarchy during route resolution and appended again to the canonical localized path.

Diagnose the path by segment

Given:

/es/category/parent/child/page/2/

review these components independently:

1. es — language prefix;
2. category — taxonomy route base;
3. parent — ancestor term;
4. child — selected term;
5. page/2 — archive suffix.

A translated term name does not determine any of those stored URL values. A valid archive can also contain a source-language segment when that segment has no localized slug.

For the editorial term workflow, see Translate term slugs.