Avoid Using the WordPress Full Site Editor with WPML (for Now)

There is a lot of excitement in the WordPress world about the Full Site Editor. It promises flexibility, an entirely new way of designing websites, and the power of blocks everywhere. But if you are planning to build a multilingual site with WPML, I strongly advise against combining it with FSE right now.

The issue is not really with WPML itself. The deeper problem is that the Full Site Editor has not made any real provision for multilingual sites. The whole concept of language switching, translating templates, or maintaining consistent designs across different locales has simply not been accounted for in the way FSE is built.

When you place WPML on top of that, things start to crack. Translations can break layouts, templates may not sync properly between languages, and the overall editing experience quickly becomes frustrating and unreliable.

If you want a multilingual WordPress site today, the safer route is to stick with either the classic theme approach or established page builders that are known to work with WPML. Those solutions are far more stable and proven — and your business site will thank you for that reliability.

Maybe in the future WordPress will take multilingual needs seriously within FSE. Until then, the combination of WPML and the Full Site Editor is best avoided.

If you are unsure about the right setup for your multilingual WordPress site, get in touch with me.

And if you’re interested in the full opinion piece I wrote about this topic, then please follow this link to my other website. The article goes into a lot of (technical) details.

Photo by CHUTTERSNAP on Unsplash