All posts

MSM and Translation in AEM: Best Practices That Scale

Daniel Strmečki

Localization is one of the first areas where many Adobe Experience Manager (AEM) implementations start to feel unnecessarily complex. Most projects start with simple requirements, such as adding a second language or translating a few pages. However, over time, the business expands its websites to support new regions, introduces different language variants, or publishes in multiple languages within a single market. A structure that worked for only two locales suddenly becomes difficult to maintain. In AEM, where content flows continuously across environments, we need a model that scales cleanly rather than a structure that grows by accident.

In this article, we'll cover how AEM's Multi-Site Manager (MSM) and Translation Framework fit together, explain the difference between a Language Copy and a Live Copy, and recommend a content structure that supports markets, languages, and brands without introducing long-term maintenance issues.

MSM vs Translation Projects

MSM is a content inheritance and site structure system in AEM, often misunderstood as a translation system. However, it does not handle localized copy or manage language-specific differences. MSM’s purpose is purely structural. It enables editors to maintain global consistency across markets, including the site hierarchy, navigation, page templates, component policies, and the general layout. MSM is a tool that makes it possible for markets/regions to inherit new pages or design updates from a global site blueprint.

A Translation Project in AEM is the mechanism that packages content for translation and applies translated text back to the site. It tracks which pages, components, and properties need translation and integrates with either human translation providers or machine translation services. Translation Projects update only the translatable content properties and do not control site structure or inheritance. When used with Live Copies, translated properties automatically break inheritance, allowing localized edits while structural elements continue to inherit from the blueprint.

Language Copy vs Live Copy

AEM offers two distinct methods for creating localized versions of a site. In practice, we often choose to use one or the other for each locale to avoid mixing different inheritance models.

A Language Copy creates a locale root and connects it directly to the translation framework. It is simple and works well for small sites with only a few languages. However, a Language Copy does not maintain any relationship with its origin/blueprint. Therefore, it will not inherit any future structural or content updates. Each locale created as a Language Copy behaves completely independently. This is fine for use cases where markets do not share much content or structure, or when local teams desire high autonomy.

A Live Copy creates a structural inheritance relationship with its blueprint. When the blueprint changes, those updates can be rolled out to every market predictably and consistently. Translation Projects still apply normally; they simply update the editorial content inside each Live Copy. This model supports centralized governance, consistency, and scale, especially when dealing with many markets and multiple languages per market.

For most enterprise AEMaaCS implementations, Live Copies provide the stability and consistency required to manage a global site over time.

A Scalable Content Structure

Most organizations don’t think in terms of “one language per site”; they think in terms of markets, and markets often have more than one language. The English language in the UK is not the same as the English language in the US. Also, many US sites may also publish in additional languages, such as Spanish. Canada usually requires both English and French, so AEM’s site structure should reflect that reality.

A clean and scalable structure in AEMaaCS may look like this:

/content
   /brand-a
      /blueprint
         /en
      /uk                 (market)
         /en              (live copy → translated)
      /us                 (market)
         /en              (live copy → translated)
         /es              (live copy → translated)
      /ca                 (market)
         /en              (live copy → translated)
         /fr              (live copy → translated)
   /brand-b
      /blueprint
         /en
      /sg                 (market)
         /en              (live copy → translated)
      /jp                 (market)
         /ja              (live copy → translated)

In this structure, each market is not a page, but a folder (such as /uk, /us, /ca, /jp) and serves as an organizational container. Most teams implement the market page as a simple redirect, so visiting /us automatically redirects users to its default language page /us/en. This redirect page is not part of MSM or the Translation Framework; it only exists to route traffic to the appropriate default language.

Each language folder inside a market (such as /us/en, /us/es, or /ca/fr) is a Live Copy of the centralized blueprint. It inherits global navigation, templates, layout, and any other structural changes defined in /blueprint/en. In a Live Copy, editors can break inheritance on pages or individual components to edit them locally without being overwritten by future rollouts. They can also add new local components or pages that are not part of the blueprint. Content that remains inherited stays locked and continues to receive updates from the blueprint.

Translation Projects are still used to translate the local content into the target language. The translation process breaks inheritance on the translated properties, allowing local language edits, while non-translated structure and components can continue to inherit from the blueprint. This model reflects real-world needs: global consistency at the structure level, and full flexibility for content and localization inside each market/language.

Other Models Depending on Editorial Workflows

While the blueprint + Live Copy approach works well for large organizations, it’s not the only valid way to structure content in AEM. Some editorial teams prefer a more autonomous model where each market operates independently and shares little or no structure at all. Others maintain a single global site with localized content fragments delivered headlessly, without duplicating page structures at all. Smaller teams may use Language Copies exclusively if they prefer simplicity over governance.

There is no one-size-fits-all solution; the right model depends on how editors collaborate, how much content is shared between markets, and how aggressively the organization standardizes global structure. The important part is careful consideration and choosing the right model from the start, rather than evolving into one by accident.

How MSM and Translation Fit Together

MSM and translation work well together when each system stays in its lane. The blueprint defines the global structure, and Live Copies inherit that structure. Translation Projects populate localized content inside each Live Copy. Markets override structural elements only when they have a legitimate need to do so.

This separation prevents the most common localization problems: overwriting translated content during rollouts, markets drifting away from global standards, and important structural updates failing to propagate to all markets.

Most long-term AEM issues come from unclear ownership. Teams sometimes treat MSM as a translation tool or push structural rollouts after a translation cycle finishes, overwriting localized text. Some markets break inheritance on dozens of pages without governance. Others manually duplicate pages, creating branches that are no longer connected to the blueprint. One problematic setup is where a live English site is also treated as the blueprint, mixing global and market responsibilities into a single site.

All these problems can cause scalability issues, and fixing them later usually requires a complete restructuring of the site.

Conclusion

For many large, globally distributed AEM implementations, a single blueprint per brand with market-language Live Copies provides a clear and scalable foundation. It creates a predictable flow where structural changes originate centrally, translations are handled explicitly through Translation Projects, and markets override only when there is a real business need. This model makes global updates easier to govern and reduces the risk of fragmentation as new regions and languages are added.

That said, this approach is not universally optimal. Some organizations benefit from looser coupling between markets, simpler Language Copy setups, or even headless localization models, depending on their editorial autonomy, governance maturity, and content reuse strategy. The key takeaway is not to blindly follow a pattern, but to choose a structure deliberately. AEM scales well when MSM, translation, and editorial workflows are aligned from the start. Most problems arise when structure evolves reactively rather than by design.

If you’re evaluating your current localization setup or planning a global rollout, this is exactly the type of decision that benefits from an experienced second opinion. We help teams design AEM localization and MSM strategies that fit their organization, not just the platform.

All posts

Blog

All posts

If these challenges sound familiar, explore how we help enterprises reduce risk.