How Translator knows content changed

Translator records source-segment state and compares it with approved target-language state. A translation can be Current, Missing or Outdated. Outdated means relevant source content changed; it does not automatically mean the complete page must be recreated.

Recommended update workflow

1. Edit and save the source content.
2. Confirm the source item remains assigned to the correct original language.
3. Open Translator → Translate.
4. Filter for missing or outdated translation.
5. Select only the affected target language and item.
6. Start the update and monitor it in Jobs & Logs.
7. Review changed sections, the full responsive page and SEO before publishing.

Incremental retranslation

Incremental processing reuses unchanged validated segments and sends only new or modified translatable text when safe. This reduces provider usage and helps preserve consistent wording. A structural builder change can still require a full-page validation even if only a few text segments changed.

Translation memory

Approved source/target segments become reusable memory for the same language direction. Memory should contain reviewed text, correct terminology and valid placeholders. Do not approve unfinished drafts or mechanically incorrect strings merely to increase the memory count.

Manual edits

A human editor may improve the target after AI translation. Keep those edits inside the target-language item and use the review/protection workflow so an automatic update does not silently replace deliberate wording. When source meaning changes, decide whether the manual target still represents the new source.

Automatic queuing

The option to automatically queue changed source content is useful only after the site’s workflow is proven. Keep target status as Draft or require approval if source editors can make high-impact changes. Avoid automatic publication for regulated claims, legal text, pricing conditions or content that requires market-specific review.

When to run a full validation

• The page builder structure changed.
• The page template or theme condition changed.
• Product variations, custom tabs or attributes changed.
• A form, popup, global widget or custom field schema changed.
• The multilingual plugin or adapter changed.

Outdated item does not appear

1. Confirm the source post was saved.
2. Verify it is still the original-language item.
3. Confirm the post type is enabled.
4. Rebuild inventory.
5. Clear only relevant application caches.
6. Do not delete the target or source until relationships are checked.

Update acceptance checklist

• Only changed meaning was updated.
• Approved unchanged terminology remains consistent.
• Manual edits are preserved or deliberately revised.
• Layout, links, SEO and language relationships remain valid.
• No duplicate target-language item was created.