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

# Getting Started

Starting with the Weglot WordPress plugin

## Getting Started

### Introduction

Weglot has built a powerful WordPress plugin that integrates in your WordPress website and make it multilingual in a few minutes.

What does Weglot plugin do exactly ?

1. It creates URL for each languages, like `/fr/about/` or `/es/about/` for instance (but doesn't create actual pages in WordPress backend)
2. On these URL, it returns the translated content
3. It adds a language button on the page and the `hreflang` tags in the `<head>` section of your page for SEO.

### Getting started

To start, install [Weglot Translate](https://wordpress.org/plugins/weglot/) plugin directly from the directory.

In the settings page, configure the 3 mandatory settings :

* **API Key** : You get an API key in your account. If you don't have one, you can [create your account](https://dashboard.weglot.com/register-wordpress).
* **Original Language** : The original language of your WordPress website.
* **Destination Languages** : The languages you want your website to be translated into.

Save the settings and you are done. You will see the language button appear on your website.

{% hint style="success" %}
**Next step:** head over to [Plugin settings](/cms/wordpress/plugin-settings.md) to control what gets translated (emails, search, specific URLs or blocks) and 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/wordpress/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.