localization
eronred/aso-skills
Expand your app to international markets with strategic localization and culturally-adapted App Store listings.
What is localization?
This skill guides you through localizing your App Store presence for new markets. Use it when planning international expansion, translating app metadata, or deciding which countries to target. It covers market prioritization, keyword research per locale, and cultural adaptation—not just translation.
- Assess current localization status and identify target markets based on size, competition, ARPU, and effort
- Prioritize markets using a weighted framework (Tier 1 includes US, UK, Germany, Japan, France, Korea, China, Brazil)
- Research local keywords for each market—avoiding the mistake of translating English keywords directly
- Localize metadata (title, subtitle, keywords, description, screenshots) with cultural and linguistic adaptation
- Provide a localization checklist and phased workflow (research, translation/adaptation, launch & monitor)
- Monitor keyword rankings and conversion rates by country post-launch
How to install localization
npx skills add https://github.com/eronred/aso-skills --skill localization- App ID (to review current localizations)
- Clarity on whether the app itself is localized (UI/content) or only the store listing needs localization
- Target market list or willingness to evaluate Tier 1 and Tier 2 markets
How to use localization
- 1.Check app-marketing-context.md for current markets and languages
- 2.Provide your App ID and clarify localization scope (app UI vs. store listing only)
- 3.List candidate markets or review the Tier 1/Tier 2 market table
- 4.Evaluate each market on the five factors: size, competition, effort, ARPU, and strategic fit
- 5.Run keyword-research skill for each target market to find local search terms (not translations)
- 6.Use the localization checklist to plan metadata, screenshots, and cultural adaptations per market
- 7.Submit localized metadata and monitor keyword rankings and conversion rates weekly
Use cases
- Deciding which 3–5 new countries to enter based on market size and competitive landscape
- Localizing metadata for a German or Japanese market where keywords differ fundamentally from English
- Adapting screenshots and promotional text for cultural relevance (currency, date formats, imagery, tone)
- Planning a multi-market rollout with effort estimates and expected download impact per region
- Iterating on existing localizations by analyzing per-country keyword rankings and conversion data
- App developers and product managers planning international expansion
- Mobile app marketers managing App Store presence across multiple regions
- ASO specialists localizing metadata for non-English markets
- Teams with budget constraints deciding between professional translation and AI-assisted localization
localization FAQ
No. This is the biggest localization mistake. Instead, run keyword-research for each market separately using local seed terms and autocomplete. Local users search differently—e.g., Germans search 'Haushaltsbuch' not 'Budget Tracker'.
Start with Tier 1 markets (US, UK, Germany, Japan, France, Korea, China, Brazil, Canada, Australia) evaluated on market size (30%), competition (25%), effort (20%), ARPU (15%), and strategic fit (10%). Most apps see highest ROI from 3–5 markets.
This skill focuses on store listing localization (metadata, keywords, screenshots). Clarify upfront whether your app UI/content is also localized, as that affects keyword strategy and screenshot design.
Budget depends on approach: professional translation with ASO expertise is higher cost but higher quality; AI-assisted with native speaker review is lower cost. The skill helps you estimate effort per market.
Monitor keyword rankings weekly in each market and track conversion rate by country. Use this data to iterate on metadata, keywords, and screenshots.
Full instructions (SKILL.md)
Source of truth, from eronred/aso-skills.
name: localization description: 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. metadata: version: 1.0.0
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
- Check for
app-marketing-context.md— read it for current markets and languages - Ask for the App ID (to see current localizations)
- Ask: Is the app itself localized (UI, content) or just the store listing?
- Ask: Which markets are they considering?
- Ask: Budget — professional translation or AI-assisted?
Market Prioritization
Tier 1 Markets (highest ROI for most apps)
| Market | Language | App Store Code | Notes |
|---|---|---|---|
| United States | English | en-US | Largest market |
| United Kingdom | English | en-GB | Easy win if US is done |
| Germany | German | de-DE | Largest EU market |
| Japan | Japanese | ja | High ARPU, competitive |
| France | French | fr-FR | Large EU market |
| South Korea | Korean | ko | High smartphone penetration |
| China | Simplified Chinese | zh-Hans | Massive but complex (needs ICP) |
| Brazil | Portuguese | pt-BR | Largest LATAM market |
| Canada | English/French | en-CA/fr-CA | Easy win |
| Australia | English | en-AU | Easy 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:
| Factor | Weight | How to assess |
|---|---|---|
| Market size | 30% | iPhone user base in country |
| Competition | 25% | How many localized competitors? |
| Effort | 20% | Translation complexity, cultural distance |
| Revenue potential | 15% | ARPU in the market |
| Strategic fit | 10% | 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:
- Run
keyword-researchfor each target market separately - Understand how locals search (different terms, different intent)
- Use local autocomplete suggestions
- 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
| Element | What to check |
|---|---|
| Screenshots | Currency symbols, date formats, number formats |
| Colors | Cultural color associations (red = luck in China, danger in West) |
| Imagery | Diverse representation, culturally appropriate |
| Tone | Formal vs informal varies by culture |
| Features | Highlight features relevant to local needs |
| Social proof | Use local press, local user counts if possible |
| Pricing | Local pricing expectations (purchasing power parity) |
Localization Workflow
Phase 1: Research (per market)
- Analyze top 10 apps in your category in the target market
- Run keyword research with local seed terms
- Identify local competitors and their positioning
- 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
- Submit localized metadata
- Monitor keyword rankings in each market (weekly)
- Track conversion rate by country
- 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
| Market | Size | Competition | Effort | Revenue | Score | Priority |
|---|
Related Skills
keyword-research— Run for each target marketmetadata-optimization— Write localized metadatascreenshot-optimization— Localize screenshot designscompetitor-analysis— Analyze local competitors
Related skills
More from eronred/aso-skills and the wider catalog.

market-movers
Track App Store chart rank changes, identify top gainers and losers, and spot breakout apps entering the top 100.

market-pulse
Comprehensive App Store market overview combining chart movements, trending keywords, featured apps, and category dynamics.

metadata-optimization
Craft high-converting App Store metadata that ranks for target keywords within platform character limits.

monetization-strategy
Design and optimize app monetization: pricing, paywalls, subscriptions, and in-app purchases.

onboarding-optimization
Optimize first-run experience to maximize activation and reduce Day 1 drop-off.

paywall-optimization
When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.