webaiplanet

LangRouter for TranslatePress adds routing and fallback control to TranslatePress automatic translation.
Instead of sending every request to a single provider, it lets you choose which translation engine should handle a request based on the current content type, target language, and fallback policy. This gives you more control over translation flow on multilingual WordPress sites.
This plugin is an independent extension for TranslatePress. It is not affiliated with, endorsed by, or maintained by TranslatePress.
It is intended for site owners, developers, agencies, and content teams that need more control than a single-engine setup can provide.
<h4>Key features</h4>
<ul>
<li>Set one default engine as the baseline route.</li>
<li>Route singular content types such as posts, pages, products, and custom post types to a preferred engine.</li>
<li>Assign target languages to different engines.</li>
<li>Define fallback behavior when the current engine cannot continue.</li>
<li>Configure each engine separately in a dedicated settings page.</li>
<li>Query language support from the admin area before changing live routing rules.</li>
<li>Inspect routing behavior through built-in runtime logs.</li>
<li>Support DeepL multi-key configuration and Volcengine Ark usage tools.</li>
<li>Connect OpenAI-compatible third-party services and custom compatible endpoints.</li>
</ul>
<h4>Supported translation engines</h4>
LangRouter currently supports:
<ul>
<li>Volcengine Ark</li>
<li>Qwen</li>
<li>Hunyuan</li>
<li>OpenAI</li>
<li>DeepL</li>
<li>Compatible OpenAI API</li>
</ul>
<h4>How routing works</h4>
LangRouter uses the following priority order:
<ol>
<li>Post type route</li>
<li>Language assignment</li>
<li>Default engine</li>
</ol>
If a singular content request matches a post type rule, that engine becomes the primary route. 
If no post type rule matches, LangRouter checks the language assignment rules. 
If no language rule matches, the plugin uses the default engine.
If the current engine cannot continue, LangRouter applies the configured fallback behavior. 
Depending on your settings, the request can stop immediately, jump directly to the default engine, or continue through the global fallback chain.
<h4>Post type routing</h4>
Post type routing is useful when different content types need different translation behavior.
For example, you can:
<ul>
<li>route products to one engine for terminology consistency;</li>
<li>route editorial content to another engine for tone and fluency;</li>
<li>keep specific custom post types on a dedicated provider.</li>
</ul>
Post type routing applies only to singular content contexts, such as a single post, page, product, or custom post type entry. 
Archive pages, taxonomy pages, search results, and other non-singular views do not use post type routing.
<h4>Language assignment and fallback rules</h4>
Language assignment selects the primary engine for a target language. 
Fallback rules define what to try next only after the current primary engine cannot continue.
This separation helps you build a clearer routing strategy:
<ul>
<li>choose the preferred engine for a target language;</li>
<li>define a different engine as the fallback;</li>
<li>keep the default engine as the final baseline or safety net.</li>
</ul>
<h4>Dedicated engine settings</h4>
Routing rules and engine credentials are managed separately. 
This makes the plugin easier to operate and maintain.
In the engine settings area, you can configure items such as:
<ul>
<li>API keys and secrets</li>
<li>model names</li>
<li>base URLs and compatible endpoints</li>
<li>request timeouts</li>
<li>additional request JSON</li>
<li>per-engine notes and operational options</li>
<li>multi-key or account-related settings for supported engines</li>
</ul>
<h4>Logging and troubleshooting</h4>
LangRouter includes a built-in runtime log viewer. 
You can enable file logging, view recent log content inside the admin area, and download log files for debugging.
This is useful when you want to confirm:
<ul>
<li>which engine was selected;</li>
<li>whether a post type route was matched;</li>
<li>whether language assignment handled the request;</li>
<li>why a fallback decision was triggered;</li>
<li>whether a provider entered the execution chain successfully.</li>
</ul>
<h4>Typical use cases</h4>
<ul>
<li>Use one engine for most traffic and reroute selected languages.</li>
<li>Route products, guides, and regular posts to different engines.</li>
<li>Keep important content on stricter fallback behavior.</li>
<li>Use DeepL, Volcengine Ark, and OpenAI-compatible services in one workflow.</li>
<li>Compare providers while keeping routing and logging in one place.</li>
</ul>
<h3>External services</h3>
This plugin can connect to third-party translation and AI services. These services are optional and are used only for translation, supported-language checks, usage checks, or diagnostic actions requested by an administrator.
No request is sent to a third-party service unless an administrator configures that engine and triggers translation or a related engine-specific action, such as a language support query, usage query, or diagnostic request.
The plugin may connect to the following services:
<ul>
<li>
OpenAI API. This service is provided by OpenAI and is used to translate content through OpenAI models. 
Data sent: text selected for translation, source and target language instructions, model settings, request parameters, and related request metadata required to complete the request. 
Sent only when this engine is configured and used by an administrator. 
Terms of Service: https://openai.com/policies/services-agreement/ 
Privacy Policy: https://openai.com/policies/row-privacy-policy/
</li>
<li>
DeepL API. This service is provided by DeepL and is used to translate content through DeepL and, when needed, query supported languages. 
Data sent: text selected for translation, source language, target language, translation parameters, or request parameters required for supported-language queries. 
Sent only when this engine is configured and used by an administrator. 
Terms and Conditions: https://www.deepl.com/en/pro-license 
Privacy Policy: https://www.deepl.com/en/privacy.html
</li>
<li>
Tencent Cloud Hunyuan (China). This service is provided by Tencent Cloud and is used to translate content through Tencent Cloud Hunyuan endpoints configured for the China service. 
Data sent: text selected for translation, source language, target language, model settings, request parameters, and related metadata required to complete the request. 
Sent only when this engine is configured for Tencent Cloud China and used by an administrator. 
Terms of Service: https://cloud.tencent.com/document/product/301/97822 
Privacy Policy: https://cloud.tencent.com/document/product/301/11470
</li>
<li>
Tencent Cloud Hunyuan (International). This service is provided by Tencent Cloud International and is used to translate content through Tencent Cloud Hunyuan international endpoints. 
Data sent: text selected for translation, source language, target language, model settings, request parameters, and related metadata required to complete the request. 
Sent only when this engine is configured for Tencent Cloud international endpoints and used by an administrator. 
Terms of Service: https://www.tencentcloud.com/document/product/1284/75295 
Privacy Policy: https://www.tencentcloud.com/document/product/1284/75293
</li>
<li>
SiliconFlow API. This service is provided by SiliconFlow and is used when Hunyuan-compatible translation is configured through the SiliconFlow compatible endpoint. 
Data sent: text selected for translation, source and target language instructions, model settings, request parameters, and related metadata required to complete the request. 
Sent only when this compatible endpoint is configured and used by an administrator. 
Terms of Service: https://docs.siliconflow.cn/cn/legals/terms-of-service 
Privacy Policy: https://docs.siliconflow.cn/cn/legals/privacy-policy
</li>
<li>
Volcengine Ark. This service is provided by Volcengine and is used to translate content through Volcengine models and, when requested by the administrator, perform usage-related queries. 
Data sent: text selected for translation, model settings, request parameters, and, for usage-related requests, the account identifiers, date ranges, and signed request data required by the service. 
Sent only when this engine is configured and used by an administrator, or when the administrator manually triggers a usage-related request. 
Terms of Service: https://www.volcengine.com/docs/6456/70590 
Privacy Policy: https://www.volcengine.com/docs/6256/64902
</li>
<li>
Alibaba Cloud DashScope / Qwen (China). This service is provided by Alibaba Cloud and is used to translate content through Qwen-compatible endpoints configured for Alibaba Cloud China. 
Data sent: text selected for translation, source language, target language, model settings, request parameters, and related metadata required to complete the request. 
Sent only when this engine is configured for Alibaba Cloud China and used by an administrator. 
Terms of Service: https://terms.alicdn.com/legal-agreement/terms/common_platform_service/20230728213935489/20230728213935489.html 
Privacy Policy: https://terms.aliyun.com/legal-agreement/terms/suit_bu1_ali_cloud/suit_bu1_ali_cloud202107091605_49213.html
</li>
<li>
Alibaba Cloud DashScope / Qwen (International). This service is provided by Alibaba Cloud International and is used to translate content through international Qwen-compatible endpoints configured by the administrator. 
Data sent: text selected for translation, source language, target language, model settings, request parameters, and related metadata required to complete the request. 
Sent only when this engine is configured for international Alibaba Cloud endpoints and used by an administrator. 
Terms of Service: https://www.alibabacloud.com/help/en/legal/latest/alibaba-cloud-international-website-terms-of-use-alibaba-cloud-international-website-terms-of-use 
Privacy Policy: https://www.alibabacloud.com/help/en/legal/latest/alibaba-cloud-international-website-privacy-policy
</li>
<li>
Compatible OpenAI API endpoints. These services are provided by the third-party provider selected by the administrator and are used when you configure a third-party service that implements an OpenAI-compatible API. 
Data sent: text selected for translation, source and target language instructions, configured model name, request headers, request parameters, and related request metadata required to complete the request. 
Sent only when a compatible third-party service is configured and used by an administrator. 
The provider, terms, privacy policy, and data handling depend on the service you choose. Review that provider before use.
</li>
</ul>
This plugin does not require any external service unless you choose to configure and use a supported engine.

LangRouter for TranslatePress

Add routing, fallback control, and engine-specific settings to TranslatePress automatic translation.

voxfor

Voxfor Multilanguage is a powerful, free WordPress multilingual plugin that makes your website accessible to a global audience. Using the DeepL API, it provides professional-quality translations while maintaining full control over your content.
IMPORTANT: This plugin uses the DeepL API external service for translations. You need to provide your own DeepL API key (free or paid). See the “External Services” section below for complete details about data transmission and privacy.
AI-powered website translation by <a href="https://netanelai.co.il/" rel="nofollow ugc">NetanelAI</a>
<h4>Resources</h4>
<ul>
<li><a href="https://www.voxfor.com/multilinguage-translate.php" rel="nofollow ugc">Official Website</a></li>
<li><a href="https://www.voxfor.com/multilinguage-translate.php#documentation" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://www.youtube.com/watch?v=rfwD2khOhgg" rel="nofollow ugc">Watch Full Video Guide</a></li>
<li><a href="https://www.deepl.com/en/pro-api" rel="nofollow ugc">Get Your DeepL API</a></li>
</ul>
<h4>Key Features</h4>
<ul>
<li>AI Translation – Uses DeepL API for accurate, context-aware translations</li>
<li>BYO API Key – Bring your own DeepL API key for unlimited scalability</li>
<li>SEO-Optimized – Automatic hreflang tags, translated image ALT text, and language-specific canonical URLs</li>
<li>Translation Memory – Stores all translations locally for efficiency and consistency</li>
<li>Visual Editor – Edit translations directly on your pages with in-context editing</li>
<li>Flexible Language Switcher – Multiple widget styles: dropdown, inline, flags, or compact</li>
<li>Smart Routing – Clean URL structure with language prefixes (/fr/, /de/, /es/)</li>
<li>Glossary Support – Define terms that must always be translated consistently</li>
<li>Exclusion Rules – Skip translation for specific pages, elements, or content</li>
<li>WooCommerce Compatible – Safe checkout process with smart exclusions</li>
</ul>
<h4>SEO Features</h4>
<ul>
<li>Automatic hreflang tag generation for all language versions</li>
<li>Image ALT text translation for better international SEO</li>
<li>Language-specific canonical URLs to prevent duplicate content</li>
<li>Structured data support for multilingual content</li>
<li>Integration with popular SEO plugins (Yoast, RankMath, All in One SEO)</li>
<li>Optional URL slug translation</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Add your DeepL API key in settings</li>
<li>Select the languages you want to support</li>
<li>The plugin automatically translates your content using DeepL API</li>
<li>All translations are stored in a local database for fast loading</li>
<li>Visitors see content in their preferred language</li>
</ol>
<h4>Language Support</h4>
Supports 33+ languages including: 
English, French, German, Spanish, Italian, Portuguese, Russian, Japanese, Chinese, Korean, Arabic, Hebrew, Swedish, Norwegian, Danish, Finnish, Dutch, Polish, Turkish, Czech, Slovak, Slovenian, Hungarian, Romanian, Bulgarian, Greek, Estonian, Latvian, Lithuanian, Thai, Vietnamese, Indonesian, Ukrainian
<h4>Developer Friendly</h4>
<ul>
<li>Clean, well-documented code</li>
<li>Extensive hooks and filters for customization</li>
<li>REST API for programmatic access</li>
<li>Compatible with page builders and custom themes</li>
<li>Full multisite support</li>
</ul>
<h3>External Services</h3>
This plugin relies on the DeepL API, an external third-party service, to provide translation functionality. By using this plugin, you acknowledge and agree to the data transmission described below.
<h4>DeepL API Translation Service</h4>
Service Provider: DeepL SE, Maarweg 165, 50825 Cologne, Germany
What the service is: 
DeepL is a professional AI translation service that provides high-quality language translation.
What it’s used for: 
This plugin uses the DeepL API to translate your website content including posts, pages, menus, widgets, image alt text, custom fields, and WooCommerce products from one language to another.
What data is sent to DeepL: 
When translation is requested, the following data is transmitted to DeepL servers: 
– Text content to be translated (post content, titles, excerpts, menu items, widget text, image alt text, custom field values, etc.) 
– Source language code (e.g., “EN” for English) 
– Target language code (e.g., “FR” for French, “DE” for German, “ES” for Spanish) 
– Your DeepL API authentication key 
– Optional: Formality preference (formal/informal) 
– Optional: Context information to improve translation accuracy 
– Optional: Glossary terms for consistent translations
When data is sent: 
Data is transmitted to the DeepL API only in the following scenarios: 
– When you manually request translation of specific content via the admin interface 
– When new content is published and automatic translation is enabled in settings 
– When bulk translation operations are performed 
– When translation memory cache does not contain a previously translated version 
– When testing API connection in plugin settings 
– When checking API usage statistics
Data NOT sent: 
– No visitor/user personal information 
– No browsing data or analytics 
– No database credentials 
– No WordPress admin credentials 
– API calls only occur during translation operations, NOT on frontend page loads
Data Storage: 
– All translations received from DeepL are stored locally in your WordPress database 
– Once cached, no further API calls are made for that content 
– Translations are served from your local database to visitors 
– No ongoing data transmission to DeepL for previously translated content
Your API Key: 
– You must provide your own DeepL API key (free or paid account) 
– API keys are stored encrypted in your WordPress database 
– This plugin does NOT collect, store, or transmit your API credentials to Voxfor or any other third party 
– Your API key is only sent to DeepL servers for authentication
Legal & Privacy Links: 
– DeepL Terms of Service: https://www.deepl.com/pro-license 
– DeepL Privacy Policy: https://www.deepl.com/privacy 
– DeepL API Documentation: https://developers.deepl.com/api-reference/translate
GDPR Compliance: 
DeepL is GDPR compliant and processes data in accordance with European data protection regulations. For more information, see DeepL’s privacy policy linked above.
User Consent: 
By installing and using this plugin with a DeepL API key, you acknowledge that content from your WordPress site will be sent to DeepL for translation purposes as described above.
<h3>Privacy Policy</h3>
This plugin stores all translations locally in your WordPress database. No data is sent to Voxfor or any other third party except the DeepL API as described in the “External Services” section. The plugin only transmits data to DeepL when translation services are actively used by the site administrator.

Voxfor Multilanguage

Professional multilingual WordPress plugin using the DeepL API. Transform your website into a global platform.

LangRouter for TranslatePress vs Voxfor Multilanguage