Games compete for a download and for continued play. A metadata change can improve discovery, but it cannot rescue a product page that hides the gameplay or a first session that does not deliver the fantasy the listing promised.

Apple’s search guidance applies to games: text relevance uses the title, subtitle, keywords, and primary category, while user behavior such as downloads, ratings, and reviews also matters. Games also have distinct discovery opportunities through game subcategories, the Apple Games app, Game Center activity, In-App Events, previews, and promoted content.

The useful strategy is one connected path:

player intent → search result → gameplay proof → first session → reason to return

Define the player and the play motivation

Genre alone is rarely a complete position. Two puzzle games may serve different motivations: calm daily progress, competitive mastery, narrative discovery, or short social sessions.

Write a brief with:

  • the player and context;
  • the core action repeated during play;
  • the emotion or outcome the game is designed to create;
  • the session length and progression model;
  • the closest substitute games;
  • the distinctive mechanic, world, social system, or content cadence;
  • the first moment that proves the promise.

Example:

A five-minute word puzzle for commuters who want one satisfying daily challenge, with friend comparison but no real-time match commitment.

This sentence makes keyword, screenshot, preview, category, onboarding, and event decisions easier.

Research game-search intent

Build candidate terms from:

  • genre and subgenre;
  • core mechanic;
  • theme or world;
  • mode, such as offline, multiplayer, co-op, daily, or idle;
  • audience and context;
  • emotional outcome;
  • competitor and adjacent-game language;
  • App Store suggestions, reviews, support, community discussion, and Apple Ads search terms.

Separate relevance from popularity. “Strategy game” may be large and accurate but too broad to explain why this game fits the player. “Offline city builder” is narrower and useful only if both claims are true.

Never use another game’s protected name, an irrelevant trending title, or a mechanic the game does not contain. Improper or misleading keywords can lead to rejection and low-quality traffic.

Map the metadata as one message

Name

Keep the brand recognizable and use the remaining space for the clearest relevant genre, mechanic, or fantasy when it reads naturally. Apple currently limits app names to 30 characters.

Subtitle

Use the 30-character subtitle to add a mode, outcome, theme, or differentiator the name does not already provide. Read the two lines together at search-result size.

Private keyword field

Use the 100-character field to extend relevant roots and combinations. Follow Apple’s current rules: avoid repetition from the name, subtitle, and category; avoid duplicate plurals, generic filler, special characters without brand meaning, competitor names, and unrelated terms.

The order of terms is not a documented universal weighting system. Optimize for accurate coverage, not folklore.

Category and subcategories

Apple lets games select Games as a primary or secondary category and choose up to two subcategories. These choices help define the game and affect discovery and comparison context. Choose what the current gameplay actually supports—not the quieter category chart.

If a product is meaningfully both an entertainment app and a game, document the reasoning and check Apple’s category definitions. Category selection is not a substitute for positioning.

Show gameplay before decoration

Depending on orientation and whether a preview is present, up to three screenshots or previews can appear in search results. The first visible assets should help a player answer:

  • What do I do?
  • What kind of game is this?
  • What makes progress or mastery satisfying?
  • Is this single-player, social, competitive, offline, or live?
  • Does the visual style match the actual game?

Use real interface and gameplay states as evidence. Key art can establish the world, but a full sequence of cinematic art without gameplay asks the player to guess.

A useful early sequence might be:

  1. the core fantasy and recognizable gameplay state;
  2. the distinctive mechanic;
  3. progression, strategy, collection, story, or social proof;
  4. modes and content depth;
  5. accessibility, offline play, events, or other important differentiators.

Captions should add meaning. “Epic Adventure” is broad; “Build routes before winter” identifies an action and tension. Test readability at actual thumbnail size.

Use the screenshot guide to plan captions, hierarchy, localization, and a valid creative test.

Use an app preview when motion proves the game

An app preview can demonstrate the loop, controls, pace, and polish more directly than still images. Apple currently allows up to three previews per localization and device size, each 15–30 seconds.

Plan the first seconds carefully:

  • show actual play quickly;
  • make the core action understandable without narration;
  • keep UI, input, and outcomes readable;
  • use accurate content and avoid a trailer that implies a different game;
  • localize on-screen text and supporting assets;
  • select a useful poster frame.

A preview takes the first search-result position when available in some layouts, so verify whether it helps recognition or hides a stronger first screenshot.

Build for the Apple Games app

Games available on the App Store automatically appear in the Apple Games app, including search, library, and continue-playing contexts. The game page uses the same product-page metadata, screenshots, and previews.

That makes storefront quality a cross-surface input. Apple also says Game Center features and In-App Events can receive prominent display across the Games app.

Do not describe this as a hidden organic rank boost. It is a set of documented discovery and engagement surfaces.

Use Game Center when it improves the game

Game Center can add leaderboards, achievements, challenges, multiplayer activities, friend discovery, notifications, and cross-device identity. Apple says enabled games can appear in additional discovery contexts and social recommendations.

Choose features from the player loop:

  • Leaderboards fit comparable scores or times.
  • Achievements fit meaningful progress and mastery.
  • Challenges turn score-based play into a friend activity.
  • Multiplayer activities help players invite and join others.

Do not bolt on meaningless achievements for a marketing checkbox. Design the system to deepen a real motivation, initialize it correctly, localize its metadata, and measure engagement and return behavior.

Publish In-App Events for timely reasons to play

Competitions, challenges, new content, live events, premieres, and other time-bound experiences can appear in the App Store and Apple Games app. They can reach new, current, and previous players.

An event needs:

  • a clear purpose and eligible audience;
  • accurate name, short description, long description, and creative;
  • start and end dates that match the in-game experience;
  • a deep link to the relevant destination when appropriate;
  • localized assets and support readiness;
  • a measurement plan for discovery, interest, downloads, opens, and downstream play.

Routine updates should not be disguised as events. The In-App Events guide covers planning and measurement.

Ask for ratings after real play value

Ratings appear in search and influence player confidence. Ask after a successful, satisfying moment—not during a match, after a loss, immediately after launch, or before the player understands the game.

Possible triggers include completing a meaningful level, returning for several sessions, finishing a challenge, or reaching a progression milestone. Use StoreKit’s system request and remember that Apple controls whether the prompt appears.

Read reviews by version, territory, and theme. Common game-specific themes include difficulty balance, ads, energy systems, pricing, controls, crashes, content cadence, offline behavior, and misleading creative.

Use the ratings and reviews guide for prompting, response operations, and review mining.

Connect acquisition to retention and monetization

A download is not a successful game acquisition if the player never reaches the core loop.

Build a small scorecard:

StageExample signal
Discoverysearch impressions or relevant keyword observations
Evaluationproduct-page views and conversion
First sessiontutorial completion and first core action
Engagementday return, sessions, level or match progress
Monetizationpurchase, subscription, ads, or payer conversion as relevant
Qualitycrashes, refunds, support contacts, review themes

Segment by storefront, version, product page, and acquisition source where the data legitimately supports it. A keyword that brings cheaper installs but weaker players may not deserve more metadata or ad budget.

Test one game-page hypothesis at a time

Use Product Page Optimization for controlled tests of screenshots, previews, descriptions, or icons when eligible. Start with a diagnosed problem:

  • Players cannot identify the genre from the first frame.
  • The creative shows theme but not the core mechanic.
  • Competitive players see a generic single-player page.
  • A landscape preview hides the strongest portrait screenshot.

Define the treatment, primary conversion metric, downstream guardrail, audience, duration, and decision rule. Do not call a new asset a winner because it is more polished.

Game ASO checklist

  • The player, motivation, core loop, and first value moment are explicit.
  • Keywords describe real genre, mechanics, modes, theme, and context.
  • Name, subtitle, field, category, and subcategories work as one system.
  • The first assets show recognizable gameplay and a credible differentiator.
  • Preview footage represents actual pace and play.
  • Apple Games, Game Center, and In-App Events are used only where they improve discovery or engagement honestly.
  • Rating requests follow satisfying, noninterruptive moments.
  • Metadata and creative are localized with the game and support experience.
  • Acquisition is judged with retention, monetization, and quality guardrails.
  • Every iteration has a saved baseline and falsifiable hypothesis.

Primary references