---
title: Translate pages
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

Before you can translate individual pages in your project into other languages, you need to set those up in the **Languages** application. For detailed info on how to configure multiple languages in Xperience, see [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md).

Afterwards, you can start to translate and create language variants of your pages:

1. Open the website channel where you want to translate pages.
2. In the header bar, open the language switcher.

   ![Language switcher in header bar](https://docs.kentico.com/docsassets/documentation/translate-pages/header_bar_language_switcher.png "Language switcher in header bar")

   > **Info:** The language switcher is available only if two or more languages are set up.
3. Select the language to translate pages into.
4. Select the page to translate.

   > **Tip:** Untranslated pages are visually marked by the _Not translated_ () workflow status.
5. Enter the translated page name. You can now choose one of the following options:

   - **Copy content from another language** is the preselected option. By default, the closest language in the [fallback chain](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) is preselected. You can choose a different language from the drop-down list. This option lets you prefill the content fields with the content available in the chosen language. If a linked item does not have a translated or published version, a warning will be displayed, and a fallback language variant of the item will be used.
   - **Create empty page** allows you to create an empty page with blank fields. Linked items need to be re-linked into the new language variant of the translated page.
   - **Translate using AIRA** see [Translate using AIRA](#translate-using-aira) for more information.

   ![Page translation](https://docs.kentico.com/docsassets/documentation/translate-pages/translate_page.png "Page translation")
6. Select **Continue**.
7. Enter the translated values of the page's fields.
8. **Save** the translated page.

You have now successfully translated the page. Note that the particular language variant is now only a _Draft_ and won't be accessible on the live site until you [publish](https://docs.kentico.com/documentation/business-users/website-content/edit-and-publish-pages.md) it. Until you do so, the language variant in the fallback language will be displayed.

If [content locking](https://docs.kentico.com/documentation/business-users/content-locking.md) is enabled, the page is now locked and only you can edit it. Variants created via _Translate using AIRA_ are locked only once you start editing.

> **Info:** Translated content items on untranslated pages are loaded in the fallback language. However, there is an exception in case the content items are injected into the page via code. In that case, content items are loaded in the language variant according to the requested language. For more information on language fallbacks, see [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md).

## Translate using AIRA

When you choose **Translate using AIRA** and start the translation process, the name and content of your page, including [Page Builder](https://docs.kentico.com/documentation/developers-and-admins/development/builders/page-builder.md) content, will be translated using [AIRA](https://docs.kentico.com/documentation/business-users/aira.md).

The translation workflow changes depending on the number of items submitted for translation. For a single item, AIRA creates a new language variant of the content in the _Draft_ state and immediately takes you to it.

However, when translating multiple pages at once (for example, when translating pages along with their linked content), your content is sent to a _Translation queue_. This allows the translation to be processed in the background, freeing you up to continue your work. You can check on its progress in the _Translation queue_ application. Once the translation of your content finishes, the related items are removed from the _Translation queue_ application.

The behavior of the translation can be [configured](https://docs.kentico.com/documentation/developers-and-admins/configuration/aira-configuration.md#configure-aira-translations), allowing you to specify, for example, formatting rules or brand terminology.

> **Note:** Existing text links to the translated content are not redirected to the new variant or translated automatically and need to be manually reviewed to ensure they lead to the correct content.