內容簡介
SlyTranslate 是一款將 AI 翻譯功能整合至 WordPress 的外掛，支援多種語言插件，提供高品質的翻譯控制。無論是在管理介面、Gutenberg 編輯器，或是透過外部 LLM 工具，都能輕鬆進行翻譯，提升網站的多語言能力。
【主要功能】
• 支援將文章、頁面及自訂文章類型翻譯成多種語言
• 直接在編輯器內翻譯選定文字或整個 Gutenberg 區塊
• 自動翻譯 ACF 自訂欄位，無需額外設定
• 提供 SEO 元資料的翻譯功能
• 支援長內容的分段處理及輸出驗證
• 可調整模型特定的提示風格及重試行為
外掛標籤
開發者團隊
② 後台搜尋「SlyTranslate – AI Translation Abilities」→ 直接安裝（推薦）
原文外掛簡介
SlyTranslate wires AI translation into WordPress at three different levels: the admin UI, the Gutenberg editor, and from external LLM tools via MCP. Whichever level you work at, the same language plugin integrations and translation quality controls apply.
It works with any LLM available through a WordPress AI connector and natively supports Polylang, WP Multilang, WPGlobus, and TranslatePress Multilingual.
What it does
Translates posts, pages, and custom post types into any language managed by your active language plugin
Translates selected text or entire Gutenberg blocks inline, without leaving the editor
Exposes the same functionality as MCP abilities, so external LLM tools (Claude Code, Codex, and others) can drive translations programmatically
Carries SEO metadata (title, description) through the same translation workflow as the post content
Translates custom fields from ACF (including ACF blocks and options pages), Meta Box, and Pods automatically — no configuration required when the field plugin is active
Handles long and structured content with chunking and output validation
Supports model-specific profiles that tune prompt style and retry behavior for known model families
Workflow 1 — Admin UI translation (posts & pages overview, side panel)
Translate full posts or pages directly inside WordPress admin — either one at a time from the editor side panel or in bulk from the list view.
Requirements: language plugin + configured AI Connector
From the post/page list, select one or more items and choose a translation action from the bulk-actions menu. A dialog lets you pick target language, model, and whether to overwrite existing translations. Progress updates live while the translation runs, and you can cancel at any time.
From the editor side panel, the same controls appear alongside the post you are currently editing. TranslatePress users get an equivalent panel inside the TranslatePress visual editor on ?trp-edit-translation pages.
The language plugin (Polylang, WP Multilang, WPGlobus, or TranslatePress) handles the translated post as it normally would — SlyTranslate creates or updates the translated entry and lets the language plugin own the relationship.
Workflow 2 — Inline Gutenberg translation (block or selected text)
Translate content while writing, without touching a language plugin or a full-post workflow.
Requirements: configured AI Connector
Select any text in a Gutenberg block and the block toolbar gains a Translate button. The selected text is replaced with the translation in place. When no text is selected, the button translates the entire block.
This workflow is self-contained: it does not require a language plugin and does not create or modify translated post entries. It is useful for one-off corrections, translating imported content on the fly, or working in a single-language site where you just need AI rewriting in another language.
Workflow 3 — LLM wrapper via MCP (Claude Code, Codex, and others)
Drive WordPress translations from inside your LLM tool of choice.
Requirements: language plugin + WordPress application password (token) + WordPress MCP Adapter plugin
When a WordPress MCP Adapter is active, SlyTranslate registers its abilities over MCP. Any MCP-capable LLM client — Claude Code, Codex, custom agents — can then discover and call them.
In this workflow the LLM wrapper provides the translation itself. SlyTranslate’s MCP abilities handle the WordPress side: reading content structure, checking translation status, writing translated entries, and coordinating with the language plugin. No WordPress AI Connector is needed because translation is performed by the external model, not by WordPress.
A typical agent session:
Call ai-translate/get-languages to find valid target language codes.
Call ai-translate/get-translation-status on the source post to read source_language and single_entry_mode.
Translate the content using the agent’s own LLM.
Call ai-translate/translate-content to write the translated entry.
This is the right workflow for automating bulk site migrations, integrating translation into a CI/CD pipeline, or building a custom translation agent that uses a model not available as a WordPress AI connector.
Internal flow
┌──────────────────┐ ┌───────────────────┐ ┌────────────────────────┐
│ Admin UI │ │ Gutenberg │ │ LLM Wrapper │
│ (panel / list) │ │ (block / toolbar) │ │ (Claude Code, Codex…) │
└────────┬─────────┘ └────────┬──────────┘ └──────────┬─────────────┘
│ REST │ REST │ MCP
└──────────────────────┴──────────────────────────┘
│
┌──────────▼──────────────┐
│ SlyTranslate Ability │
│ (REST / MCP endpoint) │
└──────────┬──────────────┘
│
┌───────────▼───────────┐
│ AI Connector │ ← UI/block workflows
│ (wp_ai_client_prompt)│ only
└───────────┬───────────┘
│
┌───────────▼───────────┐
│ LLM (any provider) │
└───────────┬───────────┘
│
┌───────────▼───────────┐
│ Chunk + Validate │
└───────────┬───────────┘
│
┌───────────▼───────────┐
│ Language Plugin │
│ Polylang / TP / … │
└───────────┬───────────┘
│
┌───────────▼───────────┐
│ WordPress Post │
└───────────────────────┘
In the MCP workflow the LLM Wrapper acts as the translation engine — the AI Connector and LLM steps inside WordPress are bypassed.
Abilities reference
ai-translate/get-languages — List languages exposed by the active language plugin
ai-translate/get-translation-status — Show translation status for a content item, including `source_language` and `single_entry_mode`
ai-translate/set-post-language — Change the language assignment of an existing content item (Polylang only)
ai-translate/get-untranslated — Find content still missing a target translation
ai-translate/translate-text — Translate arbitrary text
ai-translate/translate-blocks — Translate serialized Gutenberg blocks
ai-translate/translate-content — Create or update one translated post/page/CPT entry
ai-translate/translate-content-bulk — Bulk-translate multiple entries (set `background=true` to queue the batch via Action Scheduler/WP-Cron and poll it with `get-progress`)
ai-translate/translate-terms — Bulk-translate taxonomy terms and link them as translations (Polylang only)
ai-translate/get-translatable-fields — Introspect which meta fields a translation would translate or clear, with source attribution (manual/SEO/ACF/default/filter)
ai-translate/get-progress — Return live progress for a running translation or a queued background job (`job_id`)
ai-translate/cancel-translation — Cancel a running translation or a queued background job (`job_id`)
ai-translate/get-available-models — List models from configured connectors
ai-translate/save-additional-prompt — Save per-user additional instructions
ai-translate/configure — Read or update persistent plugin settings
MCP call sequence
For reliable results in agent workflows:
Call get-languages first when the correct target language code is unknown.
Call get-translation-status before translate-content to read source_language, single_entry_mode, and whether a translation already exists.
Omit source_language unless you intentionally pin a source variant.
Set overwrite=true only when status or prior context confirms a target-language entry already exists.
translated_post_id equals source_post_id in single-entry adapters (WP Multilang, WPGlobus, TranslatePress). In multi-post adapters (Polylang) the translated item has a sibling post ID.
Supported plugins
Language plugins
Polylang
WP Multilang
WPGlobus
TranslatePress Multilingual
Field plugins (custom fields translated alongside content)
Advanced Custom Fields (ACF) — Free and Pro, including Repeater and Flexible Content, ACF blocks in Gutenberg, and options pages
Meta Box (metabox.io)
Pods
SEO plugins (metadata translated alongside content)
Genesis SEO
Yoast SEO
Rank Math
All in One SEO
The SEO Framework
SEOpress
Slim SEO
Supported model profiles
Any LLM available through a WordPress AI connector works without configuration. The following model families have dedicated built-in profiles that tune prompt style, chunking, and retry behavior:
TranslateGemma — dedicated runtime with chat_template_kwargs support via direct_api_url
TowerInstruct / Salamandra — bilingual framing, conservative chunking, stricter retries
Nvidia Nemotron — system-prompt-aware, reasoning-disable, provider-parameter forwarding
Qwen 3.x / GLM-4.6v / Gemma 4 / Phi-4 — thinking-aware profiles
EuroLLM / Llama 3.1-8B / SauerkrautLM — conservative chunking tuned for European languages
Ministral-3 / Ministral-8B — optimized for the Ministral model family
Additional profiles can be registered via the slytranslate_model_profiles filter.
