Review translated content before publication

POM Translate separates non-empty completion from editorial approval. Build a review process that checks both the string table and the assembled visitor experience.

The Reviewed status is applied by an authorized editor; the plugin cannot infer linguistic quality.

Assign a review boundary

Review one canonical object and one locale at a time. Use Manage translations from the post editor so Translate contents opens with the object and locale already selected.

Record:

• source object and ID;
• target locale;
• translator;
• reviewer;
• URL under review;
• whether machine translation was used;
• any external legal or subject-matter approval.

Do not put private customer data or credentials into translation notes or screenshots.

Review the string table

1. Filter Machine and review every generated row.
2. filter Human and perform the required second pass;
3. compare each target with Original Text and Context;
4. preserve protected placeholders;
5. check terminology, tone, numbers, names, and punctuation;
6. save any textual corrections;
7. reload to confirm the corrected rows now show Human;
8. select approved rows and choose Mark as Reviewed.

If the table spans pages, finish and mark one page at a time.

Review the assembled route

The table cannot reveal every interaction between rows. Open the localized URL and verify:

• title, excerpt, headings, paragraphs, and metadata;
• inline markup restored by placeholders;
• buttons, forms, validation, and accessible labels;
• internal and external links;
• translated slug and redirect behavior;
• menus and taxonomy terms;
• canonical and alternate-language metadata;
• responsive layout;
• cache and signed-out behavior.

Use a private browser window to avoid a saved language preference masking the route under review.

Check source fallback

The post summary’s percentage counts non-empty target values. Filter Pending and scan the public page for remaining source-language text.

Some unchanged brands may be intentional. Save an explicit reviewed copy when the target wording is deliberately identical; otherwise keep the missing row visible in the queue.

Review outside Translate contents

A complete object can require separate approval under:

• Translate URLs;
• taxonomy translations;
• menu and custom-link translations;
• Other translations;
• Software translations;
• WooCommerce email translations;
• SEO and discovery output.

Do not mark content complete solely because its post summary reaches 100%.

React to source edits

After approval, ask source editors to flag material changes. Saving changed source text invalidates translations for affected rows and can lower the completion percentage.

Before launch or after a revision:

1. reload the source editor summary;
2. filter Pending;
3. review any regenerated row;
4. inspect the public route again;
5. reapply Reviewed only after the new target wording is approved.

Sign-off checklist

• No unintended source fallback remains.
• All machine text received human review.
• Placeholder validation passes.
• The public route matches the correct locale.
• Slugs and internal links are correct.
• Functional components work.
• Layout passes desktop and mobile review.
• Approved rows are marked Reviewed.
• Caches have been refreshed.
• A later source change has an assigned owner.

Continue with Preview a translation for the route-testing method.