

Translation health: what is up to date, what changed at the source, what was never translated.
Saasco Multilingual Translation is an AI-powered WordPress translation plugin for creating fast, SEO-ready multilingual websites.
Translate pages, posts and WooCommerce content manually or automatically with DeepL or OpenAI using your own API key. Review translations side by side and edit every segment yourself — your translated pages are real, server-rendered WordPress pages with their own URLs.
Instead of treating an entire page as one translation, Saasco Multilingual Translation tracks content segment by segment: every heading, paragraph, button and field has its own translation and its own status. That is what makes the PRO add-on possible — change two paragraphs in the source and see exactly what changed, without retranslating the whole page or overwriting your manual corrections.
Connect your own DeepL or OpenAI API key and translate as much content as you want.
There are no translation credits and no artificial translation limits imposed by the plugin. You pay the translation provider directly for what you use.
Prefer manual translation? No API key is required.
Every language gets its own server-rendered URL that search engines can crawl and index.
The free plugin includes:
Your translated pages are real WordPress pages — not dynamically replaced text rendered by an external translation proxy.
Translate and review content using a dedicated editor:
You stay in control of every translation, whether it was created manually or with AI.
Create multilingual WooCommerce stores with support for essential store content including:
Visitors can browse your store and complete their purchase in their selected language.
Add a language switcher anywhere on your WordPress site, including block themes.
It is available as:
When a translation does not exist, the switcher points visitors to the closest available equivalent instead of sending them back to the source-language homepage.
The translation engine does not send your page HTML to the translation provider.
It works with text segments and lightweight position markers — Order <0>today</0> — keeping HTML structure, CSS classes, URLs and data attributes outside the translation process.
This significantly reduces the risk of machine translation breaking your page layout.
Translations are stored in your own WordPress database as regular WordPress content.
There is no external translation server involved in rendering your pages and no SaaS platform required to keep your translations online.
If you stop using an AI provider — or stop using PRO — your translated content remains in your WordPress database.
Already running a multilingual website with Polylang?
Saasco Multilingual Translation includes a resumable Polylang import process. Your existing Polylang data is left untouched during the import.
The free version includes:
Publishing a translation is only the beginning. When you update your original content, the PRO add-on tracks which segments actually changed, marks only those as outdated and lets you retranslate just the changed content — your manual edits to everything else stay untouched.
PRO also adds:
The PRO licence only ever controls updates and support. Your site keeps working and your translations stay in place regardless of licence status.
Saasco Multilingual Translation makes no external requests while rendering your site, and none at all unless you connect a machine-translation provider yourself. If you do, the plugin sends the text of the segments you ask it to translate (with lightweight position markers, never your HTML, URLs or attributes), plus the source and target language codes, to the provider you configured, using the API key you provide. This happens only when you or a background job you started requests a machine translation, and when you test the key on the settings screen.
Your API key is stored encrypted in your own database and is sent only to the provider it belongs to. Saasco Multilingual Translation has no server of its own in this flow and never receives your text, your key or your usage.
The admin interface is built with @wordpress/scripts. The human-readable sources are shipped in the assets/ directory of this plugin; build/ contains the compiled output. Rebuild with npm install && npm run build in the plugin root.