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.
Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal
Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.
What are the key benefits of headless CMS over monolithic?
Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.
How to choose a headless CMS for your project?
No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.
Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.
Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.
Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.
Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.
Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.
| CMS |
Hosting |
API |
Best Use Case |
| Strapi |
Self-hosted / Cloud |
REST, GraphQL |
Startups, customization |
| Directus |
Self-hosted / Cloud |
REST, GraphQL |
Wrapper for existing DB |
| Sanity |
Cloud |
GROQ, GraphQL |
Media, complex content |
| Contentful |
Cloud |
REST, GraphQL |
Enterprise, localization |
| Drupal |
Self-hosted |
JSON:API, GraphQL |
Government, complex permissions |
Consequences of poor content modeling
Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.
How we build projects on headless CMS
Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.
Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.
Implementation process broken into stages:
- Content needs audit — collect all content types, relationships, localization requirements, integrations.
- Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
- CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
- Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
- Content migration (if legacy) — automated loading via API or scripts.
- Testing — check API endpoints, regression, load testing, Core Web Vitals.
- Deployment — configure CDN, SSL, CI/CD, monitoring.
How long does implementation take?
The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:
| Project Type |
Timeline |
| Simple site on Strapi + Next.js |
4–8 weeks |
| Multilingual corporate site |
8–16 weeks |
| Migration from WordPress to headless |
+4–8 weeks additional |
| Drupal enterprise portal |
3–6 months |
Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.
Non‑obvious considerations when choosing a headless CMS
- Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
- Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
- Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
- Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
- Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.
What is included
- Data schema and API documentation (Swagger/OpenAPI)
- Configured admin panel with access rights
- Editor training (2‑hour session)
- Test environment during development
- 1‑month warranty on bugs after launch
- Post‑release support (including hotfixes 24/7)
Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.
