內容簡介
WPMMCC 是一款功能齊全的多語言外掛，能自動翻譯 WordPress 內容，並為每種語言提供獨立的網址。無需頁面建構器或手動複製文章，輕鬆設定語言組和翻譯提供者，讓背景隊列自動處理其餘工作。
【主要功能】
• 支援目錄模式與多站點模式
• 自動翻譯文章、頁面及自訂文章類型
• 翻譯媒體附件的替代文字與描述
• 翻譯分類與標籤的名稱與描述
• 支援多種翻譯提供者選擇
• 背景任務隊列確保大型網站不會超時
外掛標籤
開發者團隊
原文外掛簡介
WPMMCC is a full-featured multilingual plugin that translates your WordPress content automatically and serves each language at its own URL. It works in two modes:
Directory mode — one WordPress site, multiple language prefixes (example.com/en/, example.com/zh/)
Multisite mode — each language runs as a separate site in a WordPress Multisite network
No page builders required. No manual copying of posts. Configure your language groups, pick a translation provider, and let the background queue handle the rest.
What Gets Translated
Posts, Pages & Custom Post Types
Title, content, excerpt, and any custom fields you configure. Shadow copies of translated posts are stored on the same WordPress installation and served at the correct language URL automatically.
Media Attachments
Alt text, caption, and description fields for images and other attachments.
Categories & Tags (Taxonomies)
Translate category names, tag names, descriptions, and slugs into each target language.
Theme Strings
Scan your active theme’s PHP files, JavaScript, Twig templates, and database-stored strings. Translated strings are served transparently through WordPress filter hooks.
SEO Meta Fields
Translate Yoast SEO, Rank Math, and other SEO plugin fields alongside your content. Scan, add, enable, or disable individual meta fields per site group.
Translation Providers
Choose one or more providers per translation rule. Each rule maps a source language to a target language with a specific vendor:
Google Translate — fast, broad language coverage
DeepL — high quality, especially for European languages
Baidu Translate — optimised for Chinese
Youdao — alternative for Chinese language pairs
OpenAI / compatible LLMs — context-aware, customisable prompt, supports any OpenAI-compatible endpoint (e.g. Azure OpenAI, local models)
Background Task Queue
Translations run as background jobs so large sites never time out. Built on Action Scheduler (bundled, table-prefixed to avoid conflicts with WooCommerce). Monitor progress, cancel, retry, or manually trigger jobs from the Tasks screen.
SEO & URL Management
Automatic hreflang link tags for every translated page
Canonical URL management with proper trailing-slash handling
Multilingual XML sitemaps — shadow copies are excluded from the main sitemap; child language sitemaps use correct language-prefixed URLs
Compatible with Yoast SEO, Rank Math, and other SEO plugins
Frontend Shortcodes
Use these shortcodes anywhere on your site:
[wpmmcc_ml_current_language] — outputs the current page’s language code
[wpmmcc_ml_site_group_type] — outputs the group type (directory / multisite)
[wpmmcc_ml_language_switcher] — renders a language switcher link list
[wpmmcc_ml_language_items] — outputs all available languages as a JSON array
[wpmmcc_ml_canonical] — outputs the canonical tag for the current page
[wpmmcc_ml_hreflang] — outputs all tags
Admin Enhancements
Site filter dropdowns on the Posts, Pages, Media, Categories, and Comments admin list screens — filter any list by language site with one click
Translation management screen — view, filter, and delete translation relations
Bulk translation directly from the admin post list
Requirements
WordPress 5.3 or higher
PHP 7.2 or higher
MySQL 5.7 or MariaDB 10.2
PHP extensions: openssl, json, mbstring, curl
Compatibility
Core Platform Compatibility
Minimum supported WordPress version: 5.3
Tested up to WordPress 6.9
Minimum supported PHP version: 7.2
Works on both single-site WordPress installs and WordPress Multisite networks
Site Mode Compatibility
Directory mode works on a standard single-site WordPress install and serves translated content under language-prefixed URLs such as /zh/ or /fr/
Multisite mode requires a WordPress Multisite network and maps each language to its own site in the network
SEO Plugin Compatibility
Built to work alongside Yoast SEO and Rank Math
SEO meta translation is field-based, so supported meta keys can be scanned, enabled, disabled, and translated from the SEO Fields screen
Canonical and hreflang output can be handled either by WPMMCC or by your SEO plugin, depending on your settings
No fixed version matrix is published for third-party SEO plugins; compatibility is maintained at the integration level rather than by pinning specific vendor versions in this readme
Operational Notes
Translation jobs run through a bundled Action Scheduler build with prefixed tables to reduce conflicts with WooCommerce or other plugins that ship their own Action Scheduler copy
Block themes are supported when the active theme exposes standard WordPress block-theme files such as theme.json, templates, or parts
API-based translation requires outbound HTTPS access from your server to the provider you configure
External Services
This plugin connects to third-party translation and AI services to provide translation functionality. No data is sent to any service until you explicitly test a provider/model or run a translation job. Long fields may be split into multiple outbound requests so WPMMCC can respect provider limits and merge translated fragments back locally before saving. Below is a list of all external services used:
Google Translate API
Purpose: Automatic translation of content
Data sent: Text content to be translated, source and target language codes
When: When the user tests a Google translation rule or initiates translation using Google as the provider
Service URL: https://translation.googleapis.com/language/translate/v2
Content handling: WPMMCC splits oversized plain text or HTML-heavy fields locally before sending text fragments to Google
Terms of Service: https://cloud.google.com/terms/service-terms
Privacy Policy: https://policies.google.com/privacy
DeepL API
Purpose: Automatic translation of content
Data sent: Text content to be translated, source and target language codes
When: When the user tests a DeepL translation rule or initiates translation using DeepL as the provider
Service URL: https://api.deepl.com/v2/translate or https://api-free.deepl.com/v2/translate
Content handling: WPMMCC chunks large fields before calling the DeepL text-translation endpoint; HTML-aware splitting is handled locally in the plugin
Terms of Service: https://www.deepl.com/pro-license
Privacy Policy: https://www.deepl.com/privacy
Baidu Translate API
Purpose: Automatic translation of content
Data sent: Text content to be translated, source and target language codes
When: When the user tests a Baidu translation rule or initiates translation using Baidu as the provider
Service URL: https://fanyi-api.baidu.com/ait/api/aiTextTranslate
Authentication: Authorization: Bearer API_KEY or APP ID + MD5 sign
Official documentation: https://fanyi-api.baidu.com/doc/21
Service requirement: The Baidu credentials used by WPMMCC must have AI Text Translate enabled
HTML handling: When the source contains HTML, WPMMCC sends the request with model_type=nmt and tag_handling=1
Terms of Service: https://fanyi-api.baidu.com/doc/5
Privacy Policy: https://fanyi-api.baidu.com/doc/21
Youdao Translate API
Purpose: Automatic translation of content
Data sent: Text content to be translated, source and target language codes
When: When the user tests a Youdao translation rule or initiates translation using Youdao as the provider
Service URL: https://openapi.youdao.com/translate_html
Authentication: App ID + App Secret using the official signType=v3 signature
Official documentation: https://ai.youdao.com/DOCSIRMA/html/trans/api/wyfy/index.html
Service requirement: The Youdao account must have the Webpage Translation service enabled
Content mode: WPMMCC uses this endpoint for both plain text and HTML so tag-preserving translation can use one provider flow
Terms of Service: https://ai.youdao.com/doc.s#guide
Privacy Policy: https://ai.youdao.com/doc.s
OpenAI API (or compatible)
Purpose: AI-powered translation using large language models
Data sent: Text content chunks to be translated, translation prompts, source and target language context, and optional max_tokens
When: When the user tests an LLM model/rule or initiates translation using the LLM provider
Service URL: Configurable (default: https://api.openai.com/v1/chat/completions)
Content handling: WPMMCC chunks long source content locally and asks the remote model to return translated strings in the same order, preserving placeholders and HTML markup
Terms of Service: https://openai.com/policies/terms-of-use
Privacy Policy: https://openai.com/policies/privacy-policy
Note: Users must configure their own API keys for these services. API keys are stored encrypted using AES-256 encryption in your database and are never logged or exposed in plain text.
Privacy Policy
WPMMCC respects your privacy and handles data responsibly:
Translation Data: Content sent to translation providers is processed according to each provider’s privacy policy
API Keys: Stored encrypted in your database, never transmitted except to the respective provider
No Tracking: The plugin does not track usage or send data to our servers
Local Processing: All other operations are performed locally on your server
For more information, please review the privacy policies of your chosen translation providers.
Credits
WPMMCC uses the following open-source libraries:
Action Scheduler (ASRunner 3.9.99-wpmmcc) – Consolidated build based on Action Scheduler 3.9.0, prefixed tables (wpmmcc_actionscheduler_*), defers to external Action Scheduler instances (e.g. WooCommerce) when present.
WordPress Coding Standards – Code quality
Support
Documentation: Plugin Documentation
Contributing
We welcome contributions! Please see our GitHub repository for:
Bug reports
Feature requests
Pull requests
Translation contributions
