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. 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:

1. Post type route
2. Language assignment
3. Default 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. 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. Post type routing Post type routing is useful when different content types need different translation behavior. For example, you can:

• route products to one engine for terminology consistency;
• route editorial content to another engine for tone and fluency;
• keep specific custom post types on a dedicated provider.

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. Language assignment and fallback rules 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:

• choose the preferred engine for a target language;
• define a different engine as the fallback;
• keep the default engine as the final baseline or safety net.

Dedicated engine settings 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:

• API keys and secrets
• model names
• base URLs and compatible endpoints
• request timeouts
• additional request JSON
• per-engine notes and operational options
• multi-key or account-related settings for supported engines

Logging and troubleshooting 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:

• which engine was selected;
• whether a post type route was matched;
• whether language assignment handled the request;
• why a fallback decision was triggered;
• whether a provider entered the execution chain successfully.

Typical use cases

• Use one engine for most traffic and reroute selected languages.
• Route products, guides, and regular posts to different engines.
• Keep important content on stricter fallback behavior.
• Use DeepL, Volcengine Ark, and OpenAI-compatible services in one workflow.
• Compare providers while keeping routing and logging in one place.

1.1.3

• First release.
• Added global default concurrency in the TranslatePress router settings.
• Added per-engine concurrency overrides for OpenAI, Compatible OpenAI API, Qwen, Hunyuan, and Volcengine Ark.
• Added help page examples and guidance for low, medium, and high server configurations.
• Improved runtime log deletion and empty-state handling so cleared or zero-byte log files no longer appear as active logs.
• Improved Volcengine Ark status display so overdue billing states are shown correctly.