5 Pain Points Wagtail Users Face with Multilingual Sites

Wagtail CMS has solid building blocks for multilingual websites. It has a Locale model, TranslatableMixin , and i18n_patterns for URL routing. The wagtail-localize package adds translation workflows. It also supports machine translation. When I read Discussion #13693 , I noticed clear patterns. Maintainers and users shared their real-world experiences with i18n. Here are the five biggest pain points. 1. Links That Switch Your Language When you call .localized on a page, it should return the translated version. But if no translation exists, it returns the source-language page instead of None . This causes menus and links to switch the user into a different language. Many users reported this problem. One developer wrote custom _or_none methods to work around it. This should be built into Wagtail's core. 2. Sitemaps That Forget Other Languages Wagtail's sitemap generator only lists pages in the default locale. It does not add xhtml:link alternate entries or x-default values. This hurts SE