Description
Lingomize rewrites the page HTML on its way out, so every language is the same post
with different words. Nothing is duplicated, so nothing drifts.
- Automatic
/th/,/fr/, … URLs with correcthreflang - Point-and-click editing on the live page
- A translation table for the whole site, with search and bulk editing
- Glossary and a keep-as-is term list
- Import / export as JSON, and a one-click import from WPML, Polylang, TranslatePress or Weglot
- Language switcher with flags
- AI translation, with a licence key
Licence
AI translation runs through the Lingomize licence proxy, which holds the AI key. Paste the
key from your welcome email under Lingomize → Settings. While the subscription is live the
site serves every language; let it lapse and the site goes back to its own language until
it is renewed. Your translations are never deleted — they stay in your database and come
back the moment the licence does. A site holding more original words than its plan covers
keeps every translation it has, but gets no new ones until it is upgraded or trimmed.
External services
The plugin contacts one address, only once a licence key is set. That service uses one model
provider behind it; both are described below. Nothing else leaves your server — the switcher’s flags ship with
the plugin, and no image, script or stylesheet is loaded from anywhere but your own site.
Lingomize licence proxy (https://api.lingomize.com)
Every translation request and the daily licence check go through it. Sent: the text you
chose to translate, the target language, the optional style notes you typed under Settings
(what the site is about, tone, audience), your licence key, your site’s host name, your
site’s word count and the language codes you have enabled. Nothing is sent while no licence
key is set.
Terms: https://lingomize.com/terms — Privacy: https://lingomize.com/privacy
Groq (https://groq.com)
The proxy forwards the text to be translated to Groq’s API and returns the translation.
Only that text reaches Groq; your licence key and site details do not.
Terms: https://groq.com/terms-of-use — Privacy: https://groq.com/privacy-policy
FAQ
Does it duplicate my posts?
No. One post, rewritten per language at render time.
Do I need a licence key?
For AI translation, yes — the free plan is enough to try it on a real page. Everything
else (routing, hreflang, the switcher, the editor, manual translation, import and
export) works without one.
What happens if I deactivate it?
Your pages go back to their original language. Stored translations stay in the database.
I already use WPML or Polylang. Do I have to redo the work?
No. Import / Export reads what the other plugin still serves on this site and writes it
into Lingomize’s own table, page by page. Nothing is sent anywhere to do it.
Screenshots






Changelog
0.3.8
- The og:locale tag now follows the page’s language, so a page in Thai says th_TH to
Facebook and other social sites instead of the site’s own locale. - The Flag setting on the Languages page is now Country. It sets both the flag and
og:locale. On Auto, English is en_US.
0.3.7
- Scans now get past host page caches (SiteGround and others). Before, every scan after
the first could be answered from cache, so pages were never recorded and showed as
“not scanned”. Run “Scan for new text” once after updating. - Fixed a scan URL that 404’d when other parameters followed the scan token.
0.3.6
- New Translations box on the edit screen of every page, post, product and custom post
type: how much of the page is translated per language (by a person or by AI), scan it,
and AI-translate the languages you tick. - Eye icons in that box show or hide the page’s translation per language. Hidden pages
stay translatable while you are logged in; visitors get the original. - “Don’t translate these pages” rules can now cover chosen languages only.
0.3.5
- A sentence that continues after a link or bold text (“…techniques, you’ll find…”)
is no longer split at the comma, so AI translation sees the whole sentence. Affected
sentences are collected again on the next scan and need translating once more. - Thai AI translation now uses a stronger model and reads more naturally.
0.3.4
- AI translation of headings now reads the page title and the section under each heading,
so a short heading such as “Ownership” is translated in the sense its section gives it.
Run “Scan for new text” once to pick this up for existing headings, then re-translate
them from Text: Type “Headings”, Status “AI translation”. - AI-translate in the editor and on the Text screen now uses each string’s real type
(heading, SEO title, label) instead of treating everything as body text.
0.3.3
- Language switcher flags are all the same size, and the square and circle shapes now
render as true squares and circles. - A generic switcher icon (globe, translate and so on) shows once in front of the
languages instead of before each one.
0.3.2
- A switched-off language now leaves the language switcher for logged-in editors too, and
the switcher preview in Settings. Editors can still open its pages to finish it. - In the front-end editor, accordion and tab toggles open again, so text hidden inside them
(FAQ answers, for example) can be clicked and translated.
0.3.1
- Switch a language off without removing it: visitors no longer see it, while its
translations stay and can still be finished and previewed. - “Don’t translate these pages” takes one rule per row: is exactly, starts with, contains,
ends with, or matches a pattern. Existing entries carry over unchanged.
0.3.0
- AI translation now runs on a Lingomize licence key, with a free plan to start. Plans
set how many original words the site may hold and a monthly AI-token allowance.
0.2.15
- Find & Replace across all translations is now limited to administrators.
- The page list no longer hands out draft-preview links for posts the user cannot edit.
0.2.14
- Fixed inline CSS and JavaScript leaking onto translated pages as visible text.
0.2.13
- First release on WordPress.org.
