In this guide: Checklist for reviewing a translated page before publishing or delivering it.
Contents
- Why validate
- Validation checklist
- When to validate
- Tip
Why validate
Saving translations does not always mean that a page is ready to publish. A translation may be correct from a text point of view, but still need visual review, length adjustments, or link checks.
Validation helps avoid errors before delivering a multilingual website.
Validation checklist
Check that all visible texts are translated.
Review buttons and calls to action.
Check that internal links point to the correct language.
Review forms, placeholders, and messages.
Check that HTML and shortcodes have not been broken.
Review responsive design if translated texts are longer.
Regenerate cache if the frontend does not show changes.
Verify the page as a visitor, not only as an administrator.
When to validate
After translating an important page.
After importing JSON translations.
After modifying original texts.
Before delivering a website to the client.
After updating Oxygen, WPML, or the connector if there were critical pages.
Tip
Create a review routine for each page: translation, cache, frontend, links, and responsive. It is much safer than trying to review the whole website at the end.