Missing translations and fallback behavior

Documentation / Languages and translations

Beeboo does not apply one universal fallback rule to every multilingual feature. Page routing, navigation, listings, and metadata each handle missing translations differently.

Page and navigation behavior

A translated public address needs an actual matching page. Blog and tree routing select content for the requested language, and an unresolved address can return a missing-page response. The public language selector omits choices without a usable target rather than promising to generate a version on demand.

Navigation uses translated destinations where available. Some unmatched navigation links retain their original source-language address and label. That can keep a link usable, but it can also move readers out of their chosen language. Test the menu rather than assuming it hides every untranslated page.

Listings and metadata

Blog and tree listings select items in the current language. A sparse translated listing may mean that only a few items have been translated. It does not necessarily indicate lost source content.

Secondary-language descriptions do not borrow the main-language site description. The engine uses page-specific description candidates and localized site copy; if suitable localized text is absent, it can omit the description tag and leave snippet selection to search engines.

Fill the gaps

Use page translation controls for individual pages or Translate missing in the language settings for absent versions. Review shared content and collection introductions as well as articles. Protect reviewed versions before considering any broad replacement action.

Validate from a visitor's route

Open the translated homepage, follow navigation into a collection, and switch between page versions. Inspect the final URL, visible language, listing contents, and metadata.

See Search visibility and sharing and Saving, recovery, and troubleshooting.