---
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. Translating a page doesn't create a new page in the content tree. Instead, it adds a _language variant_ to the existing page. Each language variant has its own content, URL, and [Page Builder](https://docs.kentico.com/documentation/business-users/website-content/widgets-and-page-builder.md) content, and you publish it separately from the other language variants.

> **Info:** Translating pages is different from localizing the administration interface. For information about how developers translate the administration interface into other languages, see [Translate the admin UI](https://docs.kentico.com/documentation/developers-and-admins/customization/admin-ui-localization/translate-the-admin-ui.md).

To translate a page, create its language variant with the `create_web_page_language_variant` tool of the [Management MCP server](https://docs.kentico.com/documentation/developers-and-admins/api/management-api.md). Pass every field value in the target language, because nothing is copied from other language variants. The tool publishes the new variant immediately, so visitors see it right away instead of the fallback-language version. To translate content items, use `create_content_item_variant` the same way.

> **Info:** Content items linked on a page that is shown in a fallback language are also loaded in the fallback language, even if they are translated into the language the visitor requested. 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.

The new language variant keeps the [AI content marking](https://docs.kentico.com/documentation/business-users/aira.md#ai-content-marking) of the original page's fields. Translation alone doesn't mark a field.

> **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.