In this guide: Recommendations for working safely and in an organized way with Oxygen and WPML.
Contents
- Plan before translating
- Work page by page
- Use JSON carefully
- Always review the frontend
- Do not translate technical fields
- Keep backups
Plan before translating
Before you start, define the source language, target languages, priority pages, and review workflow.
On large websites, do not try to translate everything without a clear order. Start with key pages and global templates.
Work page by page
Scan one page.
Translate or export JSON.
Import if appropriate.
Validate.
Review the frontend.
Only then move on to the next page or block.
Use JSON carefully
JSON is ideal for external or AI-assisted translation, but it should not be edited without a clear reason.
Keep the structure, IDs, keys, HTML, shortcodes, and URLs unless you know exactly what you are changing.
Always review the frontend
A translation may be saved and still need a visual review.
Texts in another language may be longer and affect buttons, columns, or sections.
Do not translate technical fields
Do not force translations on CSS classes, IDs, SVG, tokens, or internal settings.
The plugin already avoids many of these fields for safety.
Keep backups
Before large imports, bulk changes, or AI-assisted translations, make sure you have a recent backup.