Get started with AIRA translation prompts

Marketers spend a lot of time creating content that turns a first‑time visitor into a loyal customer. But if they just swap words between languages and call this content “translated”, all their effort can be ruined. A bad translation will not keep the intent, brand voice, and clarity intact, and all the work your team put in may be wasted.

With AIRA, they can evaluate the translated content and then adjust the prompt to improve translation quality. Once they nail the prompt, they can use it for every other translation which will reduce the need for retranslation. In short: better quality in, better quality out.

Translation optimization scenarios

You don’t need to be a localization expert. We’ll go through the best scenarios on how to steer AIRA’s translations toward your brand voice and requirements. You will learn how to write short, focused prompts that improve quality, speed up reviews, and keep terms consistent. Your main takeway should be:

• Translate with brand voice and approved terminology across your target languages.
  
• Prevent common AI translation pitfalls with do-not-translate (DNT) lists and glossaries.
  
• Speed up publishing time and reduce post-edit effort.

How AIRA uses ad-hoc translation prompts

When you start translation, AIRA uses a default Xperience translation prompt. You can, however, customize the default system translation prompt by providing additional translation context that will be scoped to your specific project requirments.

To achieve best results, keep your prompts brief and precise. Too much information given in a random, unstructured format will confuse the Large Language Model (LLM) that processes your translations on the backend. The more organized and clear you are in your prompt, the better your translation results will be.

These instructions influence the tone of voice, terminology, style, formatting, and SEO-related fields. You can also add DNT lists, or lists of forbidden phrases, which help AIRA determine how NOT to translate certain things. This is especially important in case of product names you might want to keep in the source language (like “FastTrack” in “FastTrack savings account” you can find in the Kbank demo project), or in cases where specific translations might be culturally inappropriate or sensitive.

You can instruct the model with clear prompts and give it well-defined boundaries similar to a creative brief, which helps AIRA make similar choices an editor would. Your prompts guide the model, but they do not override project settings or translate content that has been excluded from translation.