# Translation

The frontend language of Content Egg can be different from your main WordPress language and admin dashboard language. Content Egg has its own setting for this:

* Go to **Content Egg > Settings > Frontend**.
* Set the **"Website Language"** option to choose the language used for the frontend display.

<figure><img src="/files/A3v8BGVj2wLQvNc6rMPU" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you only want to change a button label, go to **Content Egg → Settings → Frontend**, and update the **"Product Button Text"** or **"Coupon button text"** fields.
{% endhint %}

### **1. Quick Translation via Plugin Settings**

For most use cases, you can translate frontend strings directly in the WordPress dashboard:

* Go to **Content Egg > Frontend > Frontend Texts**.
* Modify the available strings to your desired language.

![](/files/-MTVwuZRSXWBXOkPmAz7)

{% hint style="warning" %}
**Note:**\
If a string includes placeholders such as `%s` or `%d`, make sure your translated version includes **the exact same placeholders** in the correct position. These are dynamically replaced with actual values and are essential for proper functionality.
{% endhint %}

### **2. Advanced Translation with POT Files**

For more comprehensive setups, you can use a traditional translation method with `.POT` files.

* This allows you to translate all plugin strings using tools like **Poedit** or **Loco Translate**.
* Detailed steps are provided in this guide: [Localistion with POT files](/customization/localization.md).


---

# 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://ce-docs.keywordrush.com/frontend/translation.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.