Most app teams treat localization as "run the listing through Google Translate." That's why 9 out of 10 apps see their international rankings collapse within weeks of launch — the metadata reads like a robot wrote it, the keywords don't match what locals actually search, and the screenshots look foreign to the audience.

This 28-step checklist covers everything we've learned shipping localized listings to 40+ markets — metadata translation, per-market keyword research, screenshot adaptation, App Store Connect configuration, and the post-launch monitoring that catches a 0.4-star rating drop before it tanks your rank.

Phase 1: Pre-Launch Strategy (Steps 1–5)

1. Pick the right markets, not all 175 countries

The temptation on launch day is to ship to every country. Don't. Pick 5–10 priority markets where your category has proven demand and where your support team can handle reviews in that language. The top 10 by App Store revenue are: Simplified Chinese, Japanese, Korean, Spanish, French, German, Italian, Brazilian Portuguese, Russian, and Arabic. For Google Play, weight towards Indonesian, Vietnamese, Thai, Hindi, and Brazilian Portuguese where Android dominates.

2. Audit competitor presence per market

Before localizing, check whether your top three competitors are already translated in your target markets. If they are, you're catching up. If they aren't, that's an opportunity — you can dominate ranking before they wake up. Use store-level competitor tracking to confirm before committing.

3. Set your primary language strategically

Apple lets you set one Primary Language per app. This is the fallback when a user's locale isn't covered. If 60% of your audience is Japanese, your Primary should be Japanese, not English. Changing it after launch is risky because it can reset ratings in some markets.

4. Decide your localization budget per market

Not every market deserves equal investment. Tier-1 markets (top 5 by your revenue model) get full localization including custom screenshots and native review. Tier-2 markets get AI translation with native QA on the title and subtitle only. Tier-3 markets get AI translation alone. This stops you from blowing $20k on perfecting Estonian when the addressable market is 1.3 million people.

5. Plan your release calendar around local holidays and timezones

Don't launch in Japan during Golden Week or in China during Lunar New Year — review queues are slammed and your launch gets buried. Schedule per-region releases when local app review teams are responsive. Use timezone-aware scheduling so a global launch hits prime evening hours in each market.

Phase 2: Per-Market Keyword Research (Steps 6–9)

6. Translate keywords semantically, not literally

Direct translation breaks ASO. Spanish users don't search for "fitness tracker" — they search for "app de fitness" or "app para hacer ejercicio." Japanese users don't search using literal kanji translations — they often use katakana for foreign concepts and kanji for native ones. Use a localization tool that does per-market keyword research, not just word-for-word translation.

7. Mine local search trends

Use Google Trends, App Store Search Suggestions per country, and competitor keyword analysis per locale to find the actual search terms locals use. A keyword with 100k US monthly searches might have 5 in Germany — and a German keyword you never thought of might pull 40k.

8. Use all 100 characters in the iOS keyword field per locale

Apple gives every locale its own 100-character keyword field. Most apps copy the English field across all locales. That's wasted real estate. Each locale gets its own list, optimized for local search behavior.

9. Account for character limits in CJK and Cyrillic

A 30-character English title becomes 8 Chinese characters. Pad your CJK titles to use the full character allowance — you have far more space for keywords than you think. Conversely, German and French often run long; check that your translated subtitle doesn't truncate.

Phase 3: Metadata Translation (Steps 10–15)

10. Title: 25–30 characters with primary keyword

Translate the value proposition, then squeeze the primary local keyword in. Apple's 30-character limit is generous for English but tight for German. The title is the highest-weight ranking factor — treat it as keyword real estate, not branding.

11. Subtitle (iOS): 30 characters of secondary keywords

The subtitle is your second keyword field. Don't repeat the title. Use it for the second-most-important search phrase in that market.

12. Short Description (Google Play): 80 characters

Google indexes the short description heavily. Translate it for the local market with the primary keyword in the first 50 characters — Google Play snippets often truncate.

13. Long Description: keyword density that ranks Google Play

Google Play indexes the full long description for keywords. iOS does not. Translate the long description with awareness of this asymmetry: keyword-pack the Google version, write the Apple version for conversion.

14. Promotional Text (iOS): editable without app review

Use this for time-sensitive copy — sales, holiday messaging, new features. Translate per-market and update without resubmitting.

15. Release Notes: translate every release

Untranslated release notes signal to users that the app isn't maintained for their market. Use AI to translate every release in batch. Batch update tools let you push a release-notes update to 40 locales in one action.

Phase 4: Visual Localization (Steps 16–19)

16. Localize screenshot captions

Caption text on screenshots is now indexed by both Apple and Google as a ranking signal. Translate captions per market with native keywords. Tools like the AppDrift screenshot generator let you batch-export localized screenshots for every device size.

17. Adapt screenshot UI for high-value markets

For Tier-1 markets, show the actual localized app UI in screenshots, not the English UI. A Japanese user seeing English UI in screenshots assumes the app isn't translated.

18. Cultural imagery review

Hand gestures, color associations, and stock models that work in the US can offend or confuse in other markets. Red is celebratory in China but a warning color in the US. Thumbs-up is offensive in some Middle Eastern markets. Run screenshots past a cultural reviewer for any high-stakes market.

19. App Preview videos per locale

Apple supports up to three App Preview videos per locale. Subtitle them at minimum. For Tier-1 markets, dub or re-record with a local voice. Conversion lift on localized preview videos is 25–40%.

Phase 5: App Store Connect & Google Play Console Setup (Steps 20–23)

20. Enable each locale under Localizations

Adding a translation isn't enough — you must enable that locale in App Store Connect under Localizations. Forgetting this is the #1 silent localization failure.

21. Confirm Pricing & Availability per country

Apple defaults the app to a tier price; verify each country charges in local currency at the right tier. For subscription apps, set introductory offers per region and check tax collection settings.

22. Localize in-app purchase display names and descriptions

IAP display names appear on the App Store listing under In-App Purchases. Untranslated IAP names look like a half-finished port. Translate every SKU.

23. Configure phased release per market

For Google Play, use staged rollout to release at 5→20→50→100% per region. This catches localization-specific bugs before they hit your full audience. Use automated publishing tools to manage staged rollouts across 150+ countries from one dashboard.

Phase 6: Post-Launch Monitoring (Steps 24–28)

24. Track keyword rank per country, not globally

Aggregate keyword rank reports are useless. A keyword that ranks #2 in the US can rank #80 in Brazil. Track rank per locale per keyword, weekly minimum.

25. Monitor rating trends per market

Star rating drops first in the market where your localization is weakest. A drop from 4.5 to 4.2 in Germany while everyone else stays at 4.7 means your German listing or German support is the problem. Set up store monitoring with per-market rating alerts — a 0.2-star drop should page someone, not be discovered weeks later.

26. Watch for review spikes per locale

A sudden spike in negative reviews in one market often means a market-specific bug, an outage of a third-party service in that region, or a translation error users find offensive. Per-locale review spike alerts let you respond same-day.

27. A/B test screenshots per market

Google Play's Store Listing Experiments let you test screenshots, descriptions, and icons per locale. Apple's Custom Product Pages do the same. Run at least one experiment per Tier-1 market in the first 90 days.

28. Refresh metadata quarterly

Search trends shift. Competitors update. Apple and Google adjust their algorithms. A listing optimized at launch loses 30–40% of its rank within six months if the team never revisits it. Schedule a quarterly localization audit covering keywords, ratings, screenshot conversion, and competitor metadata changes.

The 28-Step Checklist (Printable Summary)

Pre-Launch Strategy

Pick 5–10 priority markets, not all 175 countries
Audit competitor presence per market
Set your primary language strategically
Tier your localization budget per market
Plan release calendar around local holidays and timezones

Per-Market Keyword Research

Translate keywords semantically, not literally
Mine local search trends per country
Use all 100 characters in the iOS keyword field per locale
Account for character limits in CJK and Cyrillic

Metadata Translation

Title: 25–30 characters with primary keyword per locale
Subtitle (iOS): 30 characters of secondary keywords
Short Description (Google Play): 80 characters with primary keyword in first 50
Long Description: keyword density tuned for Google Play
Promotional Text (iOS): time-sensitive copy per market
Release Notes: translate every release

Visual Localization

Localize screenshot captions (now a ranking factor)
Adapt screenshot UI for Tier-1 markets
Run cultural imagery review
App Preview videos per locale (subtitled or dubbed)

App Store Connect & Google Play Console Setup

Enable each locale under Localizations
Confirm Pricing & Availability per country in local currency
Localize in-app purchase display names and descriptions
Configure phased release per market

Post-Launch Monitoring

Track keyword rank per country, not globally
Monitor rating trends per market with alerts
Watch for review spikes per locale
A/B test screenshots per market
Refresh metadata quarterly

Tooling: What to Automate

Manual execution of all 28 steps for 10 markets takes 60–80 hours per release cycle. The leverage is automating the repetitive parts and reserving human time for strategic decisions.

Translation + cultural adaptation: AI-powered metadata translation with per-market keyword research replaces 4–6 hours per language with 5 minutes.
Screenshot generation: A drag-and-drop screenshot generator exports localized screenshots for every required device size in batch.
Multi-market publishing: One-click deployment to App Store and Google Play across 150+ countries, with phased rollout and timezone-aware scheduling.
Post-launch monitoring: Store monitoring with per-market alerts on rating drops, rank regressions, metadata changes, and review spikes — delivered to email, Slack, or Discord within minutes.

For teams managing more than three apps or more than five markets, automation isn't optional. The hours saved compound across every release.

Common Localization Mistakes That Break ASO

Reusing English keywords across all locales. The keyword field exists per locale for a reason — English keywords don't rank in non-English markets.
Skipping the subtitle for non-English locales. The subtitle is a 30-character keyword field. Empty = wasted rank potential.
Ignoring promotional text per locale. Editable without app review — cheap leverage.
Not localizing in-app purchase names. Listed publicly on the App Store; untranslated names signal an unfinished port.
Using stock English screenshots in CJK markets. Conversion drops 20–40% versus localized screenshots.
Setting all locales to the same release notes. Untranslated release notes signal abandonment.
Forgetting to enable the locale in App Store Connect. Translations are loaded but the locale shows English — the silent killer.

Final Notes

Localization is not a one-time pre-launch task. The apps that win internationally treat each locale as a living listing with its own keyword strategy, its own conversion testing, and its own monitoring. The tools to do this exist; the discipline is the bottleneck.

If you're shipping a global release in the next 30 days, work through this checklist sequentially. Don't skip the per-market keyword research step — it's the single highest-leverage hour you'll spend. And don't leave post-launch monitoring as a "we'll set it up later" — the rank drop happens in week two and is harder to reverse the longer you wait.

Pre-Launch Localization

App Store Localization Checklist: 28 Steps for a Global Release (2026)