Handle incomplete translations

POM Translate can render a localized route even when some target rows are empty. For each missing value, it uses the corresponding source text while preserving the localized page structure.

This fallback prevents blank headings and broken layouts, but it can produce a mixed-language experience.

Identify what is missing

The post editor shows a translated percentage for each additional locale. The figure is:

non-empty target rows ÷ all extracted post and registered meta rows

Select Manage translations, then filter Translate contents by Pending. A pending row may be empty, but bulk status actions can also label a non-empty value pending. Inspect the textarea rather than relying only on its badge.

Decide whether fallback is acceptable

Fallback can be reasonable for:

• a protected brand name;
• an invariant product model;
• a temporary internal or private review;
• low-risk content during a controlled rollout.

Do not rely on mixed-language fallback for:

• legal notices;
• checkout, account, or consent flows;
• safety instructions;
• pricing or contractual terms;
• prominent navigation;
• content advertised as fully localized.

An explicit source copy and an empty fallback are editorially different. Save an explicit copy only after deciding the wording should remain identical.

Complete the missing rows

1. Open the source object and confirm its current structure.
2. select Manage translations for the target locale;
3. filter Pending;
4. translate each empty row;
5. preserve protected placeholders;
6. save;
7. reload the table;
8. check whether the count and percentage changed;
9. inspect the public localized route.

If POM AI is enabled, individual pending rows can offer a machine-translation action, and the post editor can offer Translate with AI for missing strings. Machine output remains a draft for human review.

Understand what the percentage excludes

The post summary counts post and configured metadata rows. It does not prove completion of:

• localized slugs;
• taxonomy terms;
• menu labels;
• custom URL mappings;
• registered defaults;
• software strings;
• WooCommerce emails;
• text stored by an unsupported builder.

Review the whole visitor journey before launch.

Do not create intentional blanks by clearing a row

Clearing a target value means “translation missing,” so the source appears. It does not mean “render nothing.”

If a target locale must omit a component, use a supported locale-aware template, exclusion, or integration. Do not use an empty translation textarea as a visibility control.

Troubleshoot a percentage that will not reach 100%

Look for:

• newly added source rows;
• enabled metadata fields;
• a source change that invalidated one segment;
• a placeholder error that prevented saving;
• rows on another table page;
• an object-level or locale exclusion;
• an active background queue that temporarily locks saving.

If the editor reports No translatable strings found yet, confirm the source object is published or private and save it after enabling the relevant content parts.

Continue with Understand translation status.