--- title: Settings - Translation services --- > 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). You can access these settings in the **Settings** application under the **Content ->** **Translation services** category. | General | | | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Enable translation services | Enabling this setting allows users to create new language versions of pages and localize text values via [translation services](https://docs.kentico.com/13/multilingual-websites/configuring-translation-services.md). The available translation options are determined by the other settings in this category. | | Allow attachment translation | Determines whether the system submits page file attachments (without their [image variants](https://docs.kentico.com/13/developing-websites/managing-responsive-images.md)) for translation along with the main content of pages. | | Translation attachments file types | May be used to limit which attachment file types can be submitted for translation. Entered as a list of allowed file extensions separated by semicolons, for example: _txt;docx;pdf_
If empty, all types of attached files are included in page translations. | | Automatically import translated submissions | If enabled, the system automatically inserts translated content into pages when the data is imported into submissions.
**Warning**: This overwrites pages immediately when a service finishes the translations, without the approval of administrators.
With this setting disabled, users need to manually process completed translation submissions in the **Translations** application. | | Encoding to use | Sets the character encoding type for the XLIFF pages used to transfer translation data in and out of the system. For example: _utf-8_ | | Enable REST translation service | Enables or disables the translation REST service, which may be used to retrieve the data of pages and other types of objects in XLIFF format. It is also possible to import translated XLIFF data via REST.
The translation REST service is not affected by the general REST settings, which can be configured in **Settings -> Integration -> REST**. | | Manual translation | | | Translation submission export folder | Specifies the path of the folder in the file system where the service creates the zip packages with the translation source data (XLIFF files and instructions) when pages are submitted for [manual translation](https://docs.kentico.com/13/multilingual-websites/configuring-translation-services/human-translation-services-manual-translation.md).
If empty, the _\~/App\_Data/Translations/Export/_ folder is used. | | Translations import folder | Sets the path of the folder from which the system imports zip packages containing completed translations.
If empty, the _\~/App\_Data/Translations/Import/_ folder is used. | | Delete ZIP after successful download | If enabled, the system deletes the zip packages containing finished translations after importing the XLIFF data (the submissions can be managed in the **Translations** application). | | Translation via email | | | Translation submission recipients | Specifies the addresses to which the system sends translation assignments when submissions are created for the email service. You can enter multiple email addresses, separated by semicolons.
To assign different translator addresses for specific languages:
Open the **Translation services** application.
Create a **Clone** of the _Translation via e-mail_ service for each additional language.
Edit the services and enter the appropriate translator addresses into the **Translation submission recipients** property. This property overrides the **Default email sender** setting. | | Default email sender | When sending translation assignment emails, the system automatically sets the sender to the address of the user who submitted the translation. The value of this setting is used if no user address is available, for example in the case of translations submitted automatically or via the API. | | Microsoft Translator | | | API Key | Enter the _Authentication key_ of your Microsoft Translator subscription. See the [Microsoft documentation](https://docs.microsoft.com/en-us/azure/cognitive-services/translator/translator-text-how-to-signup) to learn how to obtain the key. | | Google Translator | | | API Key | Enter a valid _API Key_, used by the Google Translator service to identify the application's translation project. You can obtain the key from the [Google APIs console](https://code.google.com/apis/console/). | Related pages - [Configuring content for translation](https://docs.kentico.com/13/multilingual-websites/configuring-translation-services/configuring-content-for-translation.md)