---
title: Multilingual variant of a product
---

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

Translating your content gives users a smooth experience and prevents [the pages you create](https://docs.kentico.com/guides/digital-marketing/work-with-websites/Create-a-new-product-page.md) from mixing different languages. It also helps your pages perform well both on the surface (what visitors see) and behind the scenes, supporting areas such as SEO and accessibility in the markets where you operate.

Xperience by Kentico translates content automatically using [AIRA-powered translations](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/automate-translations-with-aira.md). Triggering AIRA on a page translates the page's own content and cascades through every linked content item, so you rarely need to type out a translation by hand.

If you work with content in the _Content hub_ and display it in channels such as pages or emails, the following steps show how to translate reusable content. We'll use a **product page** and a **content item** stored in the [Content hub](https://docs.kentico.com/documentation/business-users/content-hub.md), where most reusable content is maintained.

> **Info:** **Prerequisites:**
>
> If you want to follow along, make sure you:
>
> - Have the **Kbank demo site** set up and running to test the scenario. You can request it by choosing _Xperience by Kentico - Business Tutorial Kbank demo site_ [on our website](https://www.kentico.com/customers/educationcenter/training-website-requests).
> - Know what [multilingual content](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/multilingual-variant-of-content.md) in _Xperience by Kentico_ means and how it works.
> - Know how to create a [language version of a page](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/multilingual-variant-of-page.md).
> - Have access to the _Content hub_ application, and have your target languages already set up in the [Languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) application.
> - If you also want AIRA to follow your brand's tone of voice, check the setup steps in [Automate your translations with AIRA](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/automate-translations-with-aira.md).

## Translate the content

Let's see where you can find the content you need to translate. There are two main groups of content you could be translating on your site: **reusable** (or structured) and **unstructured**.

Xperience stores the **reusable content** in the _Content hub_, and you can **link it to as many places as you want** (if the chosen widget supports the content type). _Content hub_ is also the default place to store any reusable media and assets you upload, since the standalone **Media library** feature has been retired.

**Unstructured content** is used in a **specific place**, and your team can reuse it elsewhere, but only with considerable effort.
As for the translation process, AIRA translates text, long text, and rich text fields wherever they appear. On the page itself, in its Page Builder widgets, and in any linked content items, including items linked to those items (like the product's **Benefits** and **Features**). Triggering the translation once, on the page, cascades through all of it.

You'll see both content groups translated in our example Kbank _TravelGuard Insurance_ page: unstructured Page Builder widgets sit directly on the page, and a product content item is referenced from the _Content hub_.

A few things still might need a manual touch-up after the automated pass, however. Some taxonomy tags aren't translated automatically, links inside rich text need a manual check to make sure they point to the correct language variant, and **forms** must be translated separately in the [Forms](https://docs.kentico.com/guides/digital-marketing/work-with-forms/forms-application-overview.md) app (AIRA currently does not support form translation).

### 1. Find the untranslated content

How can you tell which content has not been translated yet? You don't have to search the item by item; the page you're translating will tell you right as you switch to the target language variant:

![Untranslated content item on the product page](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/not-translated-page.png "Untranslated content item on the product page")

As shown in the example below, untranslated content items – like the product item we're translating in our example – are also marked as untranslated content in _Content hub_.

If you hover over the "not translated" label, Xperience informs you that the item has not been translated. You can also see a small _Not translated_ icon next to the label. If you publish the page now, it will show the product content item in the [fallback language](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/setting-up-multilingual.md#fallback-languages).

![Untranslated content item in Content hub](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/not-translated-product.png "Untranslated content item in Content hub")

### 2. Translate the product with AIRA

You have two options when translating a product item. You can either translate it along with the product page where the item is referenced, or you can translate the item alone, directly from _Content hub_.

#### Translate the product page

In Kbank's **Personal Banking** channel, open the _TravelGuard Insurance_ page and switch the language selector to your target language to create the new variant. Then select **Translate using AIRA**.

![Selecting Translate using AIRA on the TravelGuard Insurance page](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/translate-with-aira-option.png "Selecting Translate using AIRA on the TravelGuard Insurance page")

This single trigger cascades the automated AIRA-powered translation through the following:

- The page's fields and Page Builder widgets (including unstructured content, such as the _Page heading widget_).
- The product content item referenced by this page.
- The items linked to the product, such as **Product benefits** and **Product features**. You can choose which linked items to include in the translation before confirming, but we recommend keeping all of them selected.

![Selecting linked items to include in the AIRA translation cascade](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/linked-items-selected-for-cascade-translation.png "Selecting linked items to include in the AIRA translation cascade")

> **Info:** Leaving a linked item unselected means it stays untranslated, which can lead to missing text or broken functionality once the page goes live in the target language.

Because several items are being translated together, the request is sent for processing to the _Translation queue_. This may take some time, especially if the product has many linked items. But you can keep working on other tasks while the translation finishes in the background.

![Page and product translation processing in the Translation queue application](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/aira-translation-in-progress.png "Page and product translation processing in the Translation queue application")

#### Translate the product item

In case you need to translate the product item as a standalone, you can do so directly from _Content hub_.
Locate your item, use the language selector to switch to the desired language, and open the item to access the translation dialogue.

![Translate the TravelGuard Insuarnce product item](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/translate-with-aira-product-item.png "Translate the TravelGuard Insuarnce product item")

After choosing the **Translate with AIRA** option, follow the same process as you would with a product page. Keep linked items selected for translation, and wait for the translation to finish.

### 3. Review the translated product

Once the translation is ready, you can check the results:

- in a product widget on the page itself,

![Reviewing the AIRA-translated product on product page](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/review-aira-translated-product-on-page.png "Reviewing the AIRA-translated product on product page")

- and in the product content item in the _Content hub_.

![Reviewing the AIRA-translated product in Content hub](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/review-aira-translated-product-in-content-hub.png "Reviewing the AIRA-translated product in Content hub")

AIRA aims to produce a natural, ready-to-publish translation, but it's good practice to review it and manually adjust anything AIRA couldn't process before you publish. For example, taxonomy tags in the product, links inside rich text fields, or any custom field types your developers haven't [configured for AIRA translations](https://docs.kentico.com/documentation/developers-and-admins/configuration/aira-configuration.md) are candidates for a manual review.

> **Info:** When the AIRA translation finishes, but you can still see part of the product content item, one of its linked items, or a Page Builder widget in the fallback language, it means that the field wasn't automatically translated. That means you need to translate it manually to complete the language variant. Keep in mind that unstructured content has no fallback language variant.

### 4. Think about additional settings

Based on your project implementation, there may be additional settings you'd need to pay attention to. For example, the Kbank demo site shows that editors can use **the taxonomy feature to specify a language region**, so visitors see the language variant of the content. It's an example of a product content item marketers may find useful when promoting their products to multilingual audiences.

> **Info:** Limiting product availability per market or language via taxonomies is a custom-implemented feature for the Kbank project and is not an out-of-the-box Xperience feature.

![Select a region where the content in a specific language is accessible](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/content-regional-availability.png "Select a region where the content in a specific language is accessible")

### 5. Publish the product and its linked items

Don't forget to publish the new language variant you just created and translated. When you publish the product page, the cascade publishing dialogue opens and lists every linked item that isn't published yet, including the product content item and its own linked items. These are listed but **not selected by default**. Use the multi-select checkboxes at the top of the list to select them all before confirming.

![Selecting the page's linked items for publishing](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/cascade-publishing-dialog.png "Selecting the page's linked items for publishing")

> **Info:** If you publish the page without selecting its linked items, the page goes live, but the product content item (and anything linked to it) stays _Unpublished_, so it won't display correctly on the live site in the target language.
> In the live page preview, the content may appear translated, but that's because the page **Preview tab** shows all current items on the page, published or unpublisehd. Only the published items will show on the live site.
>
> Selecting linked items for publishing is the one step that stays manual, so it's worth double-checking each time.

Once published, the _Not translated_ label changes to _Published_ for the page, the product, and every linked item you selected.

![Content item that was translated and published](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/published-content-item.png "Content item that was translated and published")

### 6. Preview the result on the live page

Finally, check that the page and the product display correctly in the target language by previewing the live _TravelGuard Insurance_ page.

## To sum up

Remember that your webpage contains **data that is not directly visible** when you preview the web page. Page SEO properties, such as title or description, or image alt tags, all **play an important role in how your multilingual content performs on the target market**. Triggering AIRA once on a page cascades through its widgets and every linked content item, but always review the result, and manually finish anything AIRA couldn't process (like taxonomy tags or links inside rich text fields). And don't forget that publishing still requires you to manually select the linked items in the cascade publishing dialogue.

Lastly, but most importantly, any parts of the reusable content items you haven't translated will appear in the fallback language variant if your project relies on fallbacks, or won't show at all if no fallback variant exists. The unstructured content has no fallback language variant.

## Practice exercise

Let's apply the previously gained knowledge in the following exercise. You'll use a single AIRA trigger to translate a page, its product, and the product's linked items together.

To follow along with the exercise, you need a running Kbank demo site.

### Task

Choose the **German** language and create the language variant of the _Electric car_ loan page in the **Personal Banking** channel, including the product content item it displays.

### Hint

If you need a little help, here are the steps you should take:

1. Find the **Electric car loan page** in the content tree.
2. **Select the target language** (of your choice) in the drop-down menu above the content tree.
3. Select **Translate using AIRA**.
4. When prompted, **select the linked items** you want to translate, the featured product content item, and its own linked items (such as benefit items and feature items). Keep all of them selected so nothing is missing on the live site.
5. Wait for the translation to finish (you can check the _Translation queue_ application at this point).
6. **Review** the result, both on the page and on the product content item in _Content hub_.
7. Check that everything is translated, including the unstructured content items in the Page Builder (rich text widgets, page heading widgets).
8. **Manually finish** anything AIRA didn't cover. For example, validate the **Regional availability** field to see if your target country is included in the tags and add it if not, and adjust any rate or amount fields based on the target country's rules and currency.
9. Save and **Publish** the page. In the cascade publishing dialogue, be sure to **multi-select all linked items** as well. They're listed but not selected by default, so you need to select them manually to ensure they publish with the page.

Here is the final page compared to the one in the fallback language:

![German language variant of a page](https://docs.kentico.com/docsassets/guides/multilingual-variant-of-product/multilingual-final-page.png "German language variant of a page")