Guides

Store-specific text, then the right languages

Use verified App profile facts to draft listing copy. Keep each store’s fields and character limits, and review every localized result before delivery.

Studio provides ASO drafting and localization alongside the visual asset workflow. Follow the API examples below to automate supported tasks. Google Play uses title (30), short description (80) and full description (4000); it has no separate keyword field. App Store uses name (30), subtitle (30), promotional text (170), keywords (100) and description (4000).

Generate the base listing

Choose a store and supply your App profile’s appId. Optional campaignFocus is up to 1000 characters: explain the desired audience, verified benefits and claims to avoid. The completed job returns kind: "aso-listing", a saved listing ID, locale en-US and only the selected store’s final fields.

POST/developer/aso

Body

{
  "appId": "665f0a2b9c1e4d0012ab34cd",
  "store": "google",
  "campaignFocus": "Use the verified Android features in this App profile. Emphasize simple meal logging and fasting. Do not invent free access, ratings, prices or platform integrations."
}

Persist a separate idempotency key for this generation, poll GET /developer/jobs/{id}, and save the completed result. A saved draft is not a store publication.

Translate your completed listing

Use the completed Developer ASO job ID and 1–10 unique target locales supported by the API. The source determines the store and App profile. Translation uses that job’s final text snapshot, so a later edit to the Studio draft does not change this request.

POST/developer/aso/localize

Body · replace the completed source job ID

{
  "jobId": "66a1f0c2b7e4d90012cd5678",
  "targetLocales": [
    "en-AU",
    "en-CA",
    "en-GB"
  ]
}

The completed job returns kind: "aso-localization" and a listings array containing each saved locale and its final fields. Keep polling a pending job; do not submit a duplicate because it has not started yet. Review regional spelling, unsupported claims and length limits. Locale order does not change the identity of an otherwise identical keyed request.

Deliver exact reviewed fields

Export or copy the text, or prepare a publishing manifest containing the exact final fields for each locale. Text and screenshot localization are separate operations. Google Play can use default-language graphic assets when a translation has no localized graphics; existing locale-specific images remain in place.

Keyword ideas are editorial suggestions. AppListingLab does not report measured search volume, keyword rank or guaranteed conversion results.