One day, our authoring team reported an issue while creating regional page variants using Live Copy in Adobe Experience Manager (AEM).

Our platform runs multiple regional sites and languages — including the United States, Europe, and Japan — from a centralized Language Master site root, where the blueprint content resides.

The situation can be represented by the following debugging flow.

From the diagram above, two possible issues appear:

• an MSM inheritance issue
• incorrect request routing when users access the root domain

First, the MSM content structure is checked to determine why the EU page references the US footer Experience Fragment.

Understanding Multi-Region Architecture in AEM

Multi-region site architecture in AEM is built on Multi-Site Manager (MSM).

Below, blueprint pages (source) push content to regional sites via rollout and synchronization.

From this, we see that the eu/en page may reference the US XF footer instead of a regional one defined in the blueprint.

There are two ways to fix this:

• Fix the footer reference in the template (Content / MSM)
• Fix request routing at the CDN layer (connectivity)

Start with the template. Without changing backend logic, authors often duplicate templates and hardcode a footer per region.

Below shows how this workaround works and why it creates more problems over time.

TODO