Description

AIT Multilingual Translate helps site owners translate WordPress content with AI and machine translation providers while saving translations locally for reuse.

The plugin is currently available as a Public Beta Build. Please make a backup before bulk translating production websites.

Language flag icons are bundled locally from the MIT-licensed lipis/flag-icons project. No external request is made to load flag images.

Why AIT Multilingual Translate?

AIT Multilingual Translate combines AI translation with a local Translation Memory to reduce API costs and improve website performance.

Instead of translating the same content repeatedly, every approved translation is stored locally and automatically reused until the original source changes.

The plugin is designed for multilingual WordPress websites, WooCommerce stores, Elementor projects, and professional agencies.

Key features

Translate with OpenAI, Google Translate, DeepL, Gemini, or Grok/xAI.
Save translations locally with Translation Memory and reuse them until source text changes.
Reduce API costs using smart cache, duplicate detection, token estimates, request limits, cache-hit statistics, and duplicate-skipped statistics.
Choose a global Translation Mode / Tone of Voice for AI providers such as SEO Optimized, Marketing, eCommerce, Technical, Legal, Luxury Brand, Friendly, or Custom Prompt.
Select source and target languages.
Scan posts, pages, products, menus, widgets, taxonomy terms, SEO meta, and public custom fields.
Process translation work in a queue so visitors do not wait for provider calls.
Edit saved translations from the frontend as an administrator.
Manage translations in a searchable Translation Matrix.
Export and import translations as CSV, PO, or MO files.
Add language switchers with shortcodes, widgets, Elementor, WordPress menus, header, or footer placement.
Use directory URLs such as /ka/about/ or query URLs such as /about/?lang=ka.
Includes WooCommerce product and category URL compatibility helpers.
Includes a debugger, route diagnostics, safe log export, and provider test tools.

Ideal for

WooCommerce stores
Elementor websites
Corporate multilingual websites
Blogs and magazines
Agencies managing multiple client websites
Developers building multilingual projects

Public Beta

AIT Multilingual Translate is still under active testing. Bulk translation can consume provider quota and should be tested on staging first. The plugin stores API keys in WordPress options unless you define keys in wp-config.php.

Trademark notice

WooCommerce and Elementor are trademarks of their respective owners. This plugin is not affiliated with, endorsed by, or sponsored by WooCommerce, Automattic, Elementor, or their parent companies.

External services

AIT Multilingual Translate can connect to external translation providers. No provider is contacted unless you configure a provider key and start a provider test, queue process, background queue run, or on-page translation request.

For all providers, the plugin may send source text strings, source language, target language, provider model/endpoint selection, and request metadata required by the provider. API keys are sent only to the selected provider endpoint and are not shown in the debugger or public output.

OpenAI:

Sends selected strings and language instructions to OpenAI when OpenAI is the active provider.
Terms: https://openai.com/policies/terms-of-use/
Privacy: https://openai.com/policies/privacy-policy/

Google Translate:

Google Translate is used to translate selected source strings when Google Translate is selected as the active provider and the site owner has configured a Google Cloud Translation API key.
The plugin sends source text strings, source language and target language to Google Cloud Translation API only when the site owner starts a provider test, queue process, background queue run or on-page translation request.
Terms: https://cloud.google.com/terms
Privacy: https://policies.google.com/privacy

DeepL:

Sends selected strings plus source and target language codes to DeepL when DeepL is the active provider.
Terms: https://www.deepl.com/pro-license
Privacy: https://www.deepl.com/privacy

Gemini:

Sends selected strings and language instructions to the Gemini API when Gemini is the active provider.
Terms: https://ai.google.dev/gemini-api/terms
Privacy: https://policies.google.com/privacy

Grok/xAI:

Sends selected strings and language instructions to xAI when Grok/xAI is the active provider.
Terms: https://x.ai/legal/terms-of-service
Privacy: https://x.ai/legal/privacy-policy

Screenshots

Dashboard with translation overview and quick actions.

Setup Wizard for configuring source and target languages, AI providers, API keys, scanning, and frontend editing. — Dashboard with translation overview and quick actions.

Installation

Upload the ait-multilingual-translate folder to /wp-content/plugins/ or install the ZIP through Plugins > Add New > Upload Plugin.
Activate AIT Multilingual Translate.
Open AI Translate in the WordPress admin menu.
Choose source and target languages.
Select a provider and add the provider API key.
Run the scanner to collect site strings.
Process the translation queue.
Add a language switcher using [aitmt_language_switcher], a widget, Elementor, or a WordPress menu item.

FAQ

Does AIT Multilingual Translate translate pages on every visit?: No. The recommended workflow is to scan strings, process them in the queue, save translations locally, and serve saved translations to visitors.
Can I use the plugin without an AI provider?: Yes. You can scan strings and manually edit translations in the Translation Matrix. Provider translation requires a provider API key.
Does the plugin support Elementor?: Yes. The plugin includes Elementor compatibility features, an Elementor Language Switcher widget, and scanner coverage for Elementor content. Always test complex layouts on staging before bulk translation.
Does the plugin support WooCommerce?: Yes. The Public Beta Build includes WooCommerce product and product-category URL compatibility helpers and scanner coverage for product content. Always test stores on staging before bulk translation.
Can I reduce AI costs?: Yes. Translation Memory automatically reuses existing translations, duplicate requests are skipped, and AI Cost Optimization settings help control provider usage.
Where are translations stored?: Translations are stored in a custom WordPress database table named with the site prefix, usually wp_aitmt_translations.
Are API keys visible in logs?: The debugger masks provider keys. Safe debug exports redact secrets and sensitive data before inclusion in reports.
Can I define API keys in wp-config.php?: Yes. Supported constants are AITMT_OPENAI_API_KEY, AITMT_GEMINI_API_KEY, AITMT_GROK_API_KEY, AITMT_GOOGLE_TRANSLATE_API_KEY, and AITMT_DEEPL_API_KEY.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“AIT Multilingual Translate” is open source software. The following people have contributed to this plugin.

itdesignsro

Translate “AIT Multilingual Translate” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

0.3.34

Updated DeepL Terms and Privacy Policy URLs in readme.txt for WordPress.org review.

0.3.33

Renamed public plugin branding to AIT Multilingual Translate.
Removed WordPress.org restricted/trademark-sensitive wording from the public plugin name.
Reworked internal prefixing from wpait/WPAIT toward aitmt/AITMT naming.
Removed custom updater / self-update override logic for WordPress.org compliance.
Improved WordPress enqueue handling for JavaScript and CSS.
Improved external services disclosure in readme.txt.
Removed or corrected broken external service legal/privacy links.
Improved plugin directory/path handling using WordPress helper functions.
Improved output buffering lifecycle.
Improved output escaping in frontend/admin rendering.
Restored target language search in the dashboard and setup wizard after the public prefix cleanup.
Restored frontend language switcher styling for shortcode, Elementor widget, automatic placement, and WordPress menu output.
Restored frontend editor editable text detection and AJAX actions after the final aitmt prefix rename.
Tested the updated package with Plugin Check.
Prepared updated ZIP package for WordPress.org review.

0.3.32

Renamed the final WordPress.org submission package to AIT Multilingual Translate.
Updated the plugin slug, folder, ZIP name, and text domain to ait-multilingual-translate.
Removed beta self-update/repair updater hooks for WordPress.org compliance.
Updated external-services disclosure and generated log directory handling.
Added explicit output-buffer shutdown handling for review safety.

0.3.31

Renamed the public WordPress.org plugin name to AIT Multilingual Translate.
Updated the submission slug and package root to ait-multilingual-translate.
Updated the text domain and language template filename for WordPress.org language-pack readiness.
Updated public-facing branding, readme text, and WordPress.org trademark wording.
Kept internal prefixes, option names, database tables, shortcodes, translation engine, queue, scanner, routing, Elementor widget, frontend editor, and WooCommerce compatibility logic unchanged.

0.3.30

Added AI Cost Optimization settings for quality mode, temperature, request character limits, estimated per-request cost limits, model guidance, and token/cost statistics.
Added safe deduplication before provider requests and translation-memory cache-hit handling for frontend auto-translate.
Added provider capability cards for active providers and planned architecture targets without enabling unfinished provider API integrations.
Loaded the WordPress text domain for language-pack readiness and disabled the older internal dictionary fallback.
Updated the public package slug to ait-multilingual-translate.
Kept translation engine, queue architecture, scanner collection logic, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.

0.3.29

Finalized the Translation Style / Tone of Voice settings section for the Public Beta release.
Added Translation Mode visibility to Scanner and Queue statistics.
Documented that per content type modes are planned for a future release while the current build uses Global Translation Mode.
Kept translation engine, queue architecture, scanner collection logic, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.

0.3.28

Added a Scanner and Queue “Translate All” action that processes queued translations in safe provider batches with quota/time-limit guidance.
Finalized Global Translation Mode / Tone of Voice UI copy and server-side custom instruction length protection.
Kept translation engine, queue architecture, scanner collection logic, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.

0.3.27

Fixed admin asset loading for all plugin subpages after the public slug change.
Replaced the remaining public Elementor switcher label that used the old plugin name.
Updated the modular settings link to the new top-level admin page.
Kept translation engine, queue, scanner, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.

0.3.26

Prepared the public WordPress.org package name, metadata, and build structure for AIT Multilingual Translate.
Added Translation Mode / Tone of Voice settings for prompt-based AI providers.
Switched default OpenAI model to gpt-4o-mini and Grok default to a lightweight model where available.
Hardened custom-table SQL and local file handling for WordPress.org Plugin Check compatibility.
Kept translation engine, queue, scanner, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.

0.3.25

Added secure frontend editor Auto Translate so administrators can request an AI/provider translation inside the edit modal, review it, and save manually.
Improved frontend editor modal loading state, textarea auto-resize, mobile spacing, and provider error messaging.
Kept translation engine, queue, scanner, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.

0.3.24

Replaced remaining parse_url() calls with WordPress wp_parse_url() for Plugin Check compatibility.
Added translator comments and documented safe internal HTML output paths.
Improved uninstall variable prefixing for WordPress Coding Standards.
Kept translation engine, queue, scanner, routing, WooCommerce handling, and language switcher behavior unchanged.

0.3.23

Public Beta Build prepared for WordPress.org submission.
Added WordPress.org readme.txt.
Added GPL license file and plugin header license metadata.
Replaced earlier beta wording with “Public Beta Build”.
Hardened uninstall table-name handling.
Preserved translation engine, queue processing, scanner, routing, provider logic, frontend editor, WooCommerce compatibility, Elementor widget logic, and language switcher core logic.

0.3.22

Added menu language switcher anchor protection for themes that rewrite menu links.

0.3.21

Prevented the frontend language URL rewriter from overwriting WordPress menu language switcher links.

0.3.20

Improved menu language switcher behavior for current-language switcher items.

Description

Why AIT Multilingual Translate?

Key features

Ideal for

Public Beta

Trademark notice

External services

Screenshots

Installation

FAQ

Does AIT Multilingual Translate translate pages on every visit?

Can I use the plugin without an AI provider?

Does the plugin support Elementor?

Does the plugin support WooCommerce?

Can I reduce AI costs?

Where are translations stored?

Are API keys visible in logs?

Can I define API keys in wp-config.php?