Core Features
Multilingual from Day One
Every language gets its own paths, content and hreflang. You're not translating one site; you're running multiple indexable entry points.
Going multilingual isn't just translating the UI. The hard part is making each language's content discoverable and indexable by the right regional search engine. gcms is designed for that, from routing to SEO.
One language, one path
/zh/…, /en/… — each language gets its own URL prefix, and can even use its own slugs. Clean to share, clean to index.
Content maintained per language
Versions of the same article are linked by a translation group, so you edit and publish each independently. Not translated yet? That page simply doesn't appear in that language — no half-finished stubs.
hreflang, automatically
Every page emits hreflang alternates (including x-default), telling search engines which language versions exist — avoiding duplicate content and routing traffic to the right language.
Custom locales too
A set of locales ships built in, and you can add any locale from the admin — a new language without a line of code.
Default language is a fallback
The default language is a fallback rule, not a forced redirect. If the visitor's browser language is outside your enabled locales, gcms falls back to the default; if the URL already says /zh/ or /en/, the path wins. That is calmer for users and clearer for search engines.
The page you're reading has a Chinese version. Try the language switcher, top right.