WordPress translation plugin

Translate your WordPress site into 108 languages.

WPGlotty sends your pages to Claude, DeepL or OpenAI and stores the translations. It works on the finished HTML page rather than on individual WordPress filters, which is why page-builder output, menus, footers, image alt text and SEO fields get translated too. Any sentence that comes out wrong, you correct by clicking it on your own site.

Languages
108
You supply
Your own API key
Requires
WP 6.4 · PHP 8.1
example.com/en/services/ EN

Services

Request a quote

edit

We work with clients who know exactly what they want to say, and in which language.

nl Vraag een offerte aan
en Request a quote
7 pages saved

en Request a quote

  • nl Vraag een offerte aan
  • de Angebot anfordern
  • fr Demander un devis
  • es Solicitar presupuesto
  • ja 見積もりを依頼
  • +103

How it differs

Why it finds text that other plugins miss.

most translation plugins

They hook WordPress filters

A plugin can only translate the text it is handed. Post content, yes. But your page builder’s header, a popup, or a label another plugin prints in a template only get translated if someone wrote an integration for that specific case. The rest stays in the original language, and you usually find out from a customer.

wpglotty

It reads the finished HTML

WPGlotty waits until WordPress, your theme, your page builder and every other plugin have finished building the page. Then it reads that HTML, finds the text and the text-carrying attributes, and replaces them. It does not matter which plugin produced the words.

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

Three steps.

  1. Add the languages you want

    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.

    Settings → Languages

  2. Let it translate the site

    WPGlotty finds your URLs, works through them in batches and stores the translations. A page it has not processed yet is translated the first time someone opens it, so a visitor never sees the original language by accident.

    wp bdt translate --lang=nl

  3. Fix what reads badly

    Open your own site in editing mode, 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.

    Front end → Edit translations

Coverage

What gets translated.

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.

Text on the page

  • 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”.

Text you cannot see

  • 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.

Shop and forms

  • 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

The AI writes the first version. You fix what it gets wrong.

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.

  • once A correction is stored per piece of text, so it applies on every page where that text appears.
  • locked Text you edited yourself is marked as such. Translating the site again will not overwrite it.
  • upfront A glossary tells the AI how to handle product names and jargon before it starts.
  • skipped Exclusions leave chosen elements, words or entire pages in the original language.
Strings lang = nl
SourceDutchStatus
Request a quote Vraag een offerte aan 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

What you decide, not the AI.

who translates

Claude, DeepL or OpenAI — your choice.

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. You can switch at any time; translations you already have stay as they are.

anthropicdeeplopenai

what it costs

A monthly limit you set yourself.

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

Words that must stay as they are.

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

Every language gets its own URLs.

nl example.com/nl/diensten/

de example.de/leistungen/

hreflang tags
Tell Google which languages a page exists in, so it shows the right one per country.
Translated slugs
The words in the address bar are translated too, per language.
A sitemap per language
Each language gets its own sitemap, so every version can be indexed.
Canonical URLs
Each language points at itself, so your translations do not compete with your originals.

Works with

  • Breakdance
  • WooCommerce
  • ACF
  • Yoast SEO
  • Rank Math
  • SEOPress
  • WP-CLI
  • Gutenberg blocks

or from the command line

$ wp bdt translate --lang=nl --batch=50
  → discovering URLs           318 found
  → segmenting DOM             4,812 strings
  → provider anthropic/claude  ok
  ✓ nl complete — hreflang + sitemap written

Requirements

WordPress
6.4 or newer
PHP
8.1 or newer
Storage
Its own database tables. Nothing is added to your posts
Caching
Clears the changed page in WP Rocket, W3TC, LiteSpeed and nginx-helper
Licence
GPL-2.0-or-later
Version
0.18.23

Questions

Questions people ask first.

Does it slow my site down?

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.

What happens if I turn it off?

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.

Who pays for the translation itself?

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.

Can I change a translation without changing the original?

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.

Do I need a page builder for this?

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

Free while it is in beta.

Make an account, get a licence key, paste it 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.

Free

While WPGlotty is in beta · one site per licence

  • As many of the 108 languages as you want
  • The editor, the glossary and the exclusion rules
  • hreflang, translated slugs, sitemaps and canonicals
  • WooCommerce, ACF and Breakdance support
  • WP-CLI commands for translating, import and export
Get your licence

Questions first? Write to us.