# Translate WordPress Posts to Any Language with DeepL

> Watch WordPress for posts in the source language, run the content through DeepL for high-quality translation, and publish the translated version back to WordPress.

- URL: https://www.automongo.com/automations/translate-wordpress-with-deepl/
- Summary: Pull WordPress posts, translate with DeepL, and publish the localized version back.
- Tools: Make
- Difficulty: Intermediate
- Category: Marketing
- Tags: wordpress, deepl, translation, content, localization
- Published: 2026-10-24
- External resource: https://www.make.com/templates/12178-translation-build

## How It Works

The Make scenario watches WordPress for new or updated posts, sends the title and body to DeepL for translation into the target language, and writes the translated post back to WordPress. Because DeepL handles formatting-aware translation, the output preserves headings, lists, and inline links from the source post without manual cleanup.

### Setup Steps

1. **Connect WordPress**: Add the WordPress connection in Make with REST API credentials that allow reading and writing posts.
2. **Connect DeepL**: Create a DeepL API account, generate an API key, and add it as a Make connection.
3. **Pick the Source and Target Languages**: In the DeepL module, set the source language (or let it auto-detect) and the target language code, for example `DE` or `FR`.
4. **Configure the Destination**: Decide whether translated posts should be published, drafted, or scheduled, and set the category and author in the WordPress create-post module.
5. **Activate the Scenario**: Turn the scenario on so every new post flows through DeepL and lands as a translated version in WordPress.

### Automation Workflow

```
WordPress (Watch New Posts) → DeepL (Translate Title + Body)
↓
WordPress (Create Translated Post)
```

### Benefits

- **Fast Localization**: Posts land in the target language within minutes of publication, not days.
- **Format Preserved**: DeepL keeps headings, lists, and inline links intact so the translated post renders correctly.
- **One Source of Truth**: Edit the source post and the scenario can re-translate, so copy edits propagate.
- **No Human-in-the-Loop by Default**: Translators can review drafts if the destination module writes posts as drafts instead of published.

### Use Cases

- SaaS blogs serving multiple markets who want localized versions of every post.
- Media sites republishing English coverage in European languages for regional audiences.
- E-commerce stores syncing product-launch posts across country sites.
- Nonprofits translating announcements for a multilingual membership base.

**Pro tip:** For a more systemic approach to localisation, check out [Tolgee](https://tolgee.io/).