SlyTranslate brings AI translation into WordPress for site owners who publish in multiple languages or want to speed up translating existing content.
It works at three levels: from the admin screens, inline inside the Gutenberg editor, and through MCP abilities that let external LLM tools drive translation tasks directly. It is built for anyone running a multilingual site who wants translation handled without copying content between apps.
For admin and Gutenberg translations, SlyTranslate relies on a WordPress AI connector, which means the site owner connects an account with an AI provider and SlyTranslate sends content to whichever language model that connector points to.
Results appear directly inside the post or page being edited, or as new translated entries created through the active language plugin. In the MCP workflow, the translation itself is produced by the external LLM tool, such as Claude Code or Codex, while SlyTranslate handles reading and writing the WordPress content.
The plugin integrates with Polylang, WP Multilang, WPGlobus, and TranslatePress Multilingual, so it fits into whichever multilingual setup a site already uses rather than requiring a new one.
Powered by Fabio ChatBot
Is SlyTranslate yours?
Tell readers what is limited and unlimited in the free version, and what the AI does in your plugin. Help them decide faster and reach the people already looking at it. In return, you answer their questions.
Key Features of SlyTranslate
Admin translation for posts and pages. Translate full posts, pages, and custom post types from the editor side panel or in bulk from the list view, with a dialog to pick the target language, model, and whether to overwrite existing translations. Progress is shown live and a running job can be canceled.
Inline Gutenberg translation. Select text in any block to get a Translate button in the block toolbar, replacing the selection or the whole block with its translation in place. This works without a language plugin, which suits quick corrections or translating imported content on the fly.
MCP abilities for external LLM tools. SlyTranslate exposes its translation functions as MCP abilities once a WordPress MCP Adapter is active, letting MCP-capable tools like Claude Code or Codex read content, check translation status, and write translated entries programmatically. In this workflow the external tool supplies the translation itself.
SEO metadata carried along. Title and description fields from supported SEO plugins are translated in the same pass as the post content, so translated pages keep their metadata without a separate step.
Automatic custom field translation. Text, textarea, and rich text fields from Advanced Custom Fields, Meta Box, and Pods are detected and translated automatically when those plugins are active, including ACF Repeater and Flexible Content layouts and ACF blocks inside Gutenberg. No setup is needed for this to work.
Reliable handling of long content. Longer or structured content is split into chunks and the output is validated, which helps keep translations consistent across lengthy posts rather than failing or truncating.
Tuned profiles for known model families. Built-in profiles adjust prompt style, chunking, and retry behavior for specific model families such as Qwen, Gemma, Phi, EuroLLM, and Ministral, while any model available through a connector still works without extra configuration.
Background bulk translation. Bulk translation jobs can be queued to run in the background via Action Scheduler or WP-Cron, so they continue even if a browser tab is closed, with progress that can be polled and canceled.
How to Install SlyTranslate
Step 1: Install the plugin. In the WordPress dashboard, go to Plugins > Add New Plugin, search for SlyTranslate, then click Install Now followed by Activate.
Step 2: Connect an AI provider. Go to Settings > Connectors and set up an AI connector so SlyTranslate can send content for translation; API keys are entered here rather than in SlyTranslate itself.
Step 3: Add a language plugin if needed. For full post and page translation, install and activate Polylang, WP Multilang, WPGlobus, or TranslatePress Multilingual. This step can be skipped if only inline Gutenberg translation is needed.
Step 4: Enable MCP access if desired. To drive translations from external LLM tools, install and activate a WordPress MCP Adapter so SlyTranslate’s abilities become available to MCP-capable clients.
Step 5: Start translating. Use the side panel or bulk action on the post and page list to translate existing content, or select text in the Gutenberg editor and use the Translate button that appears in the block toolbar.
Good to Know About SlyTranslate
According to the plugin’s documentation, ACF, Meta Box, and Pods fields are detected and translated automatically once those plugins are active, with filters available to include or exclude specific field types or keys. The FAQ also notes that content translation workflows require a supported language plugin, while inline text and block translation work without one.
API keys are entered under Settings > Connectors rather than inside SlyTranslate. Prompt behavior can be adjusted through the plugin’s settings page or per request, and a glossary setting allows brand names or fixed terms to be kept untranslated or mapped to set translations.
Download SlyTranslate on WordPress.org