App Store keywords field checker
Paste your app name, subtitle and keywords field. The checker counts the limits, points out wasted bytes and builds a cleaned version you can copy back into App Store Connect.
Comma-separated, exactly as you would type it in App Store Connect.
What we found
- Paste your keywords field above, or try the example, to see what can be trimmed.
Cleaned keywords
Our check, not Apple's validator. The rules come from Apple's published limits and common ASO practice; App Store Connect has the final say. Apple states the keywords limit as 100 bytes, so the checker counts UTF-8 bytes: plain English letters take one byte each, accented and non-Latin letters take two to four.
Your text stays in this tab. The checks run in your browser and what you type is not sent anywhere. The page itself loads fonts from Google Fonts and our analytics script; Google Analytics starts only if you accept it, and it never receives the contents of these fields. How site analytics works.
What the checker looks at
- Length: app name and subtitle against 30 characters each, the keywords field against 100 bytes.
- Spaces after or before commas, at the start or end of the field, and doubled inside a term.
- Empty items: double commas and commas at the start or end of the field.
- Words repeated inside the field.
- Words that already appear in your app name or subtitle, matched regardless of case.
- Possible singular and plural pairs, which Apple counts as duplicates, found with a simple English s/es/ies rule. These are only flagged; the cleaned version keeps both forms.
- Terms of two characters or fewer, flagged for a second look.
The cleaned version applies only the mechanical fixes: it removes extra spaces, empty items, repeated words and words already in your name or subtitle, and keeps the first occurrence of every other word in its original order. The number next to each finding shows how many bytes that fix frees.
What it can't tell you
It can't tell you which keywords are worth the space. That depends on search volume, difficulty and how relevant a term is to your app, and no length check can see any of those. For the mechanics behind these rules, read how the iOS keywords field works; for choosing between candidate terms, see keyword difficulty explained.
Seeing where those keywords actually rank over time is a different job. ASOHawk does that; it is our in-house tool, built by the person who publishes this site.
Frequently asked questions
Does Apple count the keywords field in characters or bytes?+
Apple's App Store Connect help states the limit as 100 bytes. For plain English letters, digits, commas and spaces one character is one byte, so the two counts match. Accented letters and non-Latin scripts take two to four bytes per character in UTF-8, so the checker counts bytes and shows both numbers when they differ.
Is this Apple's official validator?+
No. It's our own check, built from Apple's published limits and common ASO practice. App Store Connect has the final word on what it accepts, and Apple doesn't publish how search weighs each field.
Do you see or store the keywords I paste?+
No. The checks run in your browser and the text you type is not sent anywhere. The page loads fonts from Google Fonts and our analytics script; Google Analytics loads only if you accept it, and it records page views and link clicks, not what you type into the fields.
Why does it remove words that are already in my app name or subtitle?+
Apple's App Store search guidance asks you not to repeat words that are already in your app name, subtitle or category: those words are already searchable from your metadata, so repeating them spends bytes on terms you already cover. The checker sees only the name and subtitle you paste, so compare against your category name by eye. If you want a specific word back, add it after copying.
Should I drop one word of a singular and plural pair?+
Usually, yes. Apple's App Store search guidance counts plurals of words you already use, such as climb and climbs, as duplicates. The checker still only flags possible pairs and never removes them, because its rule is a simple English s/es/ies match: it misses irregular plurals such as child and children, and it can pair words that only look related.