AppTester.coAppTester.co
← Blog/For Developers

How to Analyze App Metadata for Store Approval

Metadata rejections are preventable. Here is a field-by-field audit of every metadata element that affects your App Store and Google Play submission: with the exact rejection risks for each.

Mar 20, 2026·7 min read·AppTester.co Team

Metadata is reviewed before the binary in both stores' automated pipeline. Errors in your title, screenshots, or privacy labels can reject a submission before a human ever looks at your app. Here is what to audit before every submission.

App name / title

30 characters (App Store) / 50 characters (Google Play)Medium

Should clearly describe the primary function of the app

Don't keyword-stuff: 'Tasks & Todos & Reminders & Notes' will be rejected

Google Play allows more characters but keep it readable on small screens

Rejection risk: keyword stuffing and misleading names trigger rejection

Subtitle (App Store only)

30 charactersLow

Should complement the name, not repeat it

Use it to describe your primary value proposition

Cannot include competitor names or generic terms like 'Best' or '#1'

Rejection risk: but wasted opportunity if not used well

Short description (Google Play)

80 charactersLow

Appears in search results: this is your hook

Focus on the primary user benefit, not a feature list

Make it compelling: what problem does this app solve?

Rejection risk: but affects conversion from search result to install

Full description

4,000 characters (both stores)High

First 3 lines appear above 'Read More': lead with value, not backstory

Describe features present in the current submitted build only

Don't mention pricing, other platforms, or external payment methods

Rejection risk: referencing unavailable features or external payments triggers rejection

Screenshots

Up to 10 per device type (App Store) / 8 per device type (Google Play)High

Must match the actual submitted build's UI: not mockups or design files

Include captions/overlays that explain each screen's value

Show real use cases, not empty or placeholder states

Rejection risk: screenshots that don't match the build are a common rejection reason

Keywords (App Store only)

100 characters total (comma-separated)Medium

Don't repeat words already in the title or subtitle: they're indexed automatically

Don't include competitor names

Use all 100 characters: prioritise high-intent, lower-competition terms

Rejection risk: competitor names and irrelevant terms trigger metadata rejection

Age rating / content rating

Set via questionnaire in both storesHigh

Answer the content questionnaire honestly: stores cross-check the actual app

If your app includes any user-generated content, age ratings change significantly

In-app purchases affect age ratings on some content categories

Rejection risk: mismatched age ratings (too low for content) trigger rejection and can cause account issues

Privacy labels / Data Safety

Detailed questionnaire: both storesCritical

Audit every SDK in your build: SDKs collect data even if your own code doesn't

Data Safety must reflect what the app actually does, not what you intended

Privacy labels on App Store are displayed on the product page to all users: accuracy affects trust

Rejection risk: inaccurate privacy labels trigger rejection and potential removal

Catch metadata issues before submission

Our App Health Check scans your binary and flags metadata-related issues. Free, 30 seconds.

Free Health Check15 Common Mistakes