AppReviewFix
Guideline library
Apple App Store — App Quality

2.3.8 — Metadata appropriate for all audiences

Official source: App Store Review GuidelinesTopic overview: The review process, app quality and enforcement
What this guideline means

Even if the app itself is rated for mature audiences, everything visible on the public App Store listing — name, icon, screenshots, description — has to be suitable for all ages, since anyone browsing the Store can see it.

Why apps actually get flagged

Common with mature-content or dating apps that use suggestive screenshots or explicit language in the public description, even when the in-app content itself is properly age-gated.

A real example

"Your app's metadata includes content that is not appropriate for all audiences, per guideline 2.3.8, regardless of your app's content or age rating."

The short version, in more detail

Guideline 2.3.8 says the public listing must be appropriate for everyone, even if the app itself is aimed at adults. Anyone browsing the Store can see the name, icon, screenshots and description, so they must suit a general audience. Mature-content and dating apps often run into this when marketing images are suggestive.

Why this rule exists

The App Store is a public storefront seen by people of every age, including children who may be browsing with a parent's device. Apple separates what an app contains from how it is advertised: the in-app age gate protects users once they are inside, but the listing is visible before any gate applies. The rule makes sure the shop window is suitable for everyone, whatever is sold inside.

What this guideline covers

  • App name, icon, screenshots and description.
  • Previews and other visible store assets.
  • The difference between in-app content and listing content.
  • The idea that the storefront is public to all ages.

What usually triggers this rejection

  • Suggestive screenshots on a dating or social app.
  • Explicit language in the description.
  • An icon or name that is not suitable for general viewing.
  • Previews that include mature scenes.
  • Promotional text that targets adult themes openly.

How reviewers evaluate it

  • Reviewers view the listing as any visitor would.
  • They evaluate the listing separately from the app's age gate.
  • They check that the assets match a general audience standard.
  • They consider localised listings as well.

Common misunderstandings

  • An age rating does not change what can appear in public metadata.
  • Mature apps can be listed, but their storefront presence must remain suitable.
  • Even a single suggestive screenshot can be enough.

Common questions

Can an adult app have a normal listing?

Yes. It needs a listing that is suitable for all viewers.

Does this apply to every language?

Yes, localised metadata is included.

Are previews covered?

Yes, previews are part of the public listing.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
Content Ratings — Content rating accuracyMetadata — Store listing metadataMisrepresentation — Store listing and ratings misrepresentation2.3.3 — Screenshot accuracy2.3.4 — Preview requirements
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.