WordPress translation plugin
WPGlotty is a WordPress translation plugin that does the whole site in one go, into any of 108 languages, using your own Claude, DeepL or OpenAI key. You pay them their price and we take nothing per word. It covers the parts other plugins miss: your page builder, your menus, your image descriptions and everything Google reads. Anything that comes out wrong, you fix by clicking it on your own site.
You bring your own API key — Claude, DeepL or OpenAI. They do the translating and they bill you, at their own rates. We add nothing per word. Set a monthly spending limit in the plugin and it stops when it reaches it.
Services
We work with clients who know exactly what they want to say, and in which language.
en How we work
Why people keep it
What it costs you
No tier, no per-word fee.
Claude, DeepL or OpenAI on your key. You pay them at their price; we take nothing per word.
Every language, every feature, every integration. Nothing is held back for an upgrade.
It counts what each translation costs, warns you on the way up, and stops at your monthly maximum.
Run a dozen sites on one provider account? Store the key once with us, strongly encrypted, and set up each site with a code that lasts fifteen minutes. Optional.
What it does
Translate once, then forget about it.
Press translate and it works through your pages. Anything it has not reached is done the moment somebody opens it.
Change a sentence and it redoes exactly the translations that went stale. New pages are picked up as they appear.
On your own site, in place. Your correction is never overwritten: not by a later run, not by a better model.
Own address, own sitemap, hreflang. Your languages do not compete with each other, and none of it needs setting up.
On your site
It behaves like a good guest.
Upload, paste your key, choose languages. No service to connect and no code to touch.
Pages come from your own database, so visitors wait for nobody and your page cache keeps working.
Your posts are not rewritten and your builder is not touched. Remove it and the site is as it was.
One address, and the person who answers is the one who wrote the code. If it turns out to be a bug, it is fixed and released, and you are told which version it landed in.
Features
Not a list of things nobody else does. A list of the things people expect to pay more for, which here are simply included. Where somebody charges extra for one, it says so.
Translating
Press translate and it works through your pages, posts, products, menus and widgets. Anything it has not reached yet is done the moment somebody opens it.
Every new page, post and product is translated as it appears, with nobody pressing anything. Change one sentence in the original and only that translation is redone.
Click any sentence on your own site and rewrite it. What you change is marked as yours and no later run overwrites it.
Elsewhere: WPML: CMS plan, €99
The words that are not in your content: buttons, labels, error messages, everything a theme or plugin puts on the page.
Elsewhere: WPML: CMS plan, €99
Terms you never want translated, and an instruction about how your brand sounds. Both travel with every request.
Names, product codes, snippets of code and anything else that should survive untouched. Written once as a rule rather than corrected on every page.
Your own account, your own key, their price. Switch model per language when one turns out to suit a market better.
Elsewhere: TranslatePress: Business plan, €199 for DeepL
Nothing is metered by us. You set a monthly ceiling at your provider and the plugin stops before it passes it.
Elsewhere: Capped on every plan at all three
On your site
Products, variations, attributes, categories and the checkout strings. It is on the page, so it is translated.
Elsewhere: WPML: CMS plan, €99
Elementor, Divi, Bricks, Breakdance and the rest, with no integration to install. Builder output is read like any other markup.
Elsewhere: WPML: CMS plan, €99
A block, a shortcode, a menu item or a Breakdance element, with your own styling rather than a fixed widget.
On every licence. Adding a market costs the translating and nothing else.
Elsewhere: Weglot: 1, 3, 5 or 10 by plan
What Google sees
Translated URLs, hreflang between every language, canonicals and a sitemap per language. Nothing to configure.
Elsewhere: TranslatePress: SEO Pack · WPML: CMS plan
A subdirectory, a subdomain or a separate domain for each language, whichever suits the market.
Elsewhere: TranslatePress: Business plan, €199
Send a visitor to their own language on arrival, from their browser or their country.
Elsewhere: TranslatePress: Business plan, €199
Translations are written into your site, not served from ours. Stop paying and they keep being served, in every language.
Elsewhere: Weglot: they stop appearing
Plans and prices for TranslatePress, WPML and Weglot taken from their own pricing pages on 3 September 2026. If something here has gone out of date, tell us.
Pricing
Every plan has every feature. What changes is how many sites you may run it on. There are no word limits, no charge per language, and nothing is metered by us, because the translating is done by your own provider account at whatever they charge you.
One site, everything switched on.
€3 per month
Billed yearly at €36, excluding VAT.
Five sites for a small team.
€8 per month
Billed yearly at €96, excluding VAT.
Unlimited sites for people who build for others.
€15 per month
Billed yearly at €180, excluding VAT.
Thirty days to change your mind. Not what you hoped for? Send one email inside thirty days and you get every cent back, with no form to fill in and nobody asking why. The translations already on your site stay where they are.
Prices exclude VAT, which is worked out at checkout from your country and your VAT number. Payment is handled by Stripe; no card details ever reach this site.
How the three compare
TranslatePress and WPML are good plugins with a lot of history behind them. Where WPGlotty differs is not in what it can do, but in who you pay and how much is kept behind a plan.
| What | WPGlotty | TranslatePress | WPML |
|---|---|---|---|
| Who does the translating | Claude, DeepL or OpenAI on your own key | Their own AI, or DeepL and Google with your key on the Business plan and up | Their own service, paid for in credits |
| What a translated word costs | Whatever your provider charges. We add nothing | Included up to your plan’s allowance | 2 credits per word for Google or DeepL, 4 for their own engine |
| Words per year | No limit from us. You set a monthly ceiling | 50,000 · 200,000 · 500,000 by plan | 90,000 or 180,000 credits by plan |
| Features held back for a higher plan | None. Every feature on every licence | DeepL and Google need the Business plan | The advanced editor, string translation, WooCommerce and page builders need the CMS plan |
| Sites per licence | 1 · 5 · unlimited by plan | 1 · 3 · unlimited by plan | 1 · 3 · unlimited by plan |
| Price | €36 to €180 a year | €99 · €199 · €349 a year | €39 · €99 · €199 |
| Edit a translation on the page | Yes | Yes | Yes, on the CMS plan |
| hreflang, translated slugs, sitemaps | Included | In the SEO Pack, on the paid plans | Included on the CMS plan |
| Your content goes to | Your provider, directly. Never through us | Their translation service | Their translation service |
Line by line against each of them: WPGlotty as a TranslatePress alternative, as a WPML alternative, or as a Weglot alternative.
Taken from translatepress.com/pricing and wpml.org/purchase on 3 September 2026. They change their plans as we change ours, so check before you decide.
How it differs
most translation plugins
They can only translate the text they are handed. Your posts, fine. But your page builder’s header, a popup, a label from some other plugin: those work only if somebody wrote an integration for that exact case. The rest quietly stays in the original language, and you hear about it from a customer.
wpglotty
It waits until your theme, your page builder and every other plugin have finished making the page, then translates what is actually on it. Which plugin put the words there stops mattering. If a visitor can see it, it gets translated.
Translations are stored in the plugin’s own database tables. Your posts are not duplicated and your page-builder data is not rewritten, so the builder keeps working exactly as it does on a site with one language.
Setting it up
WPGlotty does not translate anything itself: an AI does, on your account. Paste in a key from Anthropic, DeepL or OpenAI and you pay them directly, at their price, with a monthly ceiling you set. Nothing is metered by us and your content never passes through our servers.
Pick from a list of 108. For each one you choose the URL structure (a subdirectory like /nl/, or a separate domain) and set the tone of voice and the level of formality the AI should use.
Press translate and it works through your pages one after another. Anything it has not reached yet is done the moment a visitor opens it, so nobody ever lands on a page in the wrong language while you wait.
Open your own site in the translation editor, click a sentence and type what it should say instead. The correction is stored for that piece of text, so it also applies on every other page where the same text appears.
Coverage
Everything below is text that ends up in the HTML your server sends, which is why WPGlotty can translate it. This is what works today, not a roadmap.
Post and page content
Including text that a shortcode or a block only produces while the page is being built.
Page-builder output
Breakdance headers, footers, templates, global blocks and popups.
Navigation menus
The menu labels. You can also show a completely different menu per language.
Theme and plugin strings
Text built into your theme or another plugin, such as “Add to cart” or “Read more”.
Image alt text
Plus title, placeholder and aria-label: the text screen readers and Google read.
SEO metadata
Titles, descriptions and Open Graph via Yoast, Rank Math or SEOPress.
Structured data
The text inside your JSON-LD. URLs, prices and status values are left untouched.
URL slugs
The words in the address bar, translated per language.
WooCommerce
Product names and descriptions, categories, the cart and the checkout.
Order emails
Sent in the language the customer ordered in, not the language of your site.
ACF fields
Text, textarea and wysiwyg fields, including ones nested in repeaters and groups.
Search
A visitor types a search term in their own language and still finds your pages.
Correcting translations
Machine translation is usually fine and occasionally picks the wrong word in a headline. To correct it you do not have to find that text in a list of thousands of strings: open your own site, click the sentence, and type what it should say.
| Source | Dutch | Status |
|---|---|---|
| Delivered in three working days | Binnen drie werkdagen geleverd | edited 7p |
| Free shipping over €50 | Gratis verzending vanaf €50 | machine 24p |
| Read the case study | Lees de case study | glossary 3p |
| Book a call | Plan een gesprek | machine 11p |
Settings
who translates
You enter your own API key, so you pay that company directly and we add nothing on top. Your content is sent to them and not to us. Run several sites? You can store the key on your account instead, encrypted, and let each site collect it. You can switch provider at any time; translations you already have stay as they are.
anthropicdeeplopenai
what it costs
WPGlotty keeps track of what every translation costs. Set a maximum per month and it warns you at the percentage you choose, then stops translating when the limit is reached instead of quietly running up a bill.
$4.21 / $25.00warn at 80%
how it writes
A glossary fixes product names, legal terms and jargon in advance. Tone of voice and formality are set per language: whether Dutch uses “je” or “u”, for instance. Exclusions leave chosen elements, words or pages untranslated.
31 glossary terms12 exclusions
URLs and SEO
nl example.com/nl/diensten/
de example.de/leistungen/
Works with
If you look after a lot of sites, everything on this page can also be done from the command line: translating, importing and exporting.
Requirements
Questions
A page that has already been translated is served from the database, so there is no call to the AI while a visitor waits. A page nobody has opened yet is translated once, on that first visit, and then stored. Page caching plugins keep working: WPGlotty clears the pages it changes in WP Rocket, W3 Total Cache, LiteSpeed and nginx-helper, and tells you in the admin if it finds a cache it cannot clear itself.
Your site goes back to one language, exactly as it was. Nothing was duplicated and no page-builder data was changed, so there is nothing to undo. If you delete the plugin, its tables are removed too, but only if you switch that option on first. Leave it off and your translations are still there after a reinstall.
You do, directly to Anthropic, DeepL or OpenAI, using your own API key. We add nothing on top and your content is never sent through our servers. Set a monthly maximum in the settings and the bill stays predictable.
Yes. That is what the editor is for. Text you edit yourself is marked as edited by a person, and translating the site again will not overwrite it.
No. WPGlotty reads the finished page, so a classic theme, a block theme and a page builder are all the same to it. There is a specific Breakdance integration because builder output is exactly where other translation plugins tend to give up.
Get it
Make an account, pick a plan, paste the key into the plugin. You add your own API key for Claude, DeepL or OpenAI and pay them directly for the translation. We charge nothing per word, and your content does not pass through our servers.
Every plan
No word limits and nothing held back for a higher tier
You have this. Your key is on your dashboard.
Cookies
The site needs a couple of cookies to sign you in. Beyond that we would like to know which pages people read, and whether our advertising reaches anyone. Neither happens unless you say so. What we collect.