Multilingual MODX: Babel vs LangRouter Setup Guide
After adding a second language, the site stops being found in search — duplicate pages, missing hreflang, and manual content transfer becomes exhausting. A typical scenario for MODX: without proper architecture, multilingual turns into a nightmare. We have implemented many multilingual projects and know how to avoid these pitfalls. Below are two proven approaches: Babel (contexts) and LangRouter (single context). Babel is 2–3 times more reliable than LangRouter for large projects, but not always necessary.
How to Choose Between Babel and LangRouter?
When to Use Contexts with Babel?
Contexts with Babel are the standard for sites with heavy content: e-commerce stores, portals, news feeds. Each language gets its own resource tree, templates, and settings. Babel links corresponding pages across contexts so the language switcher works correctly. Maintenance savings reach up to 40% due to clear separation. For example, on a project with three languages (Russian, English, German), we reduced the time for adding new content by 35% after implementing Babel.
When Is LangRouter Enough?
LangRouter fits if content is identical across languages — for instance, a corporate site with a few pages. It works in one context, switches language via URL prefix and changes cultureKey. The downside: all resources are mixed, making translation management more complex. Setup pays for itself within 2–3 months.
Why Babel Is Preferable for SEO?
Babel allows precise hreflang links for each resource pair. This is critical for ranking in different regions: without proper hreflang, search engines see duplicates and downgrade the site. Babel also supports x-default, pointing to the main version. LangRouter does not offer this flexibility — hreflang must be configured manually via chunks. As stated in the Babel documentation, Babel automatically generates hreflang for linked resources, reducing error risk by up to 60%.
Step-by-Step Babel Setup
- Install Babel via Package Manager.
- Configure system settings — specify contexts and their prefixes.
- Create resources in each context and link them via Babel.
- Add a language switcher using BabelLinks.
- Configure hreflang for SEO.
Installation and Configuration
// Package Manager → Babel System settings for Babel:
babel.sites = web,en,de babel.contextPrefix_en = en/ babel.contextPrefix_de = de/ babel.contextPrefix_web = Language Switcher Output
[[!BabelLinks? &tpl=`@INLINE <a href="[[+url]]" hreflang="[[+cultureKey]]" class="lang-switch [[+active:is=`1`:then=`lang-switch--active`]]"> [[+cultureKey:upper]] </a> ` &activeCls=`active` ]] BabelLinks automatically creates links to linked resources in other contexts.
hreflang for SEO
[[!BabelLinks? &tpl=`@INLINE <link rel="alternate" hreflang="[[+cultureKey]]" href="[[+url]]">` &toPlaceholder=`hreflang` ]] <head> [[+hreflang]] <link rel="alternate" hreflang="x-default" href="[[++site_url]]"> </head> Common Mistakes When Setting Up Multilingual
- Missing resource links in Babel. If resources from different contexts are not linked, the language switcher will lead to the home page or 404. Always verify links after creating a new resource.
- Incorrect context prefixes. If the prefix does not match the actual URL, hreflang breaks. Ensure prefixes coincide with server settings.
- Ignoring x-default. Without x-default, search engines may choose the language for a region on their own, lowering relevance. Always add a link with hreflang="x-default" pointing to the main version.
Comparison of Babel and LangRouter
| Parameter | Contexts + Babel | LangRouter |
|---|---|---|
| Content separation | Full (own resources) | Single tree (TVs or lexicons) |
| Suitable for | Large sites, e-commerce | Small projects, corporate sites |
| Reliability | High (different contexts) | Medium (single context) |
| Setup complexity | Medium (contexts + links) | Low (single package) |
| Flexibility | Maximum (own templates and settings) | Limited |
Setup Timeline (approximate)
| Approach | Time (business days) | Complexity |
|---|---|---|
| Contexts + Babel | 2–3 | Medium |
| LangRouter | 1–2 | Low |
What's Included in Multilingual Setup
- Architecture analysis — choose approach (Babel/LangRouter), optimize.
- Context setup (if Babel): creation, domain binding.
- Installation and configuration of Babel/LangRouter.
- Creating resource links (for Babel).
- Developing language switcher.
- Configuring hreflang, sitemap for each language.
- Documentation and training: handover of instructions for adding new languages.
- Warranty: bug fixes within 30 days after delivery.
Timelines and Guarantees
Setting up two languages via Babel with switcher and hreflang takes 2 to 3 business days. With LangRouter, it's faster, from 1 day. We recommend Babel for projects with high SEO requirements. We guarantee stable operation of the chosen solution.
To avoid architectural mistakes, contact us. We'll evaluate your project and select the optimal solution. Get a consultation on multilingual setup — we'll find the best approach for your project.