Translate a category

WordPress categories are hierarchical: a category can have a parent, and its archive path may contain every ancestor. POM Translate keeps that hierarchy and the post assignments unchanged while localizing visible wording and URL segments.

The category taxonomy is always enabled, so there is no category checkbox to activate.

Prepare the category branch

Choose a category that is assigned to at least one published post. If it has parents, save and translate the branch from the top level down. A localized child archive can use the slug of each ancestor, so testing only the leaf category can hide an incomplete path.

Translate the category

1. Open Posts → Categories.
2. Edit the source category and confirm its Name, Slug, Parent category, and Description.
3. Select Update. This collects the current name and non-empty description and initializes missing language slugs.
4. Open Translations → Translate contents.
5. Select the target locale.
6. Set All objects to Term.
7. Enter category in Taxonomy (terms only) and the category's ID in Object ID, then select Filter.
8. Translate the name and description rows and select Save translations.
9. Open Translations → Translate URLs, select Term, search for the category, and choose Load slugs.
10. Enter the target slug and select Save slugs.

Repeat the slug step for each ancestor when the site uses nested category paths.

Verify the result

Open the localized archive and check:

• the translated heading and optional description;
• the language prefix;
• the category base;
• every parent slug in the correct order;
• the category's own slug;
• links from posts, breadcrumbs, menus, and selectors;
• canonical and alternate-language URLs.

The same WordPress category ID and parent relationship must remain in use. Do not create a translated child category and reassign posts as a substitute for this workflow.

If the label is correct but the route is not, continue with Understand term archive URLs.