ASO Audit
by appeeky / aso-skills
Use it when you want a full ASO health audit, review your App Store listing quality, or diagnose why your app isn't ranking.
Localize your App Store listing for international markets.
Listed ·Updated
Install data from skills.sh
Prioritizes the countries an app should localize its store listing for, then plans each market. Candidate markets are weighed on size, competition, effort, revenue potential and strategic fit, starting from ten tier-one markets such as Germany, Japan and Brazil. It asks whether the app itself is localized or only the listing, which markets you're considering, and whether translation will be professional or AI-assisted. Keywords get fresh research in every market, never a straight translation: budget tracker becomes Haushaltsbuch in German. Each market plan carries ten local keywords with volume and difficulty, a localized title, subtitle and keyword field within character limits, and cultural notes. It recommends native speakers with ASO knowledge over translators alone.
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.
app-marketing-context.md — read it for current markets and languages| 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 |
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)
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? |
For each target market:
The biggest localization mistake: Translating English keywords directly.
Instead:
keyword-research for each target market separatelyExample:
| 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) |
For metadata (title, subtitle, keywords):
For description:
For screenshots:
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 | Size | Competition | Effort | Revenue | Score | Priority |
|---|
keyword-research — Run for each target marketmetadata-optimization — Write localized metadatascreenshot-optimization — Localize screenshot designscompetitor-analysis — Analyze local competitorsNot using the CLI? Copy the SKILL.md and paste it straight into ChatGPT, Claude, or any agent.