App Store category selection review checklist
Category selection affects discovery, expectations, and policy context. It should describe the app's main job, not only the keyword with the largest market.
Select category from the primary user task and the app's actual functionality. Apple documents App Store categories and category management in App Store Connect. AppReviewReady interpretation: category choice should be provable from first-run behavior, screenshots, and support readiness.
Name the primary user job
Before choosing a category, describe what the user completes in the app: learn, buy, track, create, communicate, navigate, manage money, control hardware, play, or consume media. Then compare that job with the category promise.
A category selected only for traffic can create mismatch. Reviewers and users may judge a finance-looking app, kids-looking app, or health-looking app under expectations that the product cannot satisfy.
Check category fit evidence
- The first screenshots show the same job as the selected category.
- The app name, subtitle, icon, and description do not point to a different category.
- The primary category fits more strongly than a secondary marketing angle.
- Regulated categories have support, licenses, disclaimers, and age rating aligned.
- If the app has multiple audiences, the installed experience still has one dominant purpose.
Handle edge-case products deliberately
Education games, wellness trackers, creator marketplaces, finance news, social fitness, and hardware utilities can sit between categories. Pick the category that best reflects the repeated user workflow rather than the broadest possible audience.
AppReviewReady interpretation: category is not a substitute for metadata clarity. If the product crosses categories, screenshots and onboarding should explain the relationship quickly.
Retest category changes before release
- Review metadata, keywords, screenshots, age rating, and privacy labels after a category change.
- Check whether category-specific competitors make your app's claim look misleading.
- Confirm support can answer questions implied by the new category.
- Update internal positioning so ads and landing pages do not conflict with the category.
- Monitor conversion and refund quality after launch.
Category decision record
The decision record prevents last-minute category switching from becoming an SEO shortcut. It also helps compare category performance after enough impression data exists.
After launch, compare search terms and page conversion. If the category attracts irrelevant traffic, the next experiment may be a metadata repositioning rather than more content publishing.
If a category change is part of a growth experiment, define the stop condition first. Higher impressions are not useful if the app attracts users who immediately bounce, refund, or ask for a feature the app does not provide.
For apps with child, medical, finance, gambling-adjacent, or dating-adjacent signals, review category and age rating together. A category can change the context in which screenshots and claims are interpreted.
When an app expands into a new feature area, wait until the new workflow is visible and stable before changing the primary category. Premature recategorization can make the current build look misleading.
Category record: Primary job: [job] Primary category: [category] Secondary category: [category or none] Proof screens: [screens] Regulated expectations: [none/list] Metadata changed: [fields] Post-launch metric: [signal]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check category fit
Review category, metadata, screenshots, and policy expectations before submission.
Open the tool