Shared page identity and translated URLs

Documentation / Languages and translations

Modern Beeboo translations use the same pageId as their source. The language identifies the version; the URL identifies where that version appears publicly. Two translated titles therefore do not need matching slugs to remain connected.

Understand the stored and public paths

Translated page content is stored in the relevant language area under the shared page identity. For blog and tree items, the stored path can be a relative slug. The engine computes the public address using the language prefix, collection base path, and any tree ancestors.

For example, a collection prefix can be localized separately from the article slug. The final translated address can differ in several segments while still representing the same source page.

Do not create a second unrelated page merely to translate its title. That loses the identity relationship used by language navigation and search alternates. The system can read older explicit translation-source references for compatibility, but new translations use shared identities.

Use stable internal links

Use page-picker destinations where available. Internal page links are stored as page references and resolved to appropriate public URLs. Typed human-readable addresses are more vulnerable to later slug or hierarchy changes.

Changing a translated slug does not automatically repair external bookmarks or links on other websites. Add and test redirect rules when an established public address changes.

Validate identity and address together

Open both versions and use the language selector in each direction. Check the translated listing link and the canonical address. For a nested tree page, verify the full ancestor path rather than only the item's own slug.

See Collections and content trees, Pages and navigation, and Search visibility and sharing.