Sulu CMS ↔ Symfony Translation: Missing translation fallback behavior

Goal

Determine how Sulu CMS handles missing field translations when using Symfony’s Translation component, and whether the chosen strategy (default master language vs. empty string) aligns with best practices for SEO and user experience.

Constraints & Uncertainty

Sulu 3.x displays an empty string for untranslated fields, while Sulu 4.x falls back to the master language. The documentation does not specify the SEO implications of each approach, and the fallback can be overridden by both the sulu_language_fallback setting and Symfony’s fallbackLocale configuration. This ambiguity makes it difficult to decide on a consistent strategy across versions.

Specific Questions

• What are the SEO risks of showing the master language content for missing translations versus leaving fields empty?
• How does the sulu_language_fallback configuration interact with Symfony’s fallbackLocale when both are set?
• Should projects upgrade to Sulu 4.x or implement a custom override to enforce a uniform fallback strategy?