App categories and tags accurately describe content

Miscategorized apps surface to the wrong user audience in store search and browse — a productivity app filed under Games will appear in game charts and recommendations, driving low-intent installs from users who immediately uninstall when the app doesn't match their expectation. Both Apple App Store (apple-app-store-categories) and Google Play (google-play-categories) use category as a primary browse and search signal; correct categorization directly affects organic discoverability and install conversion rate. Additionally, apps with keywords that don't match their functionality are more likely to be flagged in manual review as keyword stuffing, which can trigger reviewer scrutiny of the entire listing.

Set the primary category in store metadata during App Store Connect and Play Console submission. If your project uses a store-metadata/ directory, encode it there for reproducibility.

// store-metadata/metadata.json (example convention)
{
  "category": "productivity",
  "keywords": ["tasks", "notes", "planner", "to-do", "reminders"]
}

Choose the category that describes your app's primary function, not aspirational positioning. Cross-check the app store's official category taxonomy — Apple's list is at https://developer.apple.com/app-store/categories/ and Play's at the Play Console help docs. Keywords should be terms users actually search for; test by searching in the App Store or Play Store before finalizing.

• ID: app-categories-tagged
• Severity: low
• What to look for: Look for app metadata files (app.json, eas.json, store-metadata folder, or config files) that specify app category and tags/keywords. Count the number of keywords or tags defined. Check if the categories selected are accurate (e.g., app is marked as "productivity" if it's a task manager, not "games" if it has no games). Verify tags/keywords accurately reflect the app's purpose.
• Pass criteria: App is assigned to an appropriate primary category (e.g., "Productivity", "Social", "Health & Fitness", "Games"). At least 2 keywords or tags are defined that match the app's features and use case.
• Fail criteria: App is assigned to an inappropriate category (e.g., a messaging app filed under "Games"), fewer than 2 keywords defined, or tags do not match the app's actual functionality.
• Skip (N/A) when: App category and tagging is not configured in source code (typically set directly in app store consoles).
• Detail on fail: "App is categorized as 'Games' but is a note-taking app" or "Tags include 'social media' but app is a weather app with no social features"
• Remediation: Correct categorization improves app discoverability and prevents store rejection. Set up:
  1. Review app store category options:
     • Apple App Store: https://developer.apple.com/app-store/categories/
     • Google Play Store: https://support.google.com/googleplay/android-developer/answer/9859673
  2. Select primary category that best matches your app's main use case
  3. If using EAS or app.json, set categories (if supported):

     "category": "productivity",
     "keywords": ["notes", "tasks", "productivity"]
     

  4. Be specific and honest — wrong categorization wastes your app's discoverability and may trigger store review flags
  5. Use keywords that users actually search for (test on store to verify)
  6. Periodically review and update if app functionality changes