Translate post slugs

POM Translate stores one slug per post and locale while keeping a single WordPress post ID. The same editor covers posts, pages, and eligible custom post types.

Save a localized slug

1. Save the source post in its normal WordPress editor.
2. Open Translations → Translate URLs → Content URLs.
3. Select Post.
4. Use Search for an item and select the required object.
5. Choose Load slugs.
6. Review the displayed Base slug.
7. Enter each Slug for locale.
8. Select Save slugs.
9. Follow a generated frontend link for every edited locale.

Input is normalized as a WordPress slug when saved. An empty input is ignored rather than used to erase the route.

Understand hierarchical paths

For a hierarchical post type such as pages, the route contains the localized slugs of all ancestors followed by the current object's slug:

/fr/parent-traduit/enfant-traduit/

Each segment falls back independently to its stored base slug and then to the current WordPress post_name. Complete the parent chain before treating the child route as fully localized.

For custom post types, the registered rewrite or archive base can precede the object path. That base is distinct from the individual post slug.

Verify resolution

The localized route must resolve back to the original post ID. Check:

• the locale prefix;
• any post-type route base;
• every ancestor page;
• the final post slug;
• pagination or endpoint suffixes where relevant;
• the canonical and alternate-language URLs.

If the translated slug is already stored for another object in the same locale, the editor reports a conflict and does not save that value. Choose a genuinely distinct slug.

Changing the post title later does not automatically rewrite the localized slug. Review titles and paths as separate publication decisions.