Support Log in

Seeing What Changed — Content Diff (PRO)

User Guide
Prefer video? Watch the Lang Forge tutorials 9 short guides covering every feature Watch

On any multilingual site, the original content is constantly evolving. Blog posts get updated with new information, product descriptions change as features are added, page layouts are reworked for better conversion, and policy pages are revised to reflect new regulations. When the original changes, every translation of that content becomes partially outdated because it still reflects the old version. Content Diff is a feature that automatically detects when an original post has been modified after its translations were created, shows you exactly what changed with a visual comparison, and helps you update the translations to match.

Without Content Diff, keeping translations in sync with originals requires manually comparing posts — opening the English version in one tab and the Spanish version in another, trying to spot what is different. On a site with hundreds of translated posts, this is essentially impossible to do consistently. Content Diff automates the detection and makes the review process clear and fast.

How Content Diff tracks changes

Lang Forge takes a snapshot of the original post’s content at the moment each translation is last updated. When the original is edited and saved again, Lang Forge compares the new content with the stored snapshot. If there are differences, it flags every translation of that post as “needs update” and stores the detailed comparison.

Step-by-step: Reviewing and resolving a content diff

  1. When an original post is updated, all its translations are flagged as out of date. You will notice this in two places:
– The Out of Date tile in the Translation Health section on Lang Forge → Reports → Translation Status shows the total count plus a per-language chip breakdown. Click the tile to jump to the filtered list.

– The Language metabox of the flagged translation shows a warning icon and a “Content Changed” notice (see the next steps). The Language column in post lists does not mark flagged translations

  1. Open any flagged translation post in the WordPress editor
  2. In the Language metabox, you will see a “Content Changed” notice that says how long ago the original changed
  3. Click Show Changes to open the diff view
  4. The diff view shows the original content with changes clearly highlighted:
– Green highlighted text = content that was added to the original

– Red highlighted text with strikethrough = content that was removed from the original

– Unchanged text is displayed normally for context

  1. Review the changes and decide how to update the translation. You have two options:
– Manual update: Edit the translation directly in the editor to reflect the changes you see in the diff

– Re-translate: on the Out of Date list in Translation Status, the Re-translate button re-runs AI translation of the whole post against the latest source content and overwrites the existing translation. It uses AI credits. There is no button that updates only the changed segments

  1. After updating the translation, click Mark as Current in the metabox
  2. The warning banner disappears and the translation is flagged as up to date

Managing diffs across your entire site

The Translation Status page (Lang Forge → Reports → Translation Status) is an entry point. Two places surface out-of-date content:

  • The Translation Health → Out of Date tile at the top of the page shows the total count and a per-language chip breakdown. Click it to load the dedicated Out of Date Content list — Title, Type, Language pair (e.g. English → Русский), Original modified, Translation modified, when it was Flagged, plus Re-translate (primary) and Review (secondary) buttons per row.
  • The Language metabox of each flagged translation shows the “Content Changed” notice. The Language column in the post list does not mark flagged translations, so use this page to find them.

Workflow:

  1. Open Lang Forge → Reports → Translation Status
  2. If the Out of Date tile shows a non-zero count, click it. The page scrolls to and loads the Out of Date Content list, sorted with the most recently flagged first. The list shows at most 200 translations and has no next page, while the tile counts all of them. If more than 200 are flagged, narrow the list with the Post Type and Missing translation for filters at the top of the page (press Filter, then click the Out of Date tile again), or deal with the first rows and reload to see the older ones.
  3. Choose per row:
– Re-translate — re-runs AI translation against the latest source content. The row fades out on success (the translation is no longer outdated). Burns AI credits.

– Review — opens the translation in the editor; follow the diff workflow above and click Mark as Current when done. Free.

  1. Returning to Translation Status, click ← Back to Untranslated to swap the page back to the missing-translations list.
  2. If many originals had only minor changes (typo fixes, whitespace, paragraph reflow), you still mark each translation as current on its own: open it with Review and click Mark as Current in its Language metabox. There is no bulk Mark as Current, neither in the Posts list nor on the Translation Status page.

Email notifications

Content Diff itself sends no email. The separate Email Notifications setting in Lang Forge > Settings (Content & Notifications) is one on/off switch. When it is on, users with the translator role and administrators get an email when new content in the default language is published and needs translating. There is no choice of recipients and no immediate, daily, or weekly option.

Real-world example: Seasonal content refresh

A retail website updates its homepage hero text, 15 product descriptions, and 3 policy pages as part of a spring promotion. After the content team saves the English updates, Lang Forge immediately flags 19 translations per language as out of date. The Spanish translator opens Lang Forge → Reports → Translation Status, clicks the Out of Date tile, and picks out the 19 Spanish translations in the Out of Date Content list. She starts with the homepage (highest priority), opens the diff view, sees that only the hero headline and one paragraph changed, edits those two passages by hand, and marks it as current. She works through the 15 product pages next — most have only a price or feature list change, which she edits directly. The 3 policy pages need careful manual review.

What happens on the Free plan

Content Diff is not available on the Free plan. When an original post is updated, there is no visual indicator on its translations and no diff view. Teams on the Free plan need to manually track which originals have changed — which becomes impractical on sites with more than a few dozen posts.

> Tip: After making a round of updates to your original content (like a seasonal refresh, product launch, or policy change), open Lang Forge → Reports → Translation Status and click the Out of Date tile. The Out of Date Content list shows up to 200 of the flagged translations, with the most recently flagged first, so you have a quick list of the translations that need translator attention.

> Good to know: Content Diff compares the title and the content of the original word by word, after removing the HTML tags. In the diff view, the words that were added are marked as added and the words that were removed are marked as removed, so fixing a single typo marks that word, not the whole paragraph. Lang Forge keeps a copy of the original from before the change; Mark as Current replaces that copy with the current original. A Save All in the Visual Editor that does not write the content (you typed nothing in it, and the translation already has content) leaves that copy and the notice as they are. A Save All that writes the content replaces the copy and clears the notice, when every block of the original has its place in the translation after the save. The save that the editor makes by itself and the one after AI Translate go the same way.

[Screenshot: The Content Diff view showing green-highlighted added text and red-strikethrough removed text, with the “Show Changes” and “Mark as Current” buttons]

—

Forge AI Assistant Online

Hi! I'm the Lang Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs