LocalePro
Menu
FeaturesIntegrationsCompareDocsBlogPricingAccount

Docs

Connect DeepL or Google

Get a DeepL or Google Cloud Translation key and paste it into WordPress so LocalePro can translate.

LocalePro doesn’t sell translation credits. You get a key from DeepL or Google, paste it into WordPress, and that company bills you for what it translates.

You only need one. Connecting both is optional. If you do, and you leave the choice on automatic, LocalePro uses the second when the first is down, out of quota, or can’t handle that language.

This is separate from your LocalePro purchase. The yearly price 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 key and save.

LocalePro → Settings → Translation then shows that service as connected. Use Test a translation there before you turn languages on for visitors.

If Settings → Connectors is missing, put the key in wp-config.php instead:

define( 'LOCALEREADY_DEEPL_API_KEY', 'your-deepl-key' );
// or
define( 'LOCALEREADY_GOOGLE_TRANSLATION_API_KEY', 'your-google-key' );

A value set this way wins over anything typed into the screen.

Get a DeepL 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’ll recognize (the site domain is a good one), 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. LocalePro sends those to DeepL’s free address automatically. New accounts follow whatever plans DeepL lists. We don’t resell them.

DeepL bills by character. After the key works, set a monthly ceiling under Usage and spend so a crawler can’t run up a surprise invoice.

Get a Google Cloud Translation key

LocalePro uses Cloud Translation and an API key. It does not use a service-account file, and it is not the Google Translate website.

  1. Open the Google Cloud console and sign in.
  2. Create a project, or pick one you already use. Give it a name you’ll recognize.
  3. Turn on billing for that project. Google asks for 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, limit it to Cloud Translation API only, and copy it.

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

Don’t upload a service-account file. LocalePro won’t read it. If Google shows you a JSON file, you created the wrong kind of credential. Go back and create an API key.

Limiting the key to Cloud Translation means a leaked key can’t 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 languages. If you’re unsure, start with DeepL, and add Google later if a language you need isn’t covered. LocalePro says so on the Languages tab.

After the key is in

  1. Add your LocalePro key if you haven’t already, so you get updates.
  2. Turn on languages under LocalePro → Settings → Languages.
  3. Read Translate a site for what happens on the first visit.

If the Translation tab still says the service isn’t connected, you may have saved the key on a different site, or WordPress is reading an empty LOCALEREADY_* line in wp-config.php that overrides the field. That line wins when it’s set.