Choose one storage model before translating

Polylang, WPML and TranslatePress do not store translations in the same way. Translator detects the active system and loads only its matching adapter. Never assume that disabling one multilingual plugin and enabling another migrates existing translations.

Common preparation for every system

1. Back up the site.
2. Configure source and target languages.
3. Choose the language URL structure.
4. Assign the original content to the correct source language.
5. Verify the default homepage, menus and theme locations.
6. Translate one page as Draft and validate it before products or large queues.

Polylang workflow

For Polylang, Translator creates or updates a native target-language post, assigns its language and links it to the source in Polylang’s translation group. The target should preserve the source post type, template, parent relationship, featured image and compatible builder/custom-field data.

1. In Polylang, verify that the source post type and required taxonomies are translatable.
2. Open Translator → Dashboard and confirm Polylang is detected.
3. Open Translate and confirm the source row shows the correct original language.
4. Start one target-language draft.
5. In the WordPress editor, verify the Polylang language box links source and target.
6. Assign translated menus and the translated front page through Polylang.

If an incomplete linked draft already exists, the retry workflow may recover and replace it after validation. Delete only the incorrect target-language post—not the source—and verify the language relationship before retrying.

WPML workflow

For WPML, Translator creates or updates the target version inside the WPML translation relationship. WPML continues to control languages, URL format and its translation preferences.

1. Confirm the required post types and fields are set to Translate, Copy or Copy once as appropriate.
2. For WooCommerce, verify WooCommerce Multilingual configuration and currency/stock synchronization.
3. Confirm WPML is detected on Translator → Dashboard.
4. Translate one draft and open the target through the result card.
5. Verify the WPML language relationship, field-copy rules, media and product variations.

Do not use a field as both Translator-managed human text and WPML-synchronized technical data. Product IDs, prices, stock, SKU, variation relationships and dimensions should remain synchronized technical values.

TranslatePress workflow

TranslatePress stores rendered strings in its dictionary instead of creating a normal target-language WordPress post for each page. Translator scans rendered source strings, protects technical fragments, sends translatable text and writes verified directional entries back to the TranslatePress dictionary.

1. Configure the source and target languages in TranslatePress.
2. Visit a representative page and trigger tabs, forms, product variations or popups so dynamic strings can render.
3. Confirm TranslatePress is detected.
4. Run a small translation and review the target front end using the language switcher.
5. If verification reports missing rendered strings, inspect the exact missing items and render their component state before retrying.

A 330/333 verification result means three expected rendered strings were not confirmed. It does not justify overwriting the original or marking the job complete. Identify the three strings, determine whether they are dynamic or protected, then retry only the target workflow.

Rules for switching multilingual systems

• Never deactivate or delete the current system during an active job.
• Export or back up its translation data first.
• Use a documented migration process; Translator is not a relationship migrator.
• Rebuild Translator inventory after the new system is configured.
• Translate a fresh test item and verify URLs, menus, hreflang and links.

Adapter acceptance checklist

• Only the intended adapter writes data.
• Source content is unchanged.
• Target language and URL are correct.
• Language relationships are native to the active multilingual plugin.
• Menus, homepage, SEO and WooCommerce behavior work in the target language.