Validation
App Store Rejection Checker
Validate metadata against Apple and Google Play guidelines before submission.
Comma-separated, no spaces around commas.
- Title is required.Add a title of 30 characters or fewer.App Store 2.3
- Description is empty.Add a description. An empty listing looks incomplete to reviewers.App Store · store listing
- No privacy policy URL provided.Both stores require a reachable privacy policy URL for every app.App Store 5.1.1
How it works
Catch the rejection before the reviewer does
The same metadata rules reviewers apply, run in your browser before you submit.
- 01
Pick your store
iOS or Android. The checks and character limits adapt to the store you're submitting to.
- 02
Fill in your listing
Title, subtitle or short description, keywords, description, privacy policy URL, and age rating. Everything runs in your browser, nothing is uploaded.
- 03
Read the score and verdict
A 0 to 100 score plus a split of blockers (the store refuses it), warnings (a reviewer likely flags it), and tips (wasted budget).
- 04
Apply the fix and recheck
Each finding names the guideline behind it and the exact change to make. Findings update on every keystroke until the listing is clean.
Guideline coverage
The rejection reasons we screen for
Metadata triggers behind the most common first-submission holds, mapped to the guideline that drives them.
App completeness
2.1Placeholder copy, draft text, or 'coming soon' in a live listing signals an unfinished app. We flag common placeholder phrases in your title and description.
Accurate metadata
2.3Metadata that oversells or misrepresents the app is one of the most cited rejection reasons. Keep the title, subtitle, and description true to what ships.
Promotional terms
2.3.7Apple bans pricing and promotional phrasing in names and metadata. 'Free', 'best', 'sale', and '#1' in a title are frequent first-submission rejections.
Minimum functionality
4.2Thin listings hint at thin apps. A description of a couple of lines gets flagged, so explain what the app does, who it's for, and its core features.
Privacy policy
5.1.1Both stores require a reachable privacy policy URL for every app. A missing or broken link is an automatic hold.
Trademarks and IP
5.2.1Using another brand's name, like 'iPhone' or 'Instagram', in your title risks a trademark rejection unless you have written permission.
FAQ
Store rejections, answered
The metadata rules that cause the most avoidable rejections: the 30-character title limit on both stores, Apple's ban on promotional and pricing terms (guideline 2.3.7), trademark risks like 'iPhone' or 'Google' in a title (5.2.1 and 5.2.5), placeholder content (2.1), the 100-character iOS keyword format, description length and thin content (4.2), the required privacy policy URL (5.1.1), and age rating mismatches. Google Play equivalents are applied when you switch stores.
Yes. iOS shows the subtitle and keyword fields and cites App Store guideline numbers. Android swaps in the 80-character short description, drops the keyword field, and references Google Play's store listing and Data safety policies.
Apple guideline 5.1.1 and Google Play's Data safety policy both require a reachable privacy policy URL for every app on the store, regardless of what data it collects. A missing or non-https link is a common, easily avoided hold.
No. This covers metadata triggers only. Reviewers also evaluate your binary, content moderation, privacy declarations, and in-app purchases. A clean score just means your listing text won't be the reason.
No. All checks run in your browser. Nothing you type is stored or transmitted.
Related tools