localization

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "localization" with this command: npx skills add eronred/aso-skills/eronred-aso-skills-localization

App Store Localization

You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively.

Initial Assessment

  1. Check for app-marketing-context.md — read it for current markets and languages
  2. Ask for the App ID (to see current localizations)
  3. Ask: Is the app itself localized (UI, content) or just the store listing?
  4. Ask: Which markets are they considering?
  5. Ask: Budget — professional translation or AI-assisted?

Market Prioritization

Tier 1 Markets (highest ROI for most apps)

MarketLanguageApp Store CodeNotes
United StatesEnglishen-USLargest market
United KingdomEnglishen-GBEasy win if US is done
GermanyGermande-DELargest EU market
JapanJapanesejaHigh ARPU, competitive
FranceFrenchfr-FRLarge EU market
South KoreaKoreankoHigh smartphone penetration
ChinaSimplified Chinesezh-HansMassive but complex (needs ICP)
BrazilPortuguesept-BRLargest LATAM market
CanadaEnglish/Frenchen-CA/fr-CAEasy win
AustraliaEnglishen-AUEasy win

Tier 2 Markets (good potential)

Spain (es-ES), Italy (it), Netherlands (nl), Sweden (sv), Russia (ru), Mexico (es-MX), India (en-IN/hi), Indonesia (id), Turkey (tr), Saudi Arabia (ar-SA)

How to Choose

Evaluate each market on:

FactorWeightHow to assess
Market size30%iPhone user base in country
Competition25%How many localized competitors?
Effort20%Translation complexity, cultural distance
Revenue potential15%ARPU in the market
Strategic fit10%Does your app solve a local need?

Localization Checklist

Metadata Localization

For each target market:

  • Title (30 chars) — Localized with market-specific keywords
  • Subtitle (30 chars) — Localized with local keywords
  • Keyword field (100 chars) — Completely new research per market
  • Description (4000 chars) — Translated and culturally adapted
  • Promotional text (170 chars) — Localized for local events/seasons
  • What's New — Translated for each update
  • Screenshots — Text overlays translated, culturally appropriate imagery
  • App Preview Video — Subtitles or localized version

Critical: Keywords Are NOT Translations

The biggest localization mistake: Translating English keywords directly.

Instead:

  1. Run keyword-research for each target market separately
  2. Understand how locals search (different terms, different intent)
  3. Use local autocomplete suggestions
  4. Check what local competitors use in their metadata

Example:

  • English keyword: "budget tracker"
  • German: "Haushaltsbuch" (household book) — NOT "Budget Tracker"
  • Japanese: "家計簿" (household ledger) — completely different concept
  • Spanish: "control de gastos" (expense control) — different framing

Cultural Adaptation

ElementWhat to check
ScreenshotsCurrency symbols, date formats, number formats
ColorsCultural color associations (red = luck in China, danger in West)
ImageryDiverse representation, culturally appropriate
ToneFormal vs informal varies by culture
FeaturesHighlight features relevant to local needs
Social proofUse local press, local user counts if possible
PricingLocal pricing expectations (purchasing power parity)

Localization Workflow

Phase 1: Research (per market)

  1. Analyze top 10 apps in your category in the target market
  2. Run keyword research with local seed terms
  3. Identify local competitors and their positioning
  4. Understand local App Store trends

Phase 2: Translation & Adaptation

For metadata (title, subtitle, keywords):

  • Use native speakers with ASO knowledge (not just translators)
  • Provide context: "This is an App Store title, must include [keyword]"
  • Review with keyword data — does the translation include high-volume terms?

For description:

  • Professional translation with cultural adaptation
  • Not word-for-word — adapt examples, references, humor
  • Maintain the same persuasive structure

For screenshots:

  • Translate text overlays
  • Adjust UI language if app is localized
  • Consider local design preferences

Phase 3: Launch & Monitor

  1. Submit localized metadata
  2. Monitor keyword rankings in each market (weekly)
  3. Track conversion rate by country
  4. Iterate based on performance data

Output Format

Localization Plan

For each recommended market:

## [Country] — [Language]

Priority: [High/Medium/Low]
Estimated effort: [hours/days]
Expected impact: [download increase estimate]

Keywords (top 10):
| Keyword | Volume | Difficulty | English equivalent |
|---------|--------|------------|-------------------|

Metadata:
- Title: [localized title] ([X]/30 chars)
- Subtitle: [localized subtitle] ([X]/30 chars)
- Keywords: [localized keyword field] ([X]/100 chars)

Cultural notes:
- [specific adaptations needed]

Market Prioritization Matrix

MarketSizeCompetitionEffortRevenueScorePriority

Related Skills

  • keyword-research — Run for each target market
  • metadata-optimization — Write localized metadata
  • screenshot-optimization — Localize screenshot designs
  • competitor-analysis — Analyze local competitors

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Research

keyword-research

No summary provided by upstream source.

Repository SourceNeeds Review
Research

competitor-analysis

No summary provided by upstream source.

Repository SourceNeeds Review
General

monetization-strategy

No summary provided by upstream source.

Repository SourceNeeds Review