Multilingual Websites
Overview
Kanorio websites support multiple languages simultaneously. Once you write your content in the primary language and add a second language, the system translates the entire site and publishes it automatically. Each language has its own URL (e.g., /en/ for English), a language switcher appears in the header automatically, and all necessary SEO settings (sitemaps, hreflang) are handled for you. If you update the original content later, the system only translates the changed parts; any translations you have manually corrected in the editor will not be overwritten.
Translation does not consume AI credits. This feature is available on Free, Pro, and Business plans, with support for up to 10 languages per site (including the primary language). Headless websites can fetch content for different languages using the same API, following the same rules.
Adding a Language
- Go to "Site Settings › General" in your dashboard to view your primary language and any added languages in the "Site Language" section.
- Select the language you want to add from the dropdown menu and click "Add Language".
- After saving, the language will show a "Translating" status with progress (e.g.,
Translating 120/300). Visitors cannot see this language while it is being translated. Once complete, it will automatically switch to "Live," and the language switcher will appear in your header.
Translated content includes pages (all text blocks, SEO titles, and descriptions), blog posts, products (detailed descriptions, FAQs, purchase information, option names, and plan details), store shipping times and general purchase information, authors, courses and lessons (text content and quiz questions), categories and tags, header/footer menus, online forms, legal pages, and any fields in Collections marked as "Translatable." Prices, inventory, orders, customer data, and reviews are not translated.
| Status | What it means |
|---|---|
| Translating 120/300 | The site is being translated; visitors and the API cannot see this language yet |
| Live | Visitors can switch to this language |
| Paused, will resume tomorrow | Daily auto-translation limit reached; the rest will resume tomorrow, but you can manually edit in the meantime |
| Translation failed · 3 items missing | Some content failed to translate; select "Retry missing" from the "⋯" menu in the language list to translate only the missing parts |
| Not live | Added but auto-translation is off, or you haven't published it yet |
Correcting Translations
Translations are generated by AI and published immediately, so you don't need to translate page by page. If you need to adjust the wording, you can correct it in the editor:
- Enter the Site Editor, click "Correct Language" in the top toolbar, and switch to the language you want to edit.
- The screen will display the content in that language. Click directly on the text to modify it; changes take effect upon saving. When correcting other languages, you can only switch pages and edit text. To add, move, or delete pages, switch back to the primary language.
- SEO titles, descriptions, and social sharing text for each page can be corrected at the bottom of the screen. URL and indexing settings can only be modified in the primary language.
- If the original content is updated after you have made corrections, the system will mark it with "Original content updated, translation is outdated." You can click "Translate Now" to re-translate that page or edit it manually.
Fields you have manually corrected are remembered by the system. Future automatic translations will only update uncorrected parts and will not overwrite your custom wording.
Language URL Prefixes
Primary language URLs have no prefix (e.g., example.com/about-us), while other languages are placed in their own subdirectories. During translation, the system generates a URL slug for each page, post, product, and category based on the translated title (e.g., example.com/en/about-us). If the primary language slug is alphanumeric, languages that do not use Latin characters (like Japanese or Korean) will inherit it. Once a slug is generated, it is fixed; changing the title later will not change the URL. To modify it, open the SEO settings for the page, product, or category while in the correction mode for that language (for posts, this is at the bottom of the writing screen) and edit the "URL Path." If you change a live URL, the old one will automatically redirect to the new one. Leaving it blank will inherit the primary language URL. If a visitor opens a URL in another language or an old link points to the primary language, they will be redirected to the correct language URL. URL prefixes default to language codes (e.g., en, ja, zh-hant). You can change these to your preference (lowercase letters, numbers, and hyphens, 2–30 characters) by selecting "Change URL" from the "⋯" menu in the language list. If you change the prefix for a live language, old URLs will automatically 301 redirect to the new ones. For Chinese (Traditional, Simplified, and Hong Kong), we recommend keeping the full code (e.g., zh-hant) so visitors can distinguish between them.
Automatic Translation Toggle
Each language has an "Automatic Translation" toggle, which is on by default. Content in the primary language and any subsequent changes will be automatically translated into that language. If turned off, the system will stop translating automatically and will only mark content as "Original content updated" when the primary language changes. You can then translate it manually in the editor or click "Translate Now" page by page. This is ideal for sites where every sentence requires human verification.
Removing Languages and Changing the Primary Language
- Removing a language: Click "Remove Language" in the language list. Once a live language is removed, its URLs will automatically redirect to the corresponding pages in the primary language. Translated content is kept for 30 days; if you re-add the same language within this period, the previous translations will be restored, and only missing parts will be translated (if you customized the URL prefix, set it to the same one to restore the original URLs).
- Changing the primary language: If your site has only one language, you can change the primary language directly in "Site Language" (existing content will not be translated, so please check page by page). After adding other languages, changing the primary language will affect all site URLs; this operation is currently not supported.
What Visitors and Customers See
- A language switcher appears in the header automatically, allowing visitors to choose their language. The system does not automatically redirect based on the visitor's location (this is the recommended practice for SEO; see How Multilingual SEO Works).
- The language used by a customer during checkout, login, or form submission is remembered. Subsequent transaction emails, courses and order names in the Customer Center, and certificates will use that language. Unmodified notifications use the built-in system version; modified notifications are translated alongside site content and can be corrected by switching languages in the "Edit Content" page of the email (see Store Notifications).
- Your Brand Memory and AI-generated copy use the primary language; new AI-generated content is automatically translated into other languages.
- Website Backups in ZIP format include translations for all languages.
FAQ
No. Full-site translation when adding a language, automatic updates after original content changes, and the "Translate Now" feature in the editor all cost 0 credits. Each account has a daily limit for automatic translations; if reached, the remaining parts will continue automatically the next day.
Most sites are finished within minutes. Sites with many pages and posts may take longer, and the progress will be shown in the language list. Visitors cannot see the language until translation is complete, ensuring a consistent experience.
Full-site translation covers all published content. If you do not want to translate specific content, you can switch to that language in the editor and change the translation back to the original text. For Collections, you can choose whether to enable "Translatable" for specific fields.
Yes. The language list and translation management work the same way. Your frontend can fetch content for each language using the same API parameters. Developers should refer to the Developer Documentation.