AEM Sites Playbook, Chapter 6: Multisite, localization and local ownership
What remains central, what can vary locally and how do translations stay correct?
November 10, 2026
Decide what must remain shared
Use this chapter when adding a brand, language or region, or when central updates interfere with local content. Begin with a map of current sites, language relationships, templates, shared content and responsible teams. The business decision is which information must stay consistent and which local teams may adapt it.
Distinguish translation from a business variation. Translating the same offer differs from changing an offer for a market. Define ownership at the content-object or field level: central product facts, locally approved legal text, regional imagery or market-specific navigation. Give exceptions an owner and expiry/review date rather than leave an unexplained inheritance cancellation indefinitely.
Map these decisions to the actual MSM, Live Copy and translation configuration. Adobe's Live Copy guidance separates creation, synchronization and inheritance controls. A central/local policy needs tests for those operations; it cannot be inferred from the presence of a blueprint.
Rehearse central and local changes
Create a representative local copy with known central content. Make a permitted local change, then perform the intended rollout. Compare the result with the agreed policy. Repeat the operation after moving, copying or removing a relevant component. Check navigation and referenced fragments, not only the visible text on the starting page.
In the disinherited-component discussion, the author traced duplication/order behavior to local copying/deleting and changed node names. That report supports tracing the actual content changes. It does not prove that every rollout preserves local edits or that MSM has a general reordering defect.
Record differences at the content and reference level. An editor who sees the right heading may still be using an English fragment or an unintended shared image. Give regional reviewers a checklist that includes links, locale-specific facts, dates, labels and the target channel's display conventions.
Translate the dependency set
List translatable fields and references for both standard and custom components. Review the 6.5 translation rules for that deployment and use its current Cloud Service equivalent where applicable. The 6.5.16 reference-translation discussion shows why a service-pack claim alone cannot establish correct behavior for custom references.
Decide who owns text alternatives and asset metadata in each language. Central metadata can help reuse, while a particular page may require a different alternative. The alt-text ownership discussion connects that decision to content and asset teams. Test the delivered component's actual behavior before relying on a fallback.
Carry locale relationships into customer discovery. Chapter 13 covers language-sensitive search; chapter 15 covers canonical and hreflang output. Keep one owned mapping of corresponding locale URLs so those implementations do not silently diverge.
Turn central and local policy into explicit rules
Community discussions connect rollout problems to different boundaries: local content and node changes, reference translation, and unresolved configuration advice. Some suggested fixes lack a confirmed result. Test the actual content structure and references on the stated release before treating a reported outcome as a universal product defect.
Scroll horizontally if needed.
| Content element | Policy question | Test operation |
|---|---|---|
| Shared product fact | Must every market receive the same approved value? | Central update followed by the intended synchronization |
| Local offer or disclosure | Who may change it, and should central rollout preserve it? | Approved local override followed by repeated rollout |
| Component structure/order | Which changes are central and which are local? | Copy/move/delete/reorder on a representative local fixture |
| Experience Fragment reference | Which locale counterpart should the page use? | Translation and delivered-reference inspection |
| Image and alternative | Can the local use differ from central metadata? | Locale-specific rendering and accessible-content review |
| Locale URL | Which published page corresponds to each other locale? | Mapping, navigation, search and metadata checks |
Avoid a single global statement such as regions can edit their pages. It leaves unresolved whether a region may change centrally governed facts, cancel inheritance or delete shared structures. Define the smallest meaningful unit of ownership and document an exception when the product/configuration cannot enforce the policy exactly.
Worked scenario of a central correction and a local offer
This hypothetical rollout covers an English master and French and German local experiences. Central product management owns a technical specification. Each market owns promotional copy. A reusable fragment supplies supporting content in each language.
Before testing, the teams agree that a central specification correction must propagate, local promotional copy must remain, and every page must reference the intended language fragment. A regional editor and central operator use ordinary roles; an administrator does not silently repair the fixture between tests.
The team records the content paths/objects, inherited and overridden fields, translation configuration and original values. It then performs:
Step 1. A central fact update and the intended rollout.
Step 2. A permitted local copy edit followed by another rollout.
Step 3. A local component reorder/copy operation that authors actually use.
Step 4. Creation of a translated page and inspection of its references.
Step 5. Withdrawal or replacement of a shared item and review of dependent pages.
Scroll horizontally if needed.
| Acceptance requirement | Hypothetical result | Decision |
|---|---|---|
| Central fact reaches both markets | Correct | Pass for the tested relationship |
| Local promotional copy survives | Correct in French; German value replaced | Hold German rollout until the ownership/configuration issue is resolved |
| Component order follows the policy | Changes after a local copy/delete operation | Trace actual structure before blaming rollout generally |
| Translated reference points to the local fragment | French page still points to English | Hold locale acceptance |
| Regional reviewer can identify the approved result | Reviewer sees page text but lacks reference evidence | Improve the review checklist |
The team can approve the central/local model as a direction while holding the affected market and reference behavior. It must not present partially correct text as a complete multilingual launch. If a narrower launch is proposed, the business owner explicitly accepts its market scope and communication consequences.
Choose a repair without multiplying site variants
Scroll horizontally if needed.
| Finding | Candidate action | Required proof |
|---|---|---|
| Local edit was never permitted by policy | Correct guidance or approval policy | Authors understand the allowed operation |
| Policy permits the edit but configuration does not preserve it | Correct the implementation or document a bounded alternative | Repeat the same edit/rollout successfully |
| Custom reference property is absent from translation handling | Assess the actual resource type and translation rules | The required reference changes in a representative translation |
| Brand needs a genuine structural difference | Assess separate template/policy ownership with shared components | Central fixes still reach intended components without unwanted local change |
| Many unexplained inheritance exceptions exist | Inventory ownership and reconcile content | Every retained exception has a reason and review owner |
Use deployment-specific Live Copy guidance and the applicable translation rules. A historical service-pack claim does not establish behavior for an untested custom property or Cloud Service implementation.
Keep localization operable after launch
Assign owners for translation requests, vendor handoffs, failed jobs, locale reference mapping and regional sign-off. Capture when source content changes during translation and how the reviewer identifies a stale proposal. Agree whether a correction triggers retranslation and who handles delayed markets.
Retain the central/local policy, fixture values, operations and delivered observations together. Re-run the set after template/component changes, translation configuration changes or a new language relationship. The regional owner's acceptance should cover the full experience, including navigation, references, search and withdrawal, rather than only translated text.
Accept a locale as an operating capability
Complete W06 with central/local ownership, inheritance decisions, translation scope, references and representative test results. Accept new locale creation, repeated rollout, local exceptions, translated dependencies and withdrawal. The regional content owner signs off the customer-facing result; the platform owner retains the repeatable checks and escalation path. A rollout job finishing is insufficient evidence that the local experience is correct.
W06 Brand and locale ownership
Use with chapter 6. Verify permitted local changes survive the intended central operation.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Central/local owner by content object or field | [enter] |
| Blueprint/Live Copy/language relationships | [enter] |
| Inheritance/override rule and reason for exceptions | [enter] |
| Translation fields, custom references and asset alternatives | [enter] |
| Central edit, local edit, repeated rollout and move/delete test | [enter] |
| Locale URL mapping, search/discovery checks and regional sign-off | [enter] |
