Localize your Google Play listing
Import your Google Play store listing into a project, translate it, and publish reviewed text into each Play language.
The Google Play connector is two-way. It reads your app's store listing in its source language, turns each field into a key in your project, and publishes reviewed translations back into each target language's listing. It never writes your source language.
What it translates
One connection covers one app. You choose which listing fields to translate: title, shortDescription and fullDescription. Only the fields you select become keys, and only those are written back. Other parts of a listing, such as the promo video, are left as they are.
Requirements
- Plan: Starter or above.
- Role: Admin of the project's workspace, or an Owner of its account.
- In Google Play Console: a service account with the Android Publisher API enabled, granted access to your app. Download the service account's JSON key.
- Your app's package name, for example
com.example.app. - Target languages added to your transglot project.
Connect
Open the CMS page
Open your project's settings, choose CMS, and pick Google Play in the CMS list.
Enter the app and key
| Field | What to enter |
|---|---|
| Package name | Your app's application ID, for example com.example.app |
| Source Play language | The Play language that holds your source listing, for example en-US. transglot only reads it |
| Service account JSON | Paste the whole contents of the JSON key file |
Map your languages
Under Locale → Play language, enter the Play language for each target language in the project, for example fr-FR for fr. A language you leave unmapped is skipped when publishing.
Choose the fields
Under Content types, select listing. Under Translatable fields, select the listing fields to translate.
Connect, test and sync
Select Connect, then Test connection, then Sync from CMS to import the listing. The service account key is stored encrypted and never shown again.
Publish translations back
Review the imported translations, then publish them with Publish to CMS, or turn on automatic publishing when a translation is reviewed. Only reviewed translations are published. Connect a content platform describes reviewing and publishing in full; it works the same way here.
Each publish writes every target language inside one Google Play edit and commits it once all of them are written. If any language fails, the whole edit is discarded, so your listing never ends up half updated and no unfinished edit is left behind in Play Console. Importing never commits anything.
Troubleshooting
Check that the JSON key is complete and has not been deleted in Google Cloud, and that the service account has been granted access to this app in Play Console.
Use the application ID exactly as it appears in Play Console: segments separated by dots, each starting with a letter, for example com.example.app.
It has no Play language under Locale → Play language, or none of its translations are reviewed yet.
Related
Localize your App Store listing
Import your App Store Connect listing into a project, translate it, and publish reviewed text into each App Store locale.
Connect Amazon S3 or Dropbox
Localize locale files that live in an S3 bucket or a Dropbox folder: pull the source file in, translate it, and write the target-locale files back next to it.