Handle links to untranslated content
POM Translate can keep a canonical WordPress object reachable even when some of its target-language text or URL segments are incomplete. Decide deliberately whether visitors should see that fallback or whether the menu item should be hidden in that locale.
Understand the partial-result cases
- A blank menu-label translation displays the source navigation label.
- A blank post or term text translation displays the corresponding source value.
- A missing localized slug can leave the source slug in an otherwise localized route.
- A custom URL without a target mapping keeps its original destination.
These behaviors are independent. A menu can therefore show translated navigation wording while its destination page still contains source-language copy.
Hide one menu item from selected locales
- Open Appearance → Menus.
- Expand the item.
- Under Display in languages, select every locale in which the item should appear.
- Select Save Menu.
- Visit both an included and an omitted locale.
Leaving every checkbox clear means display in all languages. It does not mean hide everywhere.
Language visibility only removes the menu item. It does not make the destination private, unpublish the object, or prevent another link from reaching it. Use the product's translation exclusions when an entire post, term, or menu item must be excluded from a locale, and verify the resulting route behavior separately.
Choose a publication policy
Before launch, classify each incomplete destination:
- Accept fallback: appropriate when the source language is an intentional temporary substitute.
- Hide from navigation: useful when the content may remain reachable but should not be promoted.
- Exclude the subject: use when the locale should not expose that translated surface.
- Complete before launch: safest for legal, checkout, account, safety, and conversion-critical paths.
Test direct URLs as well as menus. Removing a link from navigation is not an access-control mechanism.