appeeky spec
← Learn

ASO · 8 min read

Pick the searches to win

Choosing targets per country, reading coverage, using the second language a storefront reads, and where the words should go.

Everything the spec measures is about targets: which searches you cover, where you rank for them, and whether a change moved them. Pick them well and every other number means something.

What a target is

A target is a search you want the app to be found for, in one storefront. Storefronts are countries (us, de, tr); a word that matters in the US may mean nothing in Germany.

appeeky.spec.yaml
targets:
us: [sleep sounds, white noise, rain sounds, brown noise, fan sounds]
de: [einschlafgeräusche, weißes rauschen, regengeräusche]

Choosing them

  • Five to ten per country. Enough to see movement, few enough that each one matters.
  • Words people type. “white noise”, not “premium ambient audio”. Store search suggestions and the words in competitors' names and subtitles are good sources.
  • A mix of reach. One or two popular searches you can grow into, and several smaller ones you can win now.
  • Your own brand once. It is the search you should always win; it tells you if something broke.

Where the words go

  • name 30

    Sleep Sounds: White Noise

  • subtitle 30

    Rain, Fan & Baby Sleep Aid

  • keywords 100

    brown noise,ocean,lullaby,nap

App Store search weight, roughly: name over subtitle over keyword field. The description is not searched on the App Store; on Google Play the title, short and full description all are.

On the App Store, the name, subtitle and keyword field are indexed together, once. That gives three rules:

  • Never repeat a word across them. “sleep” in the name and the subtitle is wasted space; check warns about it.
  • Words combine into phrases. “rain” in the subtitle and “sounds” in the name cover “rain sounds”.
  • Commas, no spaces in the keyword field, and no plurals of words already there.

Reading coverage

zsh
$ npx @appeeky/spec coverage --country us
✓ white noise #8 name
✓ rain sounds #21 subtitle
~ brown noise #34 keywords · es-MX
✗ fan sounds — missing “fan”
4/5 covered · es-MX has 37 characters free

Each target is covered (all its words are in a searched field), partial, or missing, with the field that covers it. With an Appeeky key the list is weighted by popularity and difficulty, so the gaps worth fixing come first.

The second language

Some App Store storefronts read more than one listing language. The US also indexes Spanish (Mexico), so the es-MX keyword field adds 100 characters for US searches. coverage counts it and says how much room is left.

appeeky/store/app-store/es-MX.yaml
# appeeky/store/app-store/es-MX.yaml
keywords: fan,ocean,lullaby,nap,sonidos para dormir

Let suggest help

suggest proposes words for a keyword field: first the target words that are still missing, then, with an Appeeky key, searches with traffic that your listing does not cover yet. --apply adds the ones you pick.

zsh
$ npx @appeeky/spec suggest --locale es-MX
+ fan pop 33 helps: fan sounds
+ ocean pop 28 helps: ocean sounds
· thunderstorm pop 24 (does not fit)
Add with: appeeky-spec suggest --locale es-MX --apply <words...>

Then push, and let verify tell you on day 7 whether the new words found their searches.