Your app is live in 175 regions. Your listing speaks one.

The moment you hit publish, Apple puts your app in front of 175 storefronts and Google in front of even more — and every one of them shows your English listing, or a machine translation of it you never reviewed. Localizing the listing is the cheapest distribution lever in ASO, it doesn't require translating a single line of your app, and almost no indie does it.

This is not about translating your app

The confusion that stops most developers is thinking listing localization means app localization — extracting strings, wiring up locale files, retesting every screen. It doesn't. Your store listing is a separate surface: title, subtitle, description, keywords, and screenshots all live in App Store Connect and Play Console, per language, independent of what's in the binary. You can ship a fully German product page for an English-only app this afternoon, without a new build or a review of your code.

Is that bait-and-switch? No — plenty of tools are perfectly usable in English by people who search in German. The search happens in the user's language; the decision happens in the user's language. The listing is where both happen, and that's the part you control from a web form.

What the stores actually support

Apple supports 50 listing localizations as of this spring — App Store Connect added 11 new languages in March 2026 (Tamil, Telugu, Urdu, Bangla, and seven more, mostly aimed at India's market). Every storefront you don't localize falls back to your primary language, which is why the whole world currently sees your English page.

Google Play supports over 130 languages for store listings — and here's the part that should bother you: if a user browses in a language you haven't provided, Google shows them an automated machine translation of your listing, flagged as such, that no human ever reviewed. Your carefully written copy is already being translated into Vietnamese and Polish today. The only question is whether you get a say in the result. Play Console also sells human translation starting at $0.07 per word with about a week's turnaround, which prices a typical 300-word listing at roughly $21 per language.

The free 100 characters hiding in the US storefront

Here's the trick that makes localization pay even if you never expect a single install from abroad. Apple's keyword field gives you 100 characters per localization — and several storefronts index more than one localization. The best-known case: the United States storefront indexes both English (U.S.) and Spanish (Mexico). Fill in the Spanish (Mexico) localization and its keyword field gets indexed for US search too — effectively 200 characters of keywords in your biggest market, for free.

US visitors still see your English page (their device is set to English), so there's no user-facing downside. ASO teams have documented this behavior for years; Apple has never officially acknowledged it, so treat the exact storefront-to-locale table as something to verify against a current ASO tool before you build on it. Two rules: duplicated keywords don't stack — a word indexed once is indexed, full stop — so give each locale different terms. And this is an Apple-only game: Google Play indexes each language for its own locale and nothing else.

Start with markets that already found you

Don't translate into 50 languages. Open your analytics — App Store Connect's App Analytics by territory, or Play Console's statistics by country — and look for one specific pattern: markets giving you impressions but not installs. Those are people who searched, saw your listing, and bounced. Some of that is fit; a lot of it is a page they couldn't read. Two or three of those markets are your entire phase one.

Then localize in order of effort-to-impact. Keywords first: on Apple they're invisible to users, 100 characters, and the only text field Apple's search indexes besides title and subtitle — worst translation risk is nil. Title and subtitle second, because they're indexed and read. Description third — skippable on Apple where search never reads it, but worth doing on Google Play, where the description is exactly what ranks you. Screenshots last in the order but first in impact on conversion, which brings us to the step everyone skips.

Screenshots are the step everyone skips

Both stores accept a separate screenshot set per language, and almost nobody uploads one. A Japanese product page with English screenshot headlines undercuts itself in the first second: the headlines are the first — often the only — thing a visitor reads, and you've just told them the app isn't for them before they've seen a feature.

The good news is that screenshot localization is cheap in exactly the way app localization isn't. Your headlines are three to five words each; a full eight-frame set is maybe thirty words of translation. The design system, device frames, and UI captures stay identical — only the text layer changes. Watch the typography, though: German and Finnish headlines run noticeably longer than English and will overflow a tight layout, while Japanese and Korean run shorter and can look lost in the same frame. Re-check every frame at thumbnail size per language, the same way you did for English.

Ship a localized listing in one afternoon

This is one of the flows ShotCanvas was built for: design your screenshot set once, let AI translate the headlines and metadata per market, and export pixel-exact sets in App Store Connect's per-locale folder layout — or publish them straight to both stores without leaving the app. The free tier covers your first sets, no credit card.