AEM MSM site structure pros/cons | Community
Skip to main content
A
abid22
Level 1
February 12, 2026
Solved

AEM MSM site structure pros/cons

  • February 12, 2026
  • 2 replies
  • 0 views

Please help me to understand pros/cons between MSM site structure options as below:

Option 1:

/content/mysite/language-masters/en → /content/mysite/us/en

/content/mysite/language-masters/fr → /content/mysite/fr/fr

 

Option 2:

/content/mysite/language-masters/en_us → /content/mysite/en_us

/content/mysite/language-masters/en_gb → /content/mysite/en_gb

Best answer by giuseppebaglio

hi ​@abid22,

You’re essentially choosing between a “language‑first, then country” model (Option 1) and a “language+country as one locale” model (Option 2). Both are valid in AEM; the better option depends on how you localize and govern content.

Aspect Option 1: Language-first Option 2: Locale-first (en_us, en_gb)
Reuse High (one global en master shared across all English regions reduces duplication) experienceleague.adobe+1 Lower (separate en_us, en_gb masters create content duplication across similar languages) experienceleague.adobe​
Translation Simple (translate once from single en master to create fr, de language roots) experienceleague.adobe+1 Complex (must choose which English variant like en_us or en_gb serves as translation source) experienceleague.adobe​
Autonomy Medium (regions inherit from language master but can break inheritance for local changes) experienceleague.adobe​ High (each locale operates independently without shared language master constraints) nortal​
Adobe Fit Matches WKND tutorial and official examples (/language-masters/en → /us/en) experienceleague.adobe+1 Supported as valid language roots but not Adobe's primary teaching pattern experienceleague.adobe+1
URLs Needs dispatcher rewrites to serve friendly /en-us/ URLs from internal /us/en paths aem​ Natural mapping to SEO-preferred /en-us/, /en-gb/ URL structures aem​

 

As recommendation and decision criteria, given Adobe’s examples and translation guidance, Option 1 is usually the safer, more scalable default for a global site, especially if:

  • You want a single global English master.

  • Translation is a big part of your roadmap.

  • Regions mostly localize, not completely reinvent, pages.

Choose Option 2 only if:

  • Each region’s content is substantially different and business leadership insists on regional autonomy.

  • You have governance and dev capacity to handle more MSM/translation complexity and duplication.

 

References:

Translation Best Practices

Multi Site Manager and Translation

Reusing Content: Multi Site Manager and Live Copy

 

 

2 replies

giuseppebaglio
giuseppebaglioAccepted solution
Level 10
February 12, 2026

hi ​@abid22,

You’re essentially choosing between a “language‑first, then country” model (Option 1) and a “language+country as one locale” model (Option 2). Both are valid in AEM; the better option depends on how you localize and govern content.

Aspect Option 1: Language-first Option 2: Locale-first (en_us, en_gb)
Reuse High (one global en master shared across all English regions reduces duplication) experienceleague.adobe+1 Lower (separate en_us, en_gb masters create content duplication across similar languages) experienceleague.adobe​
Translation Simple (translate once from single en master to create fr, de language roots) experienceleague.adobe+1 Complex (must choose which English variant like en_us or en_gb serves as translation source) experienceleague.adobe​
Autonomy Medium (regions inherit from language master but can break inheritance for local changes) experienceleague.adobe​ High (each locale operates independently without shared language master constraints) nortal​
Adobe Fit Matches WKND tutorial and official examples (/language-masters/en → /us/en) experienceleague.adobe+1 Supported as valid language roots but not Adobe's primary teaching pattern experienceleague.adobe+1
URLs Needs dispatcher rewrites to serve friendly /en-us/ URLs from internal /us/en paths aem​ Natural mapping to SEO-preferred /en-us/, /en-gb/ URL structures aem​

 

As recommendation and decision criteria, given Adobe’s examples and translation guidance, Option 1 is usually the safer, more scalable default for a global site, especially if:

  • You want a single global English master.

  • Translation is a big part of your roadmap.

  • Regions mostly localize, not completely reinvent, pages.

Choose Option 2 only if:

  • Each region’s content is substantially different and business leadership insists on regional autonomy.

  • You have governance and dev capacity to handle more MSM/translation complexity and duplication.

 

References:

Translation Best Practices

Multi Site Manager and Translation

Reusing Content: Multi Site Manager and Live Copy

 

 

giuseppebaglio
giuseppebaglio
Level 10
February 12, 2026

hi ​@abid22,

You’re essentially choosing between a “language‑first, then country” model (Option 1) and a “language+country as one locale” model (Option 2). Both are valid in AEM; the better option depends on how you localize and govern content.

Aspect Option 1: Language-first Option 2: Locale-first (en_us, en_gb)
Reuse High (one global en master shared across all English regions reduces duplication) experienceleague.adobe+1 Lower (separate en_us, en_gb masters create content duplication across similar languages) experienceleague.adobe​
Translation Simple (translate once from single en master to create fr, de language roots) experienceleague.adobe+1 Complex (must choose which English variant like en_us or en_gb serves as translation source) experienceleague.adobe​
Autonomy Medium (regions inherit from language master but can break inheritance for local changes) experienceleague.adobe​ High (each locale operates independently without shared language master constraints) nortal​
Adobe Fit Matches WKND tutorial and official examples (/language-masters/en → /us/en) experienceleague.adobe+1 Supported as valid language roots but not Adobe's primary teaching pattern experienceleague.adobe+1
URLs Needs dispatcher rewrites to serve friendly /en-us/ URLs from internal /us/en paths aem​ Natural mapping to SEO-preferred /en-us/, /en-gb/ URL structures aem​

 

As recommendation and decision criteria, given Adobe’s examples and translation guidance, Option 1 is usually the safer, more scalable default for a global site, especially if:

  • You want a single global English master.

  • Translation is a big part of your roadmap.

  • Regions mostly localize, not completely reinvent, pages.

Choose Option 2 only if:

  • Each region’s content is substantially different and business leadership insists on regional autonomy.

  • You have governance and dev capacity to handle more MSM/translation complexity and duplication.

 

References:

Translation Best Practices

Multi Site Manager and Translation

Reusing Content: Multi Site Manager and Live Copy

 

​​​​

Terms & ConditionsAccessibility statement

Loading footer...