Metadata Linter
Metadata Linter checks App Store or Google Play text before you publish it: it flags every field's limit, words repeated across fields or doubled as singular and plural, other brands' names and claims like "best, #1, free", instantly.
Method
- 01
Limits from the documentation
App Store: name 30, subtitle 30, keyword field 100, promotional text 170 characters. Google Play: title 30, short description 80, full description 4,000 characters.
- 02
Word map
Every word in the searchable fields becomes a chip: unique, repeated, singular/plural twin, risky or probably already indexed. Apple indexes the name, subtitle and keyword field together, and its documentation says to avoid duplicate words, plurals of words already included in singular form, category names and the word "app".
- 03
Policy risks
Other apps' and brands' names, price and ranking claims ("best", "#1", "free"), emoji and ALL CAPS in the title, other platforms' names, placeholder text. App Review Guideline 2.3.7 and Google Play's metadata policy limit these.
- 04
Runs in your browser
The check happens entirely on your device; your text is not sent to a server and no store is called.
Questions
Should I use spaces in the keyword field?
Apple says to separate keywords with commas and no spaces ("Property,House,Real Estate"). Every space after a comma costs one of the 100 characters; spaces inside multi-word phrases are fine.
Why are the developer name and category "probably indexed"?
Apple's documentation says not to put category names in the keyword field. That the developer name also matches in search is a common observation, but Apple does not document it, so that flag is labelled "not officially documented".
Is the singular/plural check right in every language?
It uses simple suffix rules for Turkish (-lar/-ler), English, Spanish, Portuguese, French and German. A rule can be wrong; confirm a flagged pair yourself.
Does a clean result guarantee approval?
No. Review also looks at screenshots, the app itself and privacy answers. The linter only catches common risks in the text.