Skip to the content
KwernBeta
  • Pricing
Sign inGet startedDashboard
  1. Kwern
  2. Blog
  3. App Store Keywords: Filling the 100-Character Field

6 min read · 6 November 2026

App Store Keywords: Filling the 100-Character Field

Quick answer

How to fill the App Store keyword field without repeating your title or subtitle, with a worked example that turns a wasted 94 characters into 15 new words.

You get 100 characters of App Store keywords, and most first listings spend half of them on words Apple already has. The keyword field is the one part of your listing nobody else can see, so nobody tells you it is wasted. This article is about filling it well: what Apple reads, what to leave out, and a worked example that goes from a typical first draft to a field that adds fifteen new words to the searches your app can match.

Which fields Apple searches

On iOS, three fields you write decide which searches your app can appear for:

  • App name, up to 30 characters.
  • Subtitle, up to 30 characters.
  • Keyword field, up to 100 characters, visible only to you in App Store Connect.

The description is for the person reading the page. Write it well, because it helps them decide to download, but do not spend effort stuffing it with search terms.

Apple matches a search against the words in the name, the subtitle and the keyword field together. If your name holds "habit", your subtitle holds "daily" and your keyword field holds "reminder", you can be found for "daily habit reminder" without that phrase appearing anywhere as written. That one fact decides most of what follows: you need each word once, across the three fields, and the keyword field is where the words that did not fit in the name and subtitle go.

The rules that save characters

Apple's own guidance for the field, plus what follows from the matching above:

  1. Separate words with commas and no spaces. focus,sleep costs 11 characters. focus, sleep costs 12. Over a full field, those spaces add up to a word or two.
  2. Never repeat a word from the name or subtitle. It is already indexed. Typing it again buys nothing.
  3. Leave out your app's name and the word "app". Apple's guidance asks for this, and both are covered already.
  4. Leave out category names. Your app is already filed under its category.
  5. Prefer single words to phrases. "mood,journal" lets Apple match "mood journal", "journal mood" and each word with the rest of your listing. "mood journal" with a space costs the same and matches less.
  6. Do not add a plural next to its singular. Pick one form. Apple handles some plurals on its own, and the second form rarely earns its characters.
  7. No competitor names or trademarks. Apple's guidance forbids them, and a listing can be rejected for it.
  8. Only words that describe what the app does. A word that brings searchers who then do not download teaches Apple your page does not convert for that search.

A worked example

Here is a made-up app so the counts are easy to follow: a habit tracker called Streakly. Every character count below is exact.

Name (23 characters): Streakly: Habit Tracker

Subtitle (28 characters): Daily routine & goal planner

Between them, those two fields already give Apple: streakly, habit, tracker, daily, routine, goal, planner.

The first draft

This is the kind of keyword field most of us write the night before submitting:

habit tracker, habit, tracker app, daily habits, routine, goals, streakly, planner, habits app

That is 94 characters. Now go through it word by word against the name and subtitle:

  • habit, tracker, daily, routine, planner, streakly: already indexed from the name and subtitle.
  • app: covered, and Apple asks you to leave it out.
  • habits, goals: plurals of words already in the listing.
  • The spaces after the eight commas, plus the spaces inside the phrases: about 13 characters that hold nothing.

So of 94 characters, the field adds at most two words, and both are plural forms of words Apple has. In practice, it adds close to nothing.

The rewrite

Start from the question the field exists to answer: what else would someone type when looking for an app like this, that the name and subtitle do not already say? For a habit tracker that also logs moods, water and sleep, the list might be:

streak,reminder,todo,checklist,journal,self,care,mood,focus,productivity,water,sleep,workout,adhd

That is 97 characters and fifteen words, none of them repeated from the name or subtitle. Combined with what is already there, the listing can now match searches such as:

  • "habit tracker adhd"
  • "daily mood journal"
  • "water reminder"
  • "self care checklist"
  • "sleep tracker"
  • "workout planner"
  • "streak habit tracker"

None of those phrases is typed anywhere in the listing. Apple assembles them from words spread across three fields.

Two cautions on the rewrite. "self" and "care" are split because together they match "self care" and separately they can pair with other words; that is the usual trade, and it works because both are short. And "water", "sleep" and "workout" belong in the field only if the app actually tracks them. If it does not, someone searching "water reminder" lands on a page that does not offer it, and you pay for that in conversion.

How to choose the words

The example skips the hard part, which is deciding the fifteen words. A short routine that works for a solo maker:

Start from what you already have. In App Store Connect, the App Analytics section shows impressions and downloads by source, so you can see how much of your traffic comes from App Store search at all. If you run Apple Ads, the search terms report is the best list you will get: the exact words people typed before they tapped and installed. A word that converts in ads is a strong candidate for the keyword field.

Read your reviews for vocabulary. People describe your app in their own words. If three reviews call it a "routine app" and none call it a "habit builder", that is a signal about what they search for. We covered the replying side in how to reply to App Store reviews; the reading side feeds this field.

Look at the apps you lose to. Their names and subtitles are public. You cannot use their brand names, but the descriptive words they put in 60 characters show what they think matters.

Prefer words you can rank for. A new app with few ratings will not reach the first screen for "productivity" in a hurry. Longer combinations ("habit tracker adhd") have fewer searchers and fewer strong competitors. Your keyword field is better spent making many such combinations possible than chasing one broad word.

Changing the field, and reading what happened

The keyword field only changes with a new version, unlike the promotional text: you edit it in App Store Connect on the version you are preparing, and it goes live when that version is approved. That makes it worth batching your keyword change with a release you were going to ship anyway, and it means you get only a few tries a year at a typical release pace.

Because each try is precious, change one thing at a time where you can, and write down what the field said before. After the version goes live, give it at least two weeks before you judge it, then compare impressions and downloads from App Store search against the two weeks before the release. A rise in impressions with flat downloads means the new words bring people the page does not convince. A flat line means the words are not being searched, or you cannot rank for them yet.

Most makers never do this second half. The field gets written once, the week of the first submission, and is not opened again, though our app launch checklist has you check it a week before launch. That is the habit our ASO agent is built around: each week it reads the keyword field, the name and subtitle, the product page analytics and the reviews through the App Store Connect connection, and proposes the words it would drop and the ones it would add, with the reason for each. Nothing changes until you approve it, and the new field is a value you paste into the version you are preparing.

A checklist before you submit

  • Count the field. Under 90 characters means you have room for another word or two.
  • Search it for spaces. Delete every one after a comma.
  • Search it for every word in your name and subtitle. Delete each match.
  • Delete your app's name, "app" and your category name.
  • Delete any plural that sits next to its singular.
  • Delete any competitor name.
  • Read each remaining word and ask whether a person who typed it would want your app.
  • Write down the old field and the release date, so you can compare in two weeks.

If you want the rest of the weekly listing routine around this, how to market an iOS app sets it out: the listing, the reviews, one channel and one number to watch.

Share this article

XLinkedInFacebook
AJ

Alexandre Joly

This article was drafted by Kwern's own Writer agent and published here through Kwern's MCP server, the way any Kwern user publishes theirs.

Related articles

App Store Promotional Text: What to Put in 170 Characters
App Store promotional text changes without a review. What its 170 characters should say after a launch, a release or a press mention, with counted examples.

13 November 2026

How to Reply to App Store Reviews (With Templates)
Rules and copy-ready templates for answering 1 to 5 star App Store reviews, plus the promises a developer response should never make.

21 October 2026

App Launch Checklist: The Last 7 Days Before You Ship
A seven-day app launch checklist for solo makers: listing, store console baseline, waitlist, replies and launch day, in the order that stops a quiet launch.

15 October 2026

Read on

ASO Agent
Audits the App Store and Google Play listings every week and drafts the metadata changes and the review replies worth making.
App Store Connect
What Kwern reads from App Store Connect, the two listing fields it can change, and the ASO agent that reads it.

Someone is asking for what you built today.

On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.

Product

  • Agents
  • Skills
  • Pricing
  • Connectors
  • Compare
  • Blog
  • MCP server
  • Docs

Agents

  • ASO Agent
  • Apple Ads Agent
  • SEO Agent
  • GEO Agent
  • Google Ads Agent
  • X Post Agent
  • X Reply Agent
  • X Community Agent
  • Influencers Agent
  • LinkedIn Agent
  • Reddit Agent
  • Hacker News Agent
  • Competitors Agent
  • Writer Agent

Connectors

  • App Store Connect
  • Apple Ads
  • Google Play
  • RevenueCat
  • Stripe
  • PostHog
  • Google Search Console
  • Google Analytics 4
  • Google Ads
  • X
  • Reddit
  • LinkedIn
  • GitHub

Compare

  • Best AI CMO tools
  • Okara alternative
  • Okara alternatives
  • Okara review
  • Kwern vs Okara
  • Hoox alternative
  • Hoox alternatives
  • Hoox review
  • Kwern vs Hoox
  • RiseMore alternative
  • RiseMore alternatives
  • RiseMore review
  • Kwern vs RiseMore
  • Privacy policy
  • Terms of use and sale
  • Legal notice
  • Cookies

© 2026 Kwern