DeepL
Your DeepL key. Your WordPress database.
LocaleReady is the plugin that sits between WordPress and DeepL. You pay DeepL for characters. You pay us a yearly site license.
Most "DeepL for WordPress" tools either paste a widget on the page or wrap DeepL inside a monthly plan that grows with traffic. LocaleReady does neither. You create an API key on DeepL's own site, paste it under Settings → Connectors, and the plugin sends only strings it has never seen before.
The first visitor to a new sentence pays the DeepL call. After that the translation is served from your database. Cancel the LocaleReady license and those stored strings still render. You would only lose new translation going forward.
Brand names and prices are the usual DeepL failure modes. LocaleReady leaves prices alone and lets you pin protected terms so "LocaleReady" does not become a local pun.
Setup notes live intranslation service docsandhow to get an API key. Google Cloud Translation isdocumented the same way.
Questions
Is LocaleReady a DeepL plugin?+
It is a WordPress translation plugin that can use DeepL as the engine. You create the DeepL API key. LocaleReady calls it, stores the result, and does not resell DeepL credits.
Can I use Google Cloud Translation instead?+
Yes. Connect either key, or both, and pick a primary. See the Google Cloud page if that is the engine you already have.
Do you mark up the page with DeepL widgets?+
No. The visitor gets normal HTML on your domain. DeepL only sees the missing strings on the first pass.
Connect DeepL and translate the first page
Yearly license by site count. DeepL bills you for the characters you have not stored yet.