Verify Translation Quality

Review every translated post or page before publishing it. A successful provider response does not prove that the wording is correct, that every field was extracted, or that the page layout and Polylang relationship are correct.

Review language and meaning

Confirm that the target language is the one you intended and that names, product terms, measurements, dates, and calls to action retain their intended meaning.

Check negation, tone, context-sensitive phrases, and terminology used across the site.

Compare important legal, medical, financial, or other high-impact text with an approved human-reviewed translation before publication.

Check formatting and mapped fields

Open the target post or page in its editor and review the translated content in context.

Check headings, paragraphs, lists, buttons, image alternative text, captions, links, and other fields that matter to the page.

Verify that the page builder layout remains intact and that URLs, email addresses, placeholders, and other non-translatable values remain valid.

If a field is missing or unchanged, check the editor-specific extraction and XML mapping rules. Start with Understand Content Field Mapping, Translate Gutenberg Block Content, or Translate Elementor Content.

Check whether cached wording was reusedTranslateSense can reuse a saved translation when the source-string hash and target language match. The persistent cache does not distinguish provider, model, or prompt, so the wording may have been created during an earlier workflow. If the result looks unexpected, compare the source phrase and target language first, then test a changed phrase in a controlled draft. Do not assume that selecting a different provider forces every matching string to be translated again.

Verify the final WordPress state

Use the editor’s review or preview to inspect the complete target page.

Confirm the target post’s language and its relationship to the source post in Polylang.

Save or update the target content using the editor’s normal save action; applying translated values in the editor is not the same as publishing them.

Recheck the front-end preview for layout, links, missing text, and language-specific issues.

Keep editorial corrections in the saved target content and follow your normal review process before publishing.

When to investigate mapping or processingIf whole fields are absent, review the XML mapping and supported builder fields. If a bulk job is pending or stopped, use Monitor Translation Progress and Check WordPress Cron for Translation Jobs. If the text is present but reads poorly, correct it and review the provider or prompt choices in AI Providers and Translation Settings.

Screenshot to add: [Translated page quality review checklist]