Your Cart
WPML translation service setup

How to Set Up WPML Translation Service Connection and Manage Translation Delivery

Connecting WPML to a professional translation service is not a single action. A reliable workflow has four separate stages: authenticate the service, send content for translation, receive the completed work, and control whether unfinished language versions are visible to normal visitors. Keeping these stages separate makes configuration easier to test and troubleshoot.

WPML offers a generic connection process, but the selected translation service remains responsible for its own account, credentials and service-specific onboarding. Automatic delivery is also conditional: it works when the connected service supports that method. This guide explains the documented paths for listed and unlisted services, shows where the Activation Key and API Token are entered, and explains how to use automatic or manual translation pickup while incomplete languages remain hidden from the public front end.

What the WPML Translation-Service Workflow Includes

Connection, delivery and visibility are different controls

First, connect and authenticate the translation service. This only establishes the relationship between WPML and the selected provider; it does not automatically send every page or post for translation. Job submission is a separate task performed from WPML → Translations.

After content has been submitted, completed translations must be delivered back to WPML. If the service supports automatic delivery, WPML can receive and publish completed translations through the configured pickup mode. Otherwise, an administrator can retrieve them manually. Finally, language visibility is managed separately. Hiding a target language keeps unfinished translations away from normal visitors, while selected logged-in users may still be allowed to work with that hidden language.

Before You Connect a Translation Service

Separate WPML registration from translation-service authentication

Before opening the translator settings, establish which type of service you are connecting. A service listed by WPML uses the listed-service workflow and API-token authentication. A service outside WPML’s default list must provide both an Activation Key and an API Token. Obtain those credentials from the translation service’s official documentation or account area. Their location, format and onboarding process may vary by provider.

Do not confuse WPML’s own site key with a translation service’s Activation Key. The WPML site key is entered under WPML → Activate & Update. The translation service’s Activation Key and API Token belong to the connection workflow in WPML → Settings → Translators. They are different credentials with different purposes.

Choose the site instance on which you will test the workflow. Before relying on automatic delivery on a production site, use limited content and confirm whether the intended recipient is production, staging or a development copy. Keep all credentials private. Do not place site keys, Activation Keys or API Tokens in screenshots, tutorials, support tickets or public repositories.

How to Connect a Listed Translation Service

Use the setup wizard or Translators settings

WPML documents two starting points for connecting a professional translation service. During initial configuration, use the WPML setup wizard. On an existing site, open WPML → Settings → Translators. Both paths lead to the service-connection workflow, so the choice depends on whether WPML is being configured for the first time or adjusted later.

From the available services, select the professional translation service you intend to use. WPML then requires authentication with an API token. Get that token according to the selected service’s own instructions. Do not assume that every provider issues tokens in the same place or uses the same format, and do not reuse credentials from another service.

Successful authentication means that the service connection has been configured. It does not mean that content has already been submitted. To create a translation job, you must separately select content in WPML and assign it to the connected service. Account management, billing and service-specific support also remain matters for the connected provider rather than generic WPML settings.

How to Add a Service Not Listed by Default

Activation Key first, API Token after authentication

An unlisted service follows a distinct credential sequence. The service must provide an Activation Key and an API Token. Start by opening WPML → Settings → Translators and expanding the Translation Services area. Choose Activate a translation service that’s not listed here.

Enter the translation service’s Activation Key in the activation area. After the service has been added, use its Authenticate action and enter the service’s API Token. The order matters: the Activation Key activates the unlisted service entry, while the API Token is supplied during authentication.

This is not the same as entering WPML’s site key under WPML → Activate & Update. Keep the two workflows separate when documenting the setup or diagnosing a failed connection. If the service provides additional onboarding instructions, follow those instructions for obtaining and using its credentials. The generic WPML flow does not establish a universal token format or identical account process for every provider.

Protect both credentials after setup. Do not publish them, include them in a public code repository, or expose them while asking for configuration assistance. The connected service remains responsible for its own account conditions and service-specific delivery support.

Sending Translation Jobs and Choosing Delivery

Automatic pickup versus manual retrieval

Once the service is authenticated, send work from WPML → Translations. Select the content that should be translated, choose Assign translation service, and send it for translation. This step turns selected content into a translation job; connecting the service alone does not submit content.

To configure delivery, open WPML → Settings → Translators and find Translation pickup mode. When the connected service supports automatic delivery, select the automatic option in which the service delivers completed translations to WPML. In that workflow, WPML can receive and publish completed translations automatically.

Automatic delivery is not universal. Its availability depends on the connected translation service, so verify that the provider supports the selected method before relying on it. Test the process with limited content first, especially when several copies of the site exist. Confirm which instance receives the translations and review the result before treating the workflow as ready for regular production use.

If automatic delivery is unavailable or does not retrieve a completed job, use the manual fallback. Go to WPML → Translations and choose Check status and get translations. This gives the administrator a documented way to check for completed work and retrieve it without assuming that an unavailable automatic pickup means the translation job has been lost.

Automatic pickup and manual retrieval are separate operating modes. Choose the mode supported by the service, and use the manual status check when automatic retrieval does not bring the expected work into WPML.

How to Hide Languages During Translation

Public visibility and editor access are separate

Unfinished translations do not have to be shown to normal visitors. To hide a target language, go to WPML → Settings → Languages, find the relevant language, select Hide, and save the setting. The hidden language then remains unavailable on the normal front end while the translation work continues.

Hiding a language controls public visibility; it does not automatically mean that every internal user loses access. If translators or editors need to review hidden-language content, enable Display hidden languages in the relevant user profile. This separates what normal visitors can see from what selected logged-in users can review or manage.

Test the visibility behavior on the site before publishing the workflow. Language hiding should not be presented as a replacement for editorial review, access control, staging or backups. It is a front-end visibility setting that helps keep incomplete translations unavailable to ordinary visitors while authorized users continue working.

Troubleshooting and Production Checks

A practical pre-production checklist

When the workflow does not behave as expected, check each stage separately instead of treating the entire integration as one operation. Start with credentials and authentication, then confirm job submission, delivery mode and language visibility.

  • Authentication: confirm that the correct credentials belong to the selected translation service and that the service was authenticated in the Translators settings.
  • Job submission: confirm that content was selected in WPML → Translations, assigned to the translation service and actually sent.
  • Delivery support: verify that the connected service supports automatic delivery before expecting the automatic pickup mode to retrieve completed work.
  • Manual fallback: if automatic retrieval is unavailable or does not retrieve the job, use Check status and get translations.
  • Site instance: test with limited content and confirm whether the translation is arriving on the intended production, staging or development copy.
  • Visibility: check that the target language is hidden from normal visitors and that only intended logged-in users can display hidden languages.
  • Interface wording: compare menu labels with the WPML version used when the workflow is published, because documented interface labels may change between versions.

Do not expose credentials while diagnosing a connection. Also avoid treating automatic delivery as universal or assuming that a successful connection proves that delivery, publication and front-end visibility are configured correctly. Review the complete path with a small job before expanding it to more content.

The practical order is straightforward: authenticate the selected service, send content through WPML → Translations, use automatic pickup only when the service supports it, and otherwise retrieve work manually. While translations are incomplete, hide the relevant language and give selected editors access through their profiles when needed. Keep WPML registration separate from translation-service credentials, and verify service-specific account and delivery conditions with the provider. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń