Validate an imported translation set
An import completion message confirms processing, not editorial or migration completeness. Review its counters and then inspect stored and rendered results.
Interpret skipped entries
- Existing translations were intentionally retained when using Skip existing translations.
- Missing matches mean the exact source text was not present in POM Translate storage.
- Empty imported values are ignored.
- Invalid entries failed protected placeholder validation.
A high missing-match count usually means content was not extracted on the destination, or its source wording differs from the export.
Check stored values
- Open the Translation Manager for the imported locale.
- Find several distinctive source strings from the export.
- Confirm the translated text and workflow status.
- Include entries containing inline formatting or placeholders.
- Check both newly filled and previously populated strings if an override policy was used.
Do not infer success only from the total number imported. Exact source text may occur in multiple contexts, so one file entry can update several stored string records.
Check public output
While logged out, review a representative:
- page or post;
- structured or page-builder layout;
- taxonomy archive;
- navigation menu;
- WooCommerce product or email workflow when applicable.
Confirm language routing, formatting, internal links, and fallback behavior. Imported text does not restore localized slugs or other URL data, so validate those separately.
Resolve problems safely
If the wrong values were imported with Override existing translations, stop further locales and restore the database backup or correct the affected translations manually. Re-importing with Skip existing translations will not replace those non-empty values.
For missing matches, generate the destination source strings first and retry the same locale. For placeholder skips, return to the untouched export and compare the protected markers; do not remove them simply to force acceptance.