---
title: Automate your translations with AIRA
---

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

When your company expands to new markets, one of the first things your editors (or you) will have to do is to localize your content into local languages. Besides expanding your audience to users that may not be familiar with your source language, **addressing them in their native languages helps build trust in your brand**.

However, creating engaging messaging and running seasonal promotions while you are trying to maintain consistent brand messaging across several languages can quickly become a chore. More languages, more trouble, as they say.

[AIRA](https://docs.kentico.com/documentation/business-users/aira.md) helps you meet that challenge head-on by bringing content and translation together into one workspace.
With a translation capability **built directly into Xperience**, you don't need to constantly switch tools to manually copy the translations.
Instead, let AIRA handle the boring parts and translate your content automatically. This way, you'll gain more time and headspace to focus on keeping your unique tone of voice and personality intact.

In this guide, you’ll:

- Learn what AIRA automated translations can and can’t do.
- Prepare your environment for smooth translation workflows.
- Tailor AIRA translation settings to your needs.
- Try how AIRA translations work on a real-life campaign scenario.
- Pick up best practices for achieving consistent, high-quality translations.

## What AIRA automated translations can and can’t do

Before we dive into details, it helps to know what to expect from AIRA’s translation capabilities.
AIRA helps you translate content faster. One may argue that since it's automatic, every translation will sound the same, but this is not the case.

AIRA is powered by a [large language model (LLM)](https://en.wikipedia.org/wiki/Large_language_model), which uses advanced AI to understand context and meaning. You can then configure AIRA to respect your brand’s tone of voice by adding custom translation rules (called **prompts**) to generate natural-sounding translations for your text fields.

> **Info:** Our internal trials showed that using AIRA’s built-in translation feature can save up to 90% of translation time when compared to external translation tools with manual workflows. That means you spend less time copy-pasting text from one tool to another, and more time creating content and shaping campaigns.

### Currently supported AIRA functionalities

- Translation of _text_, _long text_, and _rich text (HTML)_ fields.
- Manually triggered automated translations and bulk (mass) translation from the [Content hub](https://docs.kentico.com/guides/digital-marketing/xperience-essentials/manage-content-hub-essentials.md) or the individual items.
- Optional tone of voice guidelines that help AIRA stay on brand every time.
- Custom translation prompts that reflect your terminology, cultural nuances, and preferences.

### Automated translation limitations to keep in mind

- Linked content items are translated manually in a cascade, and you choose which ones to include.
- Automated translation of taxonomies isn’t supported yet.
- Translation of content in hyperlinks is also not supported, so it is safer to always check links manually.
- AIRA will only translate the data types that are currently out-of-the-box with Xperience (custom developer-defined data types may require setup, so discuss this with your developers before starting work on your project).
- AIRA translates names of pages and items by default (you can not currently opt for keeping the name of a page or an item in the target language).
- The translation process runs asynchronously, in the background, so it may take a few moments before the translated content appears in the content type.

Understanding these boundaries upfront helps you plan realistic, efficient translation workflows that save both time and money.