Use case
Entering the German App Store: local keywords and compound words
For the German App Store, research the phrases Germans type, then check each phrase in the Germany storefront. LocalASO's documented example is "sprachen lernen" for a language-learning app, which is what German users type instead of a literal translation of "language learning".
Updated
Who this is for
You have an English-first app and want German users, for example because Germany is large for your category or because you already see some German installs. You want rank evidence before you change a listing.
The problems you probably have
- Literal translation. A German word that is correct may not be the term users type.
- Compound words. German often joins words into one. Apple does not document how it handles word combinations or compounds in search, so test rather than assume: change one field, ship, and check the ranks.
- Keyword field space. It accepts up to 100 bytes, comma-separated without spaces, and German words are long.
- One German market, three storefronts. Germany, Austria and Switzerland have separate storefronts; LocalASO lists Switzerland with German as its language. Check each one you care about.
A workflow for Germany
- Add your app and German rivals as Competitor.
- In localization, choose Germany (and Austria or Switzerland if relevant). Each keyword is adapted to the local phrase, and LocalASO checks it in that store.
- Read the board. Look for Push keywords (rank 4 to 20) first; for Hard keywords, look for a longer, more specific German term.
- In Optimize, generate the German name, subtitle and keyword field. The name is localized, so the German listing can carry a German-language name.
- Review the text yourself or with a native speaker, then paste into App Store Connect or upload as a draft.
- Compare German and English fields with the cannibalization checker if both languages are active on the same storefront.
Users can search with localized keywords in all countries where the localization is shown. Details per storefront are on the Germany keywords page, and the ranking by country guide explains why the same keyword ranks differently across countries.
What LocalASO does not do for Germany
- No proofreading. A native speaker should read what the AI proposes.
- No legal text. Imprint, privacy policy and consumer-law text are separate work.
- No true search counts. Volume and difficulty are estimates from rating counts.
- No German-language support or reviews management.
A small test plan for German compounds
Because Apple does not document how it matches German compounds, run a cheap experiment. Pick one concept, such as a task your app solves, and write it two ways in the German keyword field: as a compound and as separate words. Ship one variant per release, wait for the metadata to propagate (Apple says up to 24 hours), then read the board for both phrases. Keep what ranks and drop what does not. Do not change the English listing in the same release, so you know which change caused the move.
Next step
Pick Germany as the first market, then widen to the other German-speaking storefronts once ranks move. Download or see pricing. Wider reading: expand to Europe and Latin America.
Sources
- Apple: developer.apple.com/help/app-store-connect/reference/platform-version-information#keywords (checked November 1, 2026)
- Apple: developer.apple.com/app-store/search (checked November 1, 2026)
- Apple: developer.apple.com/help/app-store-connect/manage-app-information/localize-app-information (checked November 1, 2026)
- Apple: developer.apple.com/help/app-store-connect/reference/app-information/app-information#name (checked November 1, 2026)
Do this for every country, in minutes