> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/app-features-and-settings/translate-app.md).

# Translate app

### I have translated my WordPress website using a plugin. Will my app appear in the same language?

The app you build on AppMySite will only support the default language set in your WordPress website’s settings. Content that’s synced from your website will appear as it is in your app.

In case the Language Support feature is active, your app’s native texts, buttons, and labels will be translated to the default language of your WordPress website. Keep in mind that your website’s content will be synced to the app without any change. Read how to translate your app to a different language

{% content-ref url="/pages/OXMJUlbDMWVyA2boazq0" %}
[Languages support](/frequently-asked-questions/app-features-and-settings/languages-support.md)
{% endcontent-ref %}

{% hint style="warning" %}
Your app users will have the option to switch languages within the app if the Language support feature is active. When you switch a language, only your app’s native buttons, texts, and labels will change. The website content will be synced as it is.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/frequently-asked-questions/app-features-and-settings/translate-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.