Reach the storefronts your listing is missing.

The hidden extra keyword fields

Each App Store storefront shows one language and also searches others. Apple publishes this: the US store, for example, also searches Spanish (Mexico), Chinese and several more. An empty locale that a storefront searches is a keyword field you are not using there, at no cost and with no translation of your app required.

Apptiller knows Apple's table, checks it against your live locales, and shows which ones are empty in the storefronts you care about.

Which language should come next

Localization is often decided by guesswork, or by whichever language a friend can review. Apptiller uses your own App Analytics: where people already see the app, how many of them, and which of those storefronts show them a fallback listing. That turns "should we do German?" into a comparison you can look at. It also keeps the list short, because translating a listing nobody sees earns nothing.

Written natively, not translated word for word

A translated keyword is often not what people type. Pro drafts a locale's name, subtitle, keywords and description natively, from the searches that fit your app in that storefront. You review the draft, and it is written to App Store Connect when you approve. If you have a native speaker, this is a good thing to show them.

Custom product pages

Custom product pages let different people land on a page made for them. Since 2025 a custom page can also take keywords from your keyword field and appear in organic search. Apptiller groups your tracked terms by what the searcher wants and drafts one page per group. Its Traffic tab then shows each page's views and downloads next to the default page, once Apple has numbers for it.

In-app events and featuring

In-app events show in search, on your product page and in Apple's editorial picks. Apple also features apps it hears about early. Both are free and most small teams never use them. Apptiller proposes events from your release calendar, the season and what reviews ask for. It checks your readiness for featuring against what Apple names, and drafts the pitch.

Your approval creates each one as a draft in App Store Connect. You add the event image and submit it, and a nomination needs a second approval before it goes to Apple.

What stays yours

Model-written copy can be wrong about tone and local habits, so nothing is published without you, and a human check is still worth it for your biggest markets. Apple also reviews every new version of your text and events. Featuring is Apple's decision alone: Apptiller gets your nomination ready and sent, and no tool can promise more than that.

A worked example

An English-only app gets a steady trickle of impressions from Germany. German visitors see an English listing, and conversion there is well below your US number. Apptiller shows that gap and proposes a German listing built on what Germans search, not on a translation of your subtitle. After it goes live, the storefront row shows whether page views and downloads changed.

In the US, the same check finds that the Spanish (Mexico) locale is empty. Filling only its keyword field gives you another 100 characters of terms in the US store, which is usually the fastest localization win there is. Use it for extra terms that fit your app rather than repeating the ones you already have.

Where to start

Begin with the free wins: the empty locales your biggest storefront already searches. Next, take the storefronts where you already get impressions and show a fallback language. Only then look at new markets. Screenshots matter as much as text, so if a market starts working, localize those next. Apptiller reads your text fields and keywords; your screenshots stay in your hands.

Getting started

Connect App Analytics and your App Store Connect key, then open the Listing tab. It shows each locale with characters used and tracked terms covered. On Pro, each storefront worth doing has a draft button. The 14-day Pro trial covers this if you want to try it on one language first.

Questions