Translation service

DeepL or Google bill you directly for new text. The yearly LocalePro price is for the plugin, not a markup on translation.

Connecting a service

You need a key from DeepL, Google, or both. LocalePro does not create those keys. Connect DeepL or Google walks through each one. Then paste the key under Settings → Connectors.

The Translation tab shows each one as connected or not, with a link straight to that screen.

You don’t have to pick only one. With both connected, set the service to Automatic. LocalePro tries them in order, and uses the next if the first is unreachable, out of quota, or doesn’t support that language. A visitor doesn’t see the failure. They see a translation from whichever service answered.

Testing

Test a translation sends a short piece of text to one connected service and shows what came back: the translation, which service answered, and how long it took. This is a real request. It counts toward the same monthly usage as everything else, and it is not saved.

Names that must stay as written

Brand and product names a translator would otherwise “helpfully” translate. “Acme Cloud” becoming “Nube Acme” is the usual example. List a name once and it passes through every service exactly as written, in every language. Translations you already have are not rewritten. Regenerate one from the Translations screen if you add a name after the fact.

Two other kinds of text are protected on their own, with no list to keep:

• Prices. “$13.50”, “13,50 €”, and “13.50 USD” are recognized and held back before the request is even sent.
• Placeholders. A theme or plugin might write ### and fill in a number later. Those tokens are set aside so the translator can’t move or break them.

When a translation fails

If the service returns nothing for a sentence, you choose what a visitor sees: your original text, or nothing. Original text is the default, and the safer one. A sentence in the wrong language is still readable. A sentence that vanishes usually isn’t.