# Language per Domain

We've added TranslatePress integration in order to seamlessly allow users to navigate between different domains attached to each language. Here's a quick video going over how to set it up or feel free to read the guide below:

{% embed url="<https://www.youtube.com/watch?v=BQfjcVNEiRo>" %}
Setting Up Language Per Domain with Domain Mapping System + TranslatePress
{% endembed %}

All you have to do is enable the PRO version of Domain Mapping System along with the TranslatePress plugin, and then this dropdown box will appear for each domain you have configured in the mapping settings:

<figure><img src="/files/2p7wEFkdq6EcupVyHBaD" alt=""><figcaption><p>Language per Domain</p></figcaption></figure>

This dropdown allows selecting a specific language that will be mapped to the domain.

{% hint style="warning" %}
It is up to you to ensure the content you are mapping has translations available in order for them to display. E.g. - TranslatePress uses "string translation" - whereby it does not create a new post or page for each language. You just need to ensure you have gone through the process of translating the strings on each post/page you are mapping.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://domainmappingsystem.gitbook.io/domainmappingsystem-docs/features/language-per-domain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.