LangRouter for TranslatePress
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.
About this tool.
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.
Key features
- Set one default engine as the baseline route.
- Route singular content types such as posts, pages, products, and custom post types to a preferred engine.
- Assign target languages to different engines.
- Define fallback behavior when the current engine cannot continue.
- Configure each engine separately in a dedicated settings page.
- Query language support from the admin area before changing live routing rules.
- Inspect routing behavior through built-in runtime logs.
- Support DeepL multi-key configuration and Volcengine Ark usage tools.
- Connect OpenAI-compatible third-party services and custom compatible endpoints.
Supported translation engines
LangRouter currently supports:
- Volcengine Ark
- Qwen
- Hunyuan
- OpenAI
- DeepL
- Compatible OpenAI API
How routing works
LangRouter uses the following priority order:
- 01Post type route
- 02Language assignment
- 03Default engine
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.
