Net-Base AI Multilanguage is not a superficial language switch for us, but a technical layer for base language, target languages, browser detection, queue operation, protected terms and editorial preview. This is how language remains controllable, even when many pages, sections, legal texts and SEO fields are interconnected.
German remains the editorial authority
New content is produced from an editorially maintained German base and is systematically transferred from there into active target languages.
Company and product names remain stable
Protected terms ensure that brands, project names and company-specific terms are not mangled by automatic translation.
Queue instead of ad-hoc single updates
Changes to pages, menus, taxonomies, theme texts and SEO fields are collected, synchronized and can be tracked visibly in the backend.
What this module provides
Manages the base language German, active target languages, browser detection, translation queue and backend previews for language variants.
Functionality
- Base language is always German; all other active languages are generated from it.
- Supports pages, posts, public custom post types, menu items, taxonomies, website subtitles and fixed theme and plugin texts.
- Re-translates changed content automatically if automatic mode is active.
- Displays language variants in the frontend based on the browser language or ?lang=xx.
- Protected terms such as company, product and project names remain unchanged.
Language control in the frontend
- Browser detection only acts on activated target languages.
- ?lang=en forces a language directly, ?lang=de switches to the base language, ?lang=auto reverts to automatic detection.
- The current language choice is stored in the plugin cookie and re-evaluated on subsequent page requests.
- If nothing exists yet for a language, the output falls back to German in a controlled way.
Queue and operation
- New or outdated texts are placed in a translation queue.
- The queue is processed in the background via cron and an additional kickoff.
- The number of parallel workers is configurable; additional workers run as separate signed queue processes with database claiming instead of insecure PHP threads.
- Batch size and interval control speed, API load and costs.
- Failed jobs can be restarted in batches.
Backend assistance
- In the editor there are language-variant tabs for preview per active language.
- There you can see per field whether the translation is current, pending, outdated or failed.
- The admin page shows overall status, recent errors and the current queue operation.
- When saving settings, the entire content can be re-enqueued.
- Default protected terms are visible in a dedicated tab; custom protected terms can be maintained there as an additional list.
- Protected terms are masked before the AI request and then restored exactly afterwards so that brand and product names are not transliterated.
Interaction with SEO
- The language module provides the frontend language on which hreflang, Canonical and SEO metadata are based.
- New active languages can be translated by the other Net-Base plugins, provided they register their content.
- SEO titles and descriptions are not managed here, but linguistically linked to this system by the SEO modules.
Limitations and notes
- Without a valid API key, new jobs remain pending or fail.
- A very large number of active languages increases queue runtime, costs and the volume of content to be maintained.
- The base language remains editorially authoritative. Target languages should nevertheless be spot-checked.
Context
Multilingualism is the website’s technical language layer. It does not provide an SEO strategy and does not replace editorial control in target languages.
Why this layer is important for international visibility
Once the website, magazine and SEO become multilingual, a simple language switch is no longer sufficient. It becomes a matter of language-specific canonicals, consistent terminology, clean fallbacks and the question of how changed content is technically propagated into multiple languages without disruption.
Don’t treat languages as a side issue
Multilingualism only becomes economically viable when language, SEO, protected terms and editorial work are considered together from a technical perspective. This module is built for exactly that.