LocaleReady
Menu
FeaturesIntegrationsCompareDocsJournalPricingAccount

Docs

Get a translation API key

How to get a DeepL or Google Cloud Translation key and paste it into WordPress so LocaleReady can translate.

LocaleReady does not sell translation credits. You get a key from DeepL or Google Cloud, paste it into WordPress, and that company bills you for what it translates.

You only need one. Connecting both is optional. LocaleReady will use the second if the first is down or out of quota.

This is separate from your LocaleReady license. The license is the plugin. The key is the translator.

Where the key goes

  1. In WordPress, open Settings → Connectors.
  2. Find DeepL or Google Cloud Translation.
  3. Paste the API key and save.

LocaleReady → Settings → Translation then shows that service as connected. Use Test a translation there before you turn on languages for the public site.

If Settings → Connectors is missing (an older WordPress), put the key in wp-config.php instead:

define( 'LOCALEEASY_DEEPL_API_KEY', 'your-deepl-key' );
// or
define( 'LOCALEEASY_GOOGLE_TRANSLATION_API_KEY', 'your-google-key' );

Get a DeepL API key

You need a DeepL API plan, not a regular DeepL Translator login. Those are different products.

  1. Open DeepL’s API plans and create an account on a plan they currently sell.
  2. Sign in and go to Account → API Keys & Limits.
  3. Click Create key, give it a name you will recognize (for example, the site domain), and create it.
  4. Copy the key once. DeepL will not show the full value again.

Paste that key under Settings → Connectors → DeepL.

If you already have an older Free key, it usually ends with :fx. LocaleReady sends those to DeepL’s free endpoint automatically. New accounts follow whatever plans DeepL lists on that page. We do not resell or wrap them.

DeepL bills by character. After the key works, set a monthly ceiling in LocaleReady under Usage & spend so a crawler cannot run up a surprise invoice.

Get a Google Cloud Translation API key

LocaleReady uses Cloud Translation Basic and an API key, not a service-account JSON file, and not the consumer “Google Translate” website.

  1. Open the Google Cloud console and sign in with a Google account.
  2. Create a project, or pick one you already use. Give it a name you will recognize.
  3. Enable billing on that project. Google requires a billing account even when you stay inside their free monthly allowance.
  4. Open Cloud Translation API and click Enable.
  5. Go to Credentials → Create credentials → API key.
  6. Open the new key, restrict it to Cloud Translation API only, and copy it.

Paste that key under Settings → Connectors → Google Cloud Translation.

Do not upload a service-account JSON. LocaleReady will not read it. If Google shows you a JSON file, you created the wrong kind of credential. Go back and create an API key.

Restricting the key to Cloud Translation API means a leaked key cannot call your other Google services. Still treat it like a password.

Which one should I pick?

Either works. DeepL is the usual first choice for European languages. Google covers more language pairs. If you are unsure, start with DeepL; add Google later if a language you need is not covered (LocaleReady says so on the Languages tab).

After the key is in

  1. Activate your license if you have not already.
  2. Enable target languages under LocaleReady → Settings → Languages.
  3. Read Translate a site for what happens on the first visit.

If the Translation tab still says the service is not connected, you saved the key on a different site, or WordPress is reading an empty LOCALEEASY_* constant that overrides the Connectors field. The constant wins when it is set.