Translate term slugs

A localized term slug controls the term's own path segment. It is edited independently from the translated name and description.

Open the slug editor

1. Save the source term at least once after POM Translate is configured.
2. Go to Translations → Translate URLs.
3. In Localized slugs, select Term.
4. Use Search for an item to choose the term.
5. Select Load slugs.
6. Review the read-only Base slug.
7. Enter a value in each required Slug for locale field.
8. Select Save slugs.
9. Confirm the notice Slugs updated.

Only additional-language slugs are editable here. Changing the source slug belongs in the normal WordPress term editor.

Normalization and conflicts

POM Translate applies WordPress slug normalization when saving. Human-readable text such as Diseño Interior becomes a path-safe value such as diseno-interior.

The same localized slug cannot be reused by another stored post or term in that locale. A conflict produces Slug "value" is already in use for locale. Choose a distinct route and save again.

An empty submitted field is ignored; it does not delete the stored localized slug. If a target slug has never been stored, the editor and frontend can use the base-language slug as a fallback.

Hierarchical terms

For a child term, translating only the child slug may still leave source wording earlier in the path. POM Translate builds the archive from ancestor slugs in top-down order, using each ancestor's localized value when available and falling back to its base slug otherwise.

After a change, test the generated link rather than typing the expected path manually. Continue with Understand term archive URLs.