> For the complete documentation index, see [llms.txt](https://developers.weglot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.weglot.com/cms/craft-cms/plugin-settings.md).

# Plugin settings

Configure the Weglot plugin from the Craft control panel.

The plugin's settings live in the Craft control panel under **Settings → Plugins → Weglot**. A few options are configured here; the more advanced translation options are managed from your Weglot dashboard and are reachable through buttons on the same screen.

### Main settings

These three fields are required to make your site multilingual. See [Getting Started](https://developers.weglot.com/cms/craft-cms/getting-started.md) for the full setup walkthrough.

* **API Key** — your Weglot project key. It is validated against your Weglot account when you save.
* **Original Language** — the source language your content is written in.
* **Destination Languages** — the languages your site is translated into, as a pipe-separated list (for example `fr|es|de`).

### Dynamic content

* **Enable dynamic content** — translates content that appears after the initial page load (menus, pop-ups, content injected via JavaScript or AJAX). Off by default.
* **Whitelist selectors** — CSS selectors marking the DOM regions that should be translated dynamically.
* **Allowed URLs** — restrict dynamic translation to specific URLs. Leave empty (or use `all`) to run it on every page.

{% hint style="info" %}
Dynamic content translation can also be extended from your own plugin through Craft events — see the **Use cases** section.
{% endhint %}

### Integrations

* **Algolia** — when enabled, Weglot reverse-translates Algolia search queries so results match your source-language index while your visitors search in their own language.

### Managed in your Weglot dashboard

Some options are not stored in Craft — they live in your Weglot dashboard and open from buttons in the plugin settings:

| Option            | What it controls                                            |
| ----------------- | ----------------------------------------------------------- |
| Translations list | Browse and edit every translation of your site.             |
| Block exclusion   | Exclude content blocks or CSS selectors from translation.   |
| URL exclusion     | Exclude specific URLs, pages or languages from translation. |
| Visual Editor     | Edit translations directly on a live preview of your site.  |
| Switcher Editor   | Design and position the language switcher.                  |
| Language model    | Choose the translation engine used for your project.        |

{% hint style="success" %}
**Next step:** see the **Use cases** guides to customize translation behavior — exclusions, dynamic content, search integration and the language switcher.
{% 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://developers.weglot.com/cms/craft-cms/plugin-settings.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.
