Bilingual Content Sync

Maintains a map of every EN page and its FA counterpart (or any locale pair you run). The map is built from your route structure at setup and updates automatically as pages are added or removed, so it never silently drifts out of date the way a manually maintained spreadsheet would.

Detects a meaningful content change in either locale — not a typo fix, a real edit to claims, pricing, or structure. It reads the actual rendered page content, not just the CMS field that was touched, so a change made through a shared template or component still gets caught even if no one edited the page’s own record directly.

The paired page in the other locale is flagged for review — never auto-translated and republished silently. The flag links directly to both the old and new version of the edited page, so whoever writes the native counterpart copy is working from the exact change, not hunting for what is different.

Separates meaning-level divergence (a claim changed) from wording-level (a rephrase) so reviewers prioritise correctly. A pricing or numeric change is always treated as meaning-level regardless of how small the edit looks, since a single digit is exactly the kind of "small" change that causes the most damage left unsynced.

A weekly view shows how many pairs are in sync, how many are flagged, and the oldest unresolved flag. A pair that stays flagged past a second consecutive week gets called out separately in that report, so a stale gap between locales does not quietly age for months inside a routine digest.