Review miningMetadata checker
Audit your title, subtitle and the 100-character keyword field, and see how many characters are being wasted.
The App Store's text inventory is fixed: 30 characters of title, 30 of subtitle, 100 in the keyword field. Nobody ever sees the keyword field - it only feeds the search index, which makes every character in it either a word indexed or a character wasted.
This checker reads the three fields together, the way Apple does, and counts the characters you can win back. Nothing you type leaves the tab.
0/30
0/30
0/100
As it stands in App Store Connect, comma-separated.
Whose storefront's metadata are you auditing?
How to use it
- 1
Paste all three fields
Exactly as they stand in App Store Connect: title, subtitle, and the comma-separated keyword field.
- 2
Pick the storefront
Case folding differs by country. Turkish and Azerbaijani lowercase “I” to “ı”, and the wrong storefront breaks stems like “AI”.
- 3
Apply the findings
Each finding says how many characters it returns. The cleaned field can be copied straight out.
The three most common ways to waste the field
A typical keyword field loses 15-25 characters to one of three mistakes. That is two or three more keywords - a measurable gain when the field is full.
- A space after a comma: Apple splits on the comma, and the space indexes nothing. Across ten terms that is nine characters.
- Repeating a word already in the title: Apple indexes all three fields and combines terms across them, so the repeat spends the second field's characters for nothing.
- Singular and plural: the store already matches both forms of a stem. Writing both throws away the second one's characters.
Why an empty subtitle is expensive
The subtitle is the second most heavily indexed field and the best place to add a keyword without disturbing the title. Leaving it empty throws away 30 characters of indexing, and so does filling it with a line like “Make your life easier” that indexes nothing.
A good subtitle does two jobs at once: it carries the words you are targeting and it says what the app does at a glance.
Auditing is not a one-off
Metadata is version-scoped: changing it means shipping a new version. That is why each version should change one variable and the result should be measured - otherwise you never learn which edit worked.
And note what cleaning the field does and does not do: it makes room, it does not choose the words. What goes in the room is decided by the keywords you already rank for.
Frequently asked
- Is what I type stored anywhere?
- No. The audit runs in your browser; nothing you type is sent to a server.
- Why is there no warning about capitalisation?
- The App Store's search index is case-insensitive, so letter case is not wasted inventory. Writing the same word in two different spellings is waste, and that we do catch.
- Does this work for Google Play?
- Partly. Play has no separate keyword field; words are indexed from the description. The title and subtitle findings apply, the keyword-field section does not.
- Can I use the cleaned field as-is?
- Yes, but read it first. The suggestion only drops repeats and spaces; it makes no claim about which words belong there.
Other free tools
- Keyword difficulty calculatorWork out how hard a search term's first page is to take, with the formula the product itself runs.
- Competitor keyword gapPull out the words your rivals' metadata carries and yours does not.
- Review keyword extractorPaste user reviews and get the searchable phrases back, with the narration filtered out.
- ASO ROI calculatorPut a monthly and yearly figure on a ranking improvement, in your own numbers.
Something does this for every keyword, every day.
By hand, one keyword takes a few minutes. rankcusp measures every phrase in your pool every day, separates the ones that fall into the 11-30 band, and proposes a single metadata move for each.