Blog Sections Open
Planning XML and HTML Sitemaps for a Multilingual Babel Site
How to think about XML and HTML sitemap generation when a site has multiple language versions and shared content structure.
Multilingual sitemap generation raises a question that appears simple but affects both SEO and site structure: should every language get its own sitemap, or should the whole site share one?
The real decision
- one sitemap per language keeps language branches explicit
- a shared sitemap can be acceptable if URLs are already fully language-specific and the structure stays clear
What to optimize for
If the site has clearly separated language branches, separate sitemaps are usually easier to reason about and easier to validate. They also make it simpler to audit missing or broken language pages.
Recommended rule
Choose the sitemap strategy that matches the actual URL structure, not the one that only looks shorter on paper. In most multilingual projects, explicit language-aware sitemap generation is the safer path.
Using Rich Text Fields Inside ManagerManager Workflows
A manager UX note about what can go wrong when a ManagerManager-driven field uses rich text content and inline styles.
Changing the Default Language Context in a Babel-Based Site
A multilingual note on changing the default language in a Babel-style setup without rebuilding the entire site structure.