Fix a translation that does not appear
Use this guide when the Translation Manager contains a value but the public page still displays the source language.
Isolate the value
- Open the exact target-language URL while logged out.
- Confirm its language prefix and
<html lang>match the intended locale. - Find the source string in the Translation Manager.
- Confirm the translation is non-empty and saved under that same locale.
- Check whether the post, term, or locale is excluded.
Check the surface
- For a post field, confirm its post type and title, content, excerpt, or metadata part is enabled.
- For metadata, confirm the exact key is registered as translatable.
- For a term, confirm its taxonomy is enabled.
- For interface text, confirm the source is a registered string rather than arbitrary runtime text.
- For REST or AJAX, confirm the route/action and textual field are supported.
If the source changed after translation, save the current base-language object and review the newly extracted value. Exact source identity matters for registered and imported strings.
Remove rendering variables
Clear only the affected page, object, and CDN caches. Disable a custom output override temporarily and retest with the standard theme output.
Do not copy the translation directly into the source post or database tables. If the value appears in the wrong target locale as well, investigate leaked language context rather than the stored text.
The issue is resolved when a logged-out request returns the saved target value without requiring an editor session or browser-language redirect.