Module profile
Net-Base AI Multilanguage Overview
Net-Base AI Multilanguage is not a superficial language switcher for us, but a technical layer for base language, target languages, browser detection, queue operation, protected terms and editorial preview. Precisely for that reason language remains controllable even when many pages, topic areas, legal texts and SEO fields are interconnected.
German remains the authoritative language
New content originates from an editorially maintained German base and is then controlledly carried over into active target languages.
Company and product names remain stable
Protected terms ensure that brands, project names and company-specific terms are not fragmented by automatic translation.
Queue instead of restless single updates
Changes to pages, menus, taxonomies, theme texts and SEO fields are collected, propagated and can be tracked visibly in the backend.
What this module delivers in concrete terms
Manages the base language German, active target languages, browser detection, translation queue and backend previews for language variants.
Scope of functions
- Base language is always German; all other active languages are generated from it.
- Supports pages, posts, public custom post types, menu items, taxonomies, site subtitles as well as static theme and plugin texts.
- Automatically re-translates changed content when the automation is active.
- Displays language variants in the frontend via 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 enabled target languages.
- ?lang=en forces a language directly, ?lang=de switches to the base language, ?lang=auto resets to automatic detection.
- The current language choice is stored via 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 manner.
Queue and operation
- New or outdated texts land 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 as insecure PHP threads.
- Batch size and interval control speed, API load and costs.
- Failed jobs can be collected and re-run.
Backend aids
- In the editor there are language-variant tabs for previewing each 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 corpus can be re-enqueued.
- Standard protected terms are visible in their own tab; custom protected terms can be maintained there as an additional list.
- Protected terms are masked before the AI request and then reinserted 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 co-translated by the other Net-Base plugins, provided those plugins register their content.
- SEO titles and descriptions are not maintained here, but are linguistically linked to this system by the SEO modules.
Limits and notes
- Without a valid API key new jobs remain pending or fail.
- Very many active languages increase queue runtime, costs and the volume of content requiring follow-up.
- 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 a website, magazine and SEO become multilingual, a simple language switcher is no longer sufficient. It then becomes about language-specific canonicals, consistent terminology, clean fallbacks and the question of how changed content is technically and calmly propagated into multiple languages.
Do not treat languages as a side issue
Multilingualism only becomes economically relevant when language, SEO, protected terms and editorial processes are considered together from a technical perspective. This module is built precisely for that.