Localise your store listing

Where the downloads actually are

Both stores let you publish a different listing per territory, and both index that localised text for search in that market. An English-only listing is invisible to a shopper searching in Japanese, and unconvincing to one who finds it — which is why localisation is usually the highest-return work left on a finished listing.

Translate the listing, not the fields

The title, subtitle, description and keyword field have to work together: the subtitle completes the title, and the keywords have to match the words the description uses. Translating them one at a time breaks those relationships. Here the whole listing is translated in one pass, so it stays internally consistent — and every field remains editable afterwards.

The copy itself comes from the metadata generator, or from whatever you have already written.

A screenshot set per locale

Screenshot captions are the first thing a shopper reads, and they are the part most teams skip because redrawing a set per language is a day of work. A locale variant here reuses the design — same layout, same device frames, same backgrounds — and replaces only the caption text, so adding a language costs a translation, not a redesign.

A practical order to do it in

• Finish the English listing and screenshots first — every translation inherits its mistakes.
• Translate the copy, then read the title and subtitle in each language; they are the two fields worth a human eye.
• Generate the localised screenshot sets and check for text that overflows — German and Finnish are the usual offenders.
• Upload per territory in App Store Connect and the Play Console.