> 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/getting-started.md).

# Getting Started

Install and configure the Weglot plugin for Craft CMS.

Weglot integrates with your Craft CMS site and makes it multilingual in a few minutes. Here is what it does:

1. It creates a URL for each language — for example `/fr/about` or `/es/about` — without creating any new entries in the Craft control panel.
2. On those URLs, it serves the translated content.
3. It adds a language switcher to your pages and injects the `hreflang` tags in the `<head>` for SEO.

### 1. Install the plugin

{% tabs %}
{% tab title="Plugin Store" %}
In the Craft control panel, go to **Settings → Plugins**, open the **Plugin Store**, search for **Weglot**, and press **Install**.
{% endtab %}

{% tab title="Composer" %}
From your project root, require the package and install the plugin:

```bash
composer require weglot/craft-translate
php craft plugin/install weglot
```

{% endtab %}
{% endtabs %}

### 2. Configure the mandatory settings

Open the plugin settings (**Settings → Plugins → Weglot**) and fill in the three required fields:

* **API Key** — your Weglot project key. If you don't have one, [create your account](https://dashboard.weglot.com/register?project=craft); a **Register on Weglot** button is also shown in the settings until a valid key is saved.
* **Original Language** — the source language of your Craft site (the language your content is written in).
* **Destination Languages** — the languages you want your site translated into, entered as a pipe-separated list, for example `fr|es|de`.

Save the settings. Weglot validates your API key, syncs your configuration, and the language switcher appears on your site.

{% hint style="info" %}
The **Original Language** and **Destination Languages** menus are populated from the 110+ languages Weglot supports, fetched live from your account.
{% endhint %}

{% hint style="success" %}
**Next step:** head over to [Plugin settings](https://developers.weglot.com/cms/craft-cms/plugin-settings.md) to control what gets translated — exclusions, dynamic content and search integrations — and to customize 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/getting-started.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.
