String Catalog Logo
String Catalog
Start Free Log In
Skip to content
Home
Docs
Localize App Store and Google Play Metadata

Guides

Localize App Store and Google Play Metadata

Localize App Store and Google Play metadata in String Catalog with field guidance, locale-aware review, and export-ready output for launch workflows.

Use this workflow when you need to localize app store listing copy, not just in-app strings.

What This Covers

Store metadata localization is useful when your team wants to manage launch copy such as:

  • App name or title
  • Subtitle or short description
  • Promotional text
  • Longer store descriptions

The goal is to keep listing copy aligned with the release instead of managing it in disconnected documents or spreadsheets.

Typical Workflow

  1. Open your project's Metadata area.
  2. Choose the platform you want to work on.
  3. Enter or update the base-language store copy.
  4. Save the base values.
  5. Run localization for missing fields.
  6. Review localized output field by field.
  7. Export the finished metadata package for publishing or handoff.

Platform Coverage

Platform availability depends on the project and the assets connected to it.

  • Apple App Store metadata is available for supported projects.
  • Google Play metadata appears when the project includes the Android side of the workflow.

If your project covers both iOS and Android, String Catalog can help you keep both listing surfaces aligned.

Why Teams Use It

Teams usually add metadata localization when they want to:

  • Keep store copy close to the app release workflow
  • Catch field-level issues before publishing
  • Reduce hand-copying across locales
  • Export clean output for the next launch

Field Guidance and Review

Store metadata is reviewed differently from regular app strings because each field has a different job.

String Catalog helps teams review metadata with:

  • Field-by-field organization
  • Platform-aware copy structure
  • Locale-aware output
  • Export-ready formats for downstream publishing workflows

Exports

After review, teams can export store metadata for the next step in their release process.

Supported export paths include:

  • JSON export
  • CSV export

This keeps the final handoff cleaner than rebuilding each locale manually at the last minute.

Access and Availability

Store metadata localization is a paid workflow for teams that need launch-ready copy support beyond strings alone.

Common Mistakes

  • Treating store metadata like generic app strings instead of reviewing each field in context.
  • Updating listing copy without checking whether the base-language fields are complete first.
  • Assuming every project will automatically show both Apple App Store and Google Play surfaces.
  • Waiting until release day to review exported metadata for each locale.