Use post and term menu links
Menu items created from WordPress pages, posts, post-type archives, categories, tags, or other supported terms should keep their native object relationship. POM Translate localizes their generated URLs through the routing system; they do not need an entry in the custom URL dictionary.
Complete the destination before testing the menu
- Keep the original WordPress object attached to the menu item.
- Translate its readable content under Translations → Translate contents.
- Open Translations → Translate URLs → Content URLs.
- Select the object type and load the same post or term.
- Enter the target-locale slug and save it.
- Return to Appearance → Menus only if the navigation label itself also needs editing.
- Follow the link generated by the public menu.
POM Translate resolves an internal URL back to its base path, rebuilds the path for the requested locale, and adds the language prefix when that locale uses one. Existing query parameters, fragments, and trailing-slash style are retained.
Avoid converting native items into Custom Links
A manually pasted URL loses the semantic relationship WordPress normally maintains for an object-backed menu item. Prefer adding the page, post, archive, or term from its native menu panel. This keeps normal WordPress link generation and POM Translate's post and term URL filters in the path.
Use Custom links only when the destination is genuinely custom, external, a file, an iframe source, or otherwise requires an explicit mapping.
Verify the complete route
For a post or page, check the language prefix and every localized rewrite or slug segment. For a hierarchical term, inspect the taxonomy base, all ancestor segments, and the selected term's slug. A working route can contain a source-language segment when its localized slug is blank because URL localization has its own fallback behavior.
The menu label and object title are also separate strings. Translating the page title does not automatically replace a custom navigation label.
See Translate term slugs for taxonomy destinations and URLs and routing for the complete route model.