In the previous article, you’ve read about setting up multilingual on Kbank. Now, you can start translating the pages as needed.
Translating your company website helps you reach a broader audience and provide a better user experience, which leads to higher conversion rates.
Let’s see how to translate a page into your targeted language.
Watch a short video to see the whole translation workflow.
Want to test how translations work? Follow the rest of the guide to get a hands-on experience.
When translating a page, you need to know which one to pick so you don’t work on something already translated. Xperience by Kentico shows you the translation status at first glance. Just switch to the target language using the drop-down selector in the top left corner and see the icons next to the pages in the content tree:
When creating a language variant of a page, you’re preparing a base for the content you’ll translate later. You need to take care of things in the background before you prepare the content visitors see when they visit your website.
In this article, we’ll create a language variant of the Travel Guard Insurance page in the demo Kbank site.
SEO properties are an essential part of any web page. Translating SEO properties to the targeted language supports the page in local search engines, so the target audience can find it easier. On the other hand, not translating the SEO properties could promote the translated page to the audience of the fallback language.
For example, if your company's website is in English, and you decide to add a Spanish version but keep the SEO properties in English, the English audience can find the pages in Spanish. At the same time, the Spanish audience may miss the translated pages, and the number of visitors and potential conversions will be lower.
Let's first add some English SEO metadata to the TravelGuard Insurance product page.
You can use the following values:
If your company is active on social media to promote content, translate the Open Graph fields as well. If your developers implemented a custom connector app to share your content on your social media profiles, filling data in the OG properties creates a social media post, both the headline and the text, in the desired language.
Let's add OpenGraph content to the TravelGuard Insurance page to see how translation works. You can use the following values:
AIRA translations let editors quickly generate language variants of existing content without manual translation or external tools. You can translate pages (including their Page Builder content) and reusable content items in the Content hub.
When you start translating the page, AIRA creates a draft you can review, publish, or discard. The translation process is customizable within your Xperience application. You can define brand-specific terminology, exclude certain words, and set formatting rules in the AIRA application.
Let's translate the TravelGuard Insurance page.
URL is the next important thing you need to consider. If you leave the URL as is, which you can see in the example below, the URL includes the language prefix. Still, the URL slug is the same as in the original language. You can adjust the URL slug to match the page's targeted language.
After AIRA completes the translation, validate the output. Check for errors introduced by the language model, such as mistranslations, inconsistencies, or terminology that conflicts with your brand guidelines or technical standards. Pay particular attention to inappropriate naming conventions or phrasing that misrepresent your product or service.
You may have other fields to think about based on your project implementation in your Xperience application. Some fields are not text fields, so they don’t need to be translated, but it’s good to think about them.
For example, on our Kbank demo site, we have the Page publish date. You may want to decide whether to keep it the same as the original page or use a different date.
Now that you have translated or adjusted all the fields, save the page and review the translated content.
In our example, the page is a product page, so a product content type is linked directly to the page. However, not every page has a content item linked to the page itself; instead, content items are linked to the widgets.
As we mentioned above, the Kbank website we use in this example has a product page with the product linked directly to it. This means we’ll translate the product into the Content view. For other content items, we’ll switch to the Page Builder.
In the following guide, prepare the multilingual variant of a content item.