DEV Community

Mahdi JabinPour
Mahdi JabinPour

Posted on

A Translation Change Log for WPML: Keep Product Updates Consistent Across Languages

The first multilingual launch usually gets plenty of attention. The fifth small edit to a product page often gets much less.

Suppose a store changes a laptop specification, adds a compatibility exception or revises an installation service. The original page is updated. Which translated pages now need attention, and who decides when the change is finished?

I would answer those questions with a small change log before adding more automation.

Disclosure: We develop Lumo WPML AI Translation Addon. This article describes a maintenance process to use with it, rather than claiming that the addon automatically detects or verifies every source change.

Record the source edit in plain language

A useful entry says what changed, not just that a page was edited. “Updated the adapter compatibility note” gives a reviewer something concrete to check. “Content updated” does not.

Keep the source URL, edit date, affected languages and the facts that changed together. Add the person responsible for review. A spreadsheet or a task in your normal project system is enough.

Here is an illustrative entry:

Field Example
Source page Product A
Change Added an exception for an older accessory
Languages to review French and German
Scope Compatibility paragraph and related FAQ
Acceptance Exception present on published pages

This is a manually maintained checklist. It does not depend on assuming that any particular field or template is automatically synchronized.

Decide the scope before translating again

A title correction and a rewritten product description are different jobs. Avoid retranslating a complete catalogue when you only need to review a defined set of pages.

Our addon includes title-only and body-only retranslation options. Choose the relevant mode for the content you intend to update, and confirm what that operation covers in your current WPML setup. A changed field outside that scope may need separate attention.

Keep the reviewer focused on meaning

Give the reviewer the old fact, the new fact and the source page. Ask them to confirm that the translation reflects the change without losing an exception or adding an unsupported promise.

If the page contains measurements, product identifiers or service conditions, check them explicitly. A general “looks good” is difficult to audit later.

Treat a finished job as the beginning of verification

Open the actual translated URL. Check the changed section, its links and the mobile layout. If the fact also appears in an FAQ or template, review that location too.

For long content, Lumo WPML AI Translation Addon works in chunks and can resume from the last finished chunk. That helps manage the processing work. It does not replace deciding which content is affected or approving the published meaning.

Close the task with evidence

Record the reviewed URLs, reviewer and completion date. Leave unresolved languages clearly marked as pending rather than closing the entire task because one page passed.

This creates a useful handover for agencies. A client can see what was updated, and another developer can pick up the next change without guessing.

The addon uses your own supported provider API key inside the WPML workflow. WPML is required and AI usage is billed separately by the provider.

See Lumo WPML AI Translation Addon.

The habit matters as much as the translation tool: when the original changes, make the other languages part of the same work item.

Top comments (0)