App Store rejection risk checker
Paste your name, subtitle, keywords and description before you submit. See the words and lengths that tend to draw a rejection on the App Store or Google Play, and why.
Input
Separate names with commas. Each one is looked for in every field.
Findings
Paste your listing on the left. Findings appear here as you type.
What the checker looks at
- Length is counted the way each console counts it: characters, and bytes for the App Store keyword field.
- The same word weighs differently by field: a price word in the description is a note, in the name it is a high risk.
- Brand and platform terms cover the best-known apps and stores in ten languages. Add your competitors' names to check them too.
- A finding is a risk, not a verdict. Review also looks at the build, screenshots and privacy answers.
The calculation runs in your browser; everything you type stays on your device.
FAQ
Common questions
What are the most common App Store metadata rejection reasons?
Names of other apps or companies, price or ranking claims in the name or keywords, mentions of Android or other stores, placeholder text, and descriptions of features the build doesn't have. The checker looks for each of these.
Is the App Store keyword limit 100 characters or 100 bytes?
100 bytes. Plain Latin letters take 1 byte, letters like é or ü take 2, and Japanese, Chinese or Korean characters take 3, so a Japanese keyword field holds about 33 characters.
Can I put free in my app name?
Apple asks for no pricing information in the name, subtitle or keywords, and Google Play doesn't allow price or promotion words in the title. Say it in the description, and keep it accurate when the app has in-app purchases.
Does a clean result mean my app will be approved?
No. The checker reads only the text you paste. Review also looks at the build, the screenshots, the privacy answers and how the app behaves.
Start measuring today.
Free plan: 1 app, 25 keywords in each of 2 storefronts, 30 days of history, no card, no end date.