Diagnose POM Translate problems

Start with one affected object, one target locale, and one logged-out URL. Identify which layer fails before changing settings or clearing data.

Diagnostic order

1. Confirm the locale is enabled and the final URL selects it.
2. Confirm the source value was extracted.
3. Confirm a non-empty translation is stored for that locale.
4. Check whether the object or locale is excluded.
5. Verify the relevant content type, field, taxonomy, or integration is enabled.
6. Inspect rendered output without caches.
7. Check localized routing, selector links, SEO, AJAX/REST, email, or background context as applicable.

Choose the symptom

• A translation does not appear
• A page is partly untranslated
• A visitor sees an old translation
• A content skeleton is outdated
• A registered string is missing
• A menu label is not translated
• The language selector is missing
• A selector opens the wrong URL
• A translated URL returns 404
• A bulk job stops
• POM AI credits or authorization fail
• A WooCommerce email uses the wrong language
• Collect safe support information

Do not reset translation storage as a general troubleshooting step. Back up first and make the smallest reversible change.