AEM translated fragments still point to the source locale

An AEM team has thousands of reusable Content Fragments. It wants to translate only changed snippets, yet the localized fragments still reference paths under the source language. A recent Experience League discussion describes exactly this tradeoff: including unchanged referenced fragments in a translation job may fix paths but can make already large jobs harder to run.

Treat the reference as a separate deliverable

The business requirement is not merely a translated string. A localized page or app must resolve each nested reference to an approved fragment in its own language. Inventory a representative graph of source fragments, their references, existing target-language copies, and the expected target paths. Include references to fragments that were not changed this cycle. A successful translation job with source-locale links is still an incomplete release.

Test the supported configuration on a small graph

Adobe's knowledge-base article on this symptom says reference paths can be adjusted when the translation setting includes associated assets rather than “Do not translate.” That guidance solves the path symptom in its example; it does not prove that every unchanged referenced fragment can be excluded from a large translation job. Measure job size, repeated entries, and provider charges on a small fixture before changing a global translation setting.

Choose an operating rule for unchanged references

If the standard setting brings too many fragments into jobs, define a narrowly scoped post-translation validation or path-rewrite step with AEM owners. It should confirm that the target fragment exists, that locale roots map predictably, and that references outside the expected tree are rejected. Test rollback and publish a broken-reference report. Do not blindly replace language tokens in paths: Adobe's fragment model treats language variants as separate fragments with matching relative paths only when the content structure supports that convention.

Adovo’s view

Localization is a graph problem disguised as a translation job. The release is ready when the translated content and every reference land in the right locale; sending more text to a provider is only one way to get there. Make path integrity a release gate, then optimize job size against that gate.