Skip to content Skip to sidebar

This topic contains 0 reply, has 0 voices.

Last updated by lobkeB 1 month, 2 weeks ago.

Assisted by: Maiya AI Support.

Author Posts
June 22, 2026 at 9:05 am #18117639

lobkeB

We use WooCommerce, WPML and the Flatsome theme with UX Builder.

For regular pages, we no longer translate everything line by line in the WPML Translation Editor. Instead, we create the Dutch page in UX Builder, place the content in HTML blocks, and then manually translate those HTML blocks for each language. This works much better for SEO and saves a lot of time.

We would like to know whether a similar workflow is safe and recommended for WooCommerce product pages.

Can we safely switch existing WooCommerce products from the WPML Translation Editor to manual translation / WordPress Editor, without risking that existing translations, variations, attributes, stock, images, prices, SKUs or SEO fields are overwritten, disconnected or lost?

Ideally, we would like to manually translate and optimize the product descriptions, short descriptions, FAQ sections and possible UX Builder content per language, while keeping technical product data such as SKU, price, stock, variations, attributes and images properly synchronized by WPML.

What is the recommended workflow for this?

Also, if we switch an existing translated product from the WPML Translation Editor to manual translation, will the existing translated content remain intact? And what happens when we later update the original Dutch product?