← Fixes/Metadata

Fix: App Metadata Rejection

Metadata rejections cover your app name, screenshots, description, age rating, and privacy policy link. Here is how to identify the exact issue and fix it for resubmission.

Updated Mar 2026·6 min read

Read the rejection message carefully: Metadata rejections usually include a description of exactly what was observed. The reviewer may include a screenshot. Match their description to the issues below to find the exact fix.

Misleading screenshots (Guideline 2.3.3 / Play metadata policy)

Both

You may have seen

Rejection message mentions screenshots showing features not present in the app, outdated UI, or UI that does not match the submitted build.

Fix

Replace every screenshot with recordings of the current app build. Remove any screenshot showing a feature behind a paywall without indicating that. Remove mockups and marketing renders — use actual device screenshots.

Keyword stuffing in app name or subtitle

iOS

You may have seen

App name or subtitle contains a list of keywords rather than a brand name and clear descriptor.

Fix

Your app name should be your brand name plus one clear descriptor. Your subtitle (30 chars) should describe the primary function. Remove any comma-separated keyword lists.

App description references competitor names

Both

You may have seen

Rejection cites use of third-party brand names in the description.

Fix

Remove all competitor brand names. Replace comparative language ('better than X') with feature descriptions ('does Y without Z').

Missing or broken privacy policy link

Both

You may have seen

Rejection states no privacy policy link was found, or the link provided returns an error.

Fix

Add a working privacy policy URL in App Store Connect (App Information > Privacy Policy URL) and Play Console (Store Listing > Privacy Policy). Test the URL from a browser before resubmitting.

Age rating inconsistent with content

Both

You may have seen

Reviewer found content that is inconsistent with the declared age rating: violence in a 4+ rated app, or user-generated content with no moderation in a family-rated app.

Fix

Either update the age rating to match the content, or remove the content that is inconsistent. For user-generated content, add a moderation and reporting system.

App name or icon too similar to existing app

Both

You may have seen

Rejection cites similarity to an existing app or trademark infringement.

Fix

Search the store for your proposed name and icon design before submitting. Change the name or icon to be clearly distinct. If you believe the rejection is in error, respond via the Resolution Center with evidence of your trademark.

Feature graphic missing or low quality (Google Play)

Android

You may have seen

App listing is missing the 1024x500 feature graphic, or the provided graphic is low resolution or contains prohibited content.

Fix

Create a 1024x500 px feature graphic that shows your app name and core value proposition clearly. Avoid using Play Store badges or Apple logos in the graphic.

After fixing metadata: full audit before resubmitting

Check every screenshot — not just the one flagged. If one was misleading, others may be too.

Test every link in your store listing: privacy policy, support URL, and marketing URL

Read the full app description and verify every claimed feature works in the current build

Check the content rating questionnaire matches the actual content of your app

Run the AppTester Health Check to catch any binary issues before the next review cycle

Catch metadata issues before submission

Human testers review your store listing for accuracy and flag metadata issues before a reviewer does. From $19.