App Store Rejection Checker
Paste your app metadata, get back the issues that trigger rejections, ranked by severity. Apple guidelines and Play Store policies in one pass
Vos métadonnées
Maximum 30 caractères
Maximum 30 caractères, complétez le nom
Maximum 170 caractères, modifiable sans nouvelle soumission
Maximum 100 caractères, séparés par virgules, sans espaces
Entre 200 et 4000 caractères
Obligatoire, doit être en HTTPS
Obligatoire, doit être en HTTPS
Facultatif
Résultats
26
2
0
0
L'URL de politique de confidentialité est obligatoire pour toute fiche App Store et Play Store
Correction : Publiez une politique de confidentialité et collez l'URL publique
L'URL de support est obligatoire
Correction : Utilisez une page de contact ou une URL de centre d'aide
All rules checked
| Rule | Field | Severity |
|---|---|---|
| Beta or pre-release language anywhere | all | error |
| Apple or Google brand mention in name | name | error |
| Trademark symbols in name or subtitle | name, subtitle | warn |
| Forever or lifetime pricing claim | description | warn |
| Privacy policy URL missing | privacyUrl | error |
| Privacy policy URL is not a valid URL | privacyUrl | error |
| Privacy policy not HTTPS | privacyUrl | error |
| Privacy URL on dev or preview domain | privacyUrl | error |
| Support URL missing | supportUrl | error |
| Support URL is not a valid URL | supportUrl | error |
| Support URL not HTTPS | supportUrl | error |
| Description shorter than 200 characters | description | warn |
| Description longer than 4000 characters | description | error |
| App name longer than 30 characters | name | error |
| Subtitle longer than 30 characters | subtitle | error |
| Promotional text longer than 170 characters | promoText | error |
| Keywords longer than 100 characters | keywords | error |
| Keywords contain spaces after commas | keywords | warn |
| Keyword duplicated between name and keywords | keywords | warn |
| All-caps phrasing in app name | name | warn |
| More than one emoji in app name | name | warn |
| Subtitle identical to or contained in name | subtitle | warn |
| Description starts with a weak opener | description | info |
| Marketing superlatives in description | description | info |
| Crypto or get-rich-quick language | description | warn |
| Health claims without disclaimer | description | error |
| Subscription disclosure check | description | info |
| External payment provider mentions | description | error |
Most common reasons apps get rejected
Apple publishes the top rejection reasons every quarter and the same suspects keep showing up. Guideline 2.3.10 (irrelevant information in metadata, including the word "beta"), guideline 5.1.1 (missing privacy policy or invalid URL), and guideline 2.1 (minimum functionality, often triggered by placeholder content). Together these account for nearly half of all metadata rejections.
The rest come from brand confusion (using "Apple" or "iPhone" in your name), pricing slip-ups (claiming "forever free" or "lifetime" without a corresponding subscription configuration), and trademark symbols that Apple strips automatically and rejects you for re-adding. Most of these are easy to catch before submission with a five-minute review.
Apple's metadata rules in plain English
The name maxes out at 30 characters, the subtitle at 30, the promotional text at 170, and keywords at 100. The description tops out at 4,000. Anything over those limits is auto-blocked by App Store Connect, but reviewers also reject metadata that uses every character on stuffing rather than describing the app.
Beta language, version numbers in the title, and competitor brand names all trip the metadata review. So do prices stated in the description ("$9.99/month") when they conflict with your subscription configuration. The cleanest path is to write the metadata once for humans, then run it through this checker before each submission.
Google Play policy gotchas
Google Play enforces an 80-character short description and stricter content policies on health, finance, and crypto categories. The Data Safety section is roughly equivalent to Apple's privacy label but with its own taxonomy: you cannot copy your Apple answers verbatim. Misrepresenting either is a strike against your developer account.
Play also rejects apps for declared functionality that does not match the binary. If your description mentions an AI feature that the user cannot find within 30 seconds of opening the app, expect a takedown. Keep store copy aligned with the actual onboarding flow, and test with a fresh install before every release.
How to appeal a rejection without burning your reviewer relationship
If a rejection feels wrong, reply through Resolution Center with a clear explanation, screenshots, and where applicable a video walkthrough. Avoid sarcasm, do not escalate before exhausting the first round, and never accuse the reviewer of being wrong outright. Most successful appeals show new evidence the original review did not have.
For genuinely policy-driven rejections, the App Review Board exists for second opinions, but use it sparingly. Two appeals in a row tends to slow down all your future reviews. The fastest fix for ambiguous rejections is usually to comply with the reading the reviewer applied, ship, and revisit the wording on the next release once you have a track record.
Frequently asked questions
How accurate is this checker?
The checker runs the same rules App Review enforces publicly: name and subtitle limits, beta language bans, brand mention restrictions, privacy URL requirements. It catches the common 70% of metadata rejections, not every edge case. A clean run does not guarantee approval, but a flagged run almost guarantees rework.
Does it check my actual app binary?
No. This is a metadata-only checker. It analyzes the strings you submit to App Store Connect or Google Play Console. Binary issues like missing privacy strings in Info.plist, crashes, or guideline 2.1 minimum functionality are not in scope.
Will it catch Google Play Store issues too?
Many of the rules apply to both stores: brand confusion, beta language, missing privacy policy, oversized descriptions. Google Play has stricter limits on title length (30 chars same as Apple) and short description (80 chars). Use the warnings as a starting point and always cross-check the latest policy pages.
What does the severity mean?
Errors are issues that almost always trigger rejection. Warnings are issues that often trigger rejection or kill conversion. Info notes are stylistic suggestions that do not block submission but tend to help approval and downloads.
Can I save my checks?
Yes. The form auto-saves to local storage, so refreshing the page keeps your inputs. Use the "Export report as JSON" button to share results with a teammate or store them with your release notes.
Related resources
Ship a polished listing on the first try
Generate App Store and Play Store screenshots that match the quality your metadata deserves
Try ScreenMagic free