LangRouter for TranslatePress

Rather than simply connecting a few more interfaces, LangRouter for TranslatePress upgrades automatic translation into a set of execution links that can be triaged by content type, target language, and failure policy.

fig. beginning / Resources for building websites / WordPress Plugin Recommendations / LangRouter for TranslatePress

task sth.

How will a request be handled?

1. Article type main engine Single content page only

If the current page is a single article, page, product or custom article type detail page, check the article type assignment rules first.

2. Language distribution Select main engine by locale

It will only enter language allocation if no higher priority rules are hit, or if the preceding rules allow the global link to continue.

3. Fallback rules Triggered only on failure

The fallback rule is not the main route, but rather the current main engine fails before it starts to take over.

4. Default engine Manually specified in the background

The default engine is the ultimate under-the-hood solution, not all requests go through it first at the outset.

Why this plugin is valuable

The difficulty is never “can it translate automatically”, but how to control it once it's online.

People who will actually use this plugin focus on control, failure strategies and troubleshooting.

One Engine Running All Content

It's hard to balance effectiveness and cost when product pages, blog pages, landing pages, and help centres all go through the same engine.

Wide variations in language adaptation

One engine is great for one language and mediocre for another, making it difficult to do both in a single route.

How to continue after failure

Should I just stop, just cut the default engine, or continue the global fallback chain? Hard to do without a routing layer.

You can't see what's going on when things go wrong.

It's not just about “failing”, it's about who you hit, who you fall back to, and where you end up.

Real Route Priority

Not “default engine + some additional rules”, but a sequential execution chain

Article Type Main Engine

Highest priority, but only in effect on a single content page.

language allocation

Determining the main engine by target language lends itself to separate triage of key languages.

Fallback rules

Intervenes only when the current primary engine fails and does not participate in primary routing.

Default Engine

Manually specified in the background as a final tout.

The most valuable thing about article type rules is that each rule determines how to go after a failure

Failure does not translate.

Perfectly suited for critical content, it stops directly upon failure and does not continue any subsequent links.

Default engine only

When the current rule fails, it jumps directly to the manually specified default engine in the backend.

global rule

When the current rule fails, it continues to go through language assignment, fallback rules, and finally to the default engine.

Competencies that really deserve to be highlighted

These are the points that show the value of the plugin more than “how many engines are supported”.

Default engine manually specified

Clearly set up the base and final pockets programmes, which are better suited to the production environment.

Article types can be finely triaged

Individual articles, pages, products, and custom article types can all be assigned a separate main engine.

Each rule has an independent failure strategy

It's not a uniform fallback, but different content types can use different failure handling.

Separation of language allocation and fallback

How to choose the main engine and how to connect it after failure are configured separately and independently for clearer logic.

Backend Query Language Support

Support can be queried by language name, code or locale, verify before configuring.

Logs trace real links

The ability to see the source of the hit, the current engine, the source of the fallback and the final state, no more blind guesses.

Supported Engines

Volcengine Ark

Supports account pooling and usage related capabilities

Qwen

Support for models, regions and custom interfaces

Hunyuan

Support for official models and compatible endpoints

OpenAI

Support for model selection and custom APIs

DeepL

Supports key and related state management

OpenAI Compatible API

Suitable for third-party gateways or self-built compatible services

Plugin Screenshots

Screenshot of plugin background settings

highlight

A few examples of configurations that understand value at a glance

Example A

The surest way to start: set only the default engine

First, set the only translation engine that has been verified in the background as the default engine to ensure that the whole automatic translation link runs through first, and then gradually increase the routing rules.

Ideal for just accessing, just migrating, and looking for stability first.

 
默认引擎：OpenAI
文章类型分配：不配置
语言分配：不配置
回退规则：不配置

Effect: All requests end up going to the default engine manually specified in the background. The configuration is the simplest and most troubleshooting-friendly.

Example B

Default engine for most languages, a few languages optimised separately

It's a very practical way to play the game: remain stable overall, but divert a few key languages individually to more appropriate engines.

Ideal for those who already have a main engine, but want to optimise local language performance.


默认引擎：OpenAI
语言分配：
en_US = Hunyuan
yue = DeepL
am = OpenAI Compatible

Effect: Most languages still go to the default engine; English, Cantonese, and Amharic are assigned to separate main engines.

Example C

Commodity page priority to go to the specified engine, after the failure of the direct cut default pockets

Great for malls: product detail pages prioritise the use of engines better suited to terminology scenarios, but don't drag your feet when you encounter failure, just cut the default engine.

Suitable for WooCommerce, multilingual malls, and product sites.


默认引擎：OpenAI
文章类型分配：
product -> DeepL（仅默认引擎）

Effect: the product detail page will go to DeepL in priority; once it fails, it will directly jump to the manually specified default engine OpenAI in the background.

Example D

Key content must only go to the specified engine and stop when it fails

Some content you'd rather not flip than have it error back to another engine to continue generating.

Ideal for brand statements, legal pages, terminology pages.


默认引擎：DeepL
文章类型分配：
guides -> Qwen（失败不翻译）
语言分配：
am = Volcengine Ark
回退规则：
am = Hunyuan

Effect: If it's a guides single detail page, go Qwen first; once Qwen fails it just stops and doesn't continue the global link.

Example E

Continuing the global link after article type failure to form a complete fallback system

This is one of the most production-like configurations: go to the exclusive main engine first, and when it fails, continue with language allocation, fallback rules, and only finally land on the default engine.

Suitable for sites with complex content structure, many languages and high availability requirements.


默认引擎：DeepL
文章类型分配：
guides -> Qwen（全局规则）
语言分配：
am = Volcengine Ark
回退规则：
am = Hunyuan

Effect: guides single detail page first go Qwen; after failing to continue to try Volc, then try Hunyuan, before finally reaching the default DeepL.