LocalizeASO Logo LocalizeASO
Start free

Metadata localization

The metadata screen loads App Store Connect metadata and merges it with LocalizeASO drafts. For agent-generated changes, create a metadata field-review job so every locale and field shows current value, proposed value, keyword signals, warnings, and diff before anything is applied or submitted.

Fields

LocalizeASO supports:

  • Title.
  • Subtitle.
  • Keywords.
  • Description.
  • Promotional text.
  • What’s new.
  • Marketing URL.
  • Support URL.

The app also stores metadata settings such as app name, title structure, update instructions, create instructions, optimize instructions, default what’s new text, and support URL templates.

Review modes

The dashboard supports three metadata proposal modes:

  • Update: rewrite existing locale fields.
  • Create: create missing locale metadata.
  • Optimize: improve existing metadata against ASO rules and imported keywords.

Each mode can use custom instructions. Hosted LocalizeASO AI or a BYO Codex/AI agent can create the proposal, but approval, draft apply, and App Store Connect submit remain human-only steps.

Title structure

The metadata settings include title style and casing. This lets you control whether generated titles include the app name or focus on main keywords only.

Validation

LocalizeASO validates fields before approval and post-approval submit. It checks App Store field limits and keyword usage across title, subtitle, and keyword fields.

Current limits:

| Field | Limit | | --- | ---: | | Title | 30 | | Subtitle | 30 | | Keywords | 100 | | Promotional text | 170 | | Description | 4000 | | What’s new | 4000 |

Drafts

Edits are stored as drafts per app and locale. Approved field-review proposals can be applied to drafts, exported to local asc metadata files, or submitted through hosted LocalizeASO if the active pass includes hosted App Store Connect submit convenience.

Release notes

Release notes can be generated and reviewed separately. Hosted submit routes still require explicit human review confirmation, and field-review handoffs should be used for agent-generated release-note changes.

Support URLs

Support URLs can be templated and reviewed per locale. Use this when each locale needs a local support or help page URL; hosted submit still requires explicit human confirmation.