Offer your hub in several languages
Updated September 17, 2026
Add a language to a hub, and its event cards follow.
What it’s for
A hub is a public address like any other, so it can be read in several languages: add a version, review the texts, and visitors get the translated hub at its own address, indexed by search engines as such.
Its event cards follow. A page you have already translated shows its translated name and summary on the card, and its registration form opens in that language too. A page you have not translated keeps its own: a hub never hides an event because it is not translated yet.
Open your hub. At the top right of the canvas, beside the device pill, the language pill names the language shown: the one the hub is written in.
Click the pill. The menu lists the source language, then each version with its status, then an “Add a language” group with one row per language the hub can still take. “Written in” at the bottom sets the language the hub itself is written in.
Add a language drafts the whole hub with AI. You review every text afterwards. Pick a version: the canvas shows the hub as its visitors will see it in that language, and the right panel becomes the translation overview — how far along it is, and each section with its own status.
Good to know
- Unlike a page, a hub is not tied to one event, so nothing tells it which language it is written in: you do. “Written in” holds that choice, and everything else follows from it — the address without a language suffix serves it, and the other versions are translations of it.
- Changing the language a hub is written in reframes every version. If one of them is already in the language you pick, it becomes the hub itself and stops being a separate version.
- Each language lives at its own address, such as /your-hub/fr, with its own canonical link and hreflang alternates. Visitors are never redirected: someone whose browser speaks another available language sees a discreet hint in the footer instead.
- To have a card show its translated name, translate the page itself: its event name and summary are part of what a page translation covers. Until then the card reads in the page’s own language, which is what its visitors would see anyway.
- An automatic collection can also filter on language, so one hub can gather only what you publish in a given language. “Same language as this page” makes one section list each language’s own events at that language’s address.
- Embedding a hub on your own site offers the same choice: the version you name, or the visitor’s browser language.
Related articles
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?