All skills
dpearson2699 avatar

/app-store-optimization

@45c9085

Optimize App Store product pages for search visibility and conversion. Use for App Store Optimization (ASO), keyword research, app name/subtitle/keyword-field strategy, conversion-focused descriptions and promotional text, screenshot captions and ordering, Custom Product Pages with assigned search keywords, In-App Events, Product Page Optimization tests, localized metadata, ratings/review strategy, and in-app review prompt timing with RequestReviewAction or AppStore.requestReview. Also use when routing ASO vs App Store review, privacy/ATT, or StoreKit implementation boundaries.

Use this Skill: https://skilld.dev/gh/dpearson2699/swift-ios-skills/app-store-optimization

This session only. Nothing lands on disk.

referenceskeyword-research-methodology.md

≈2.3k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Keyword Research Methodology

Step-by-step process for identifying, scoring, and maintaining the keyword field for App Store search optimization.

Contents

How Apple Indexes Metadata

Apple documents the main App Store search signals as text relevance, including matches for the app title, subtitle, keywords, and primary category, plus user behavior such as downloads, ratings, and reviews. Use this table as a practical planning map, not as a precise ranking-weight model:

Field Indexed for search? Controllable per version? Notes
App name Yes Yes (with new version/status permitting) 30 characters. Choose a distinctive name that hints at what the app does.
Subtitle Yes Yes (with new version/status permitting) 30 characters. Summarize value or typical use in a concise phrase.
Keyword field Yes Yes (with new version/status permitting) Up to 100 bytes. Use comma-separated terms with no spaces after commas.
Primary category Yes Yes (with new version/status permitting) Apple includes the primary category in search relevance. Do not repeat the category name in keywords.
Custom Product Page assigned keywords Yes, for approved visible pages Yes (in App Store Connect) Can route matching searches to a custom page instead of the default product page.
In-app event name and short description Visible in Search/event cards Yes (per event) Use query-relevant language for the event card, but avoid treating event copy as a hidden keyword field.
Description Conversion-focused Yes (with new version/status permitting) Apple's product page guidance says not to add unnecessary keywords to improve search results.
Promotional text No ranking effect Yes (anytime) Apple says promotional text does not affect search ranking. Use it for timely conversion messaging.
Ratings and reviews Behavior/search signal Ongoing Ratings and reviews influence search and conversion, but review text should be used as customer research rather than keyword stuffing.

Indexing behavior details

  • Do not include both singular and plural forms of the same term; Apple treats them as duplicates.
  • Do not repeat words from the app name, subtitle, or category in the keyword field.
  • Use spaces only inside real keyword phrases; do not add spaces after commas.
  • Keep each comma-separated keyword longer than two characters and the complete field at or below 100 UTF-8 bytes.
  • Include separate related terms when both are genuine search terms, such as "photo" and "photography".

Research Process

Step 1: Competitor audit

Identify the top 5-10 apps ranking for the primary category terms. For each competitor, note:

  • Title and subtitle keywords
  • Visible positioning patterns (terms that appear frequently across top-ranking titles, subtitles, and screenshots)
  • Gaps -- relevant terms that competitors are not targeting

Use App Store search autocomplete to discover what users actually type. Start typing a category term and note the suggested completions.

Step 2: Category analysis

List every term a user might associate with the app's functionality:

  • Primary function terms (what the app does)
  • Use case terms (why a user would want it)
  • Audience terms (who the user is)
  • Adjacent terms (related activities or workflows)

Filter this list against competitor findings. Terms that appear in many competitor titles are high-volume but high-competition. Terms that appear in autocomplete but not in competitor metadata represent opportunities.

Step 3: Search Ads discovery

Run Apple Search Ads discovery campaigns with broad-match keywords matching the primary function. After 2-4 weeks of data:

  • Export the search term report to see actual queries that triggered impressions.
  • Sort by tap-through rate (TTR) to identify high-intent terms.
  • Sort by conversion rate to identify terms where users who find the app actually download it.
  • Add high-performing discovered terms to the keyword field.

Step 4: Iteration cycle

With each app update:

  1. Review App Analytics for keyword impressions, tap-through rates, and conversion rates.
  2. Identify underperforming keywords (low impressions or low TTR) and replace them.
  3. Test new terms discovered through Search Ads or category changes.
  4. Check if competitor metadata has shifted -- new competitors or renamed apps can change the keyword landscape.

Keyword Scoring Framework

Score each candidate keyword on three dimensions:

Dimension Score range How to assess
Relevance 1-5 Does the keyword describe what the app actually does? 5 = core function, 1 = tangentially related
Volume 1-5 Is this term frequently searched? Use Search Ads impression data as a proxy. 5 = high impressions, 1 = minimal
Difficulty 1-5 How many established apps target this term? 5 = low competition (good), 1 = dominated by major apps

Decision rule: Include a keyword only if Relevance >= 3. Among qualifying keywords, prioritize by (Relevance x 2) + Volume + Difficulty. This weights relevance heavily while still favoring discoverable, winnable terms.

Disqualify keywords that:

  • Do not describe the app's actual functionality (Relevance < 3)
  • Are competitor brand names (violates App Store guidelines)
  • Duplicate a word already in the title or subtitle
  • Are the app's primary category name (Apple adds it automatically)

Slot Allocation Strategy

The 100-character keyword field requires careful allocation. Here are allocation patterns for different app types:

Example: Fitness tracking app

Title: FitTrack -- Workout Log (23 chars used) Subtitle: Exercise & Activity Stats (25 chars used)

Keyword field strategy -- do not repeat: fittrack, workout, log, exercise, activity, stats

gym,training,health,run,step,calorie,weight,strength,cardio,hiit,yoga,plank,squat,routine,progress

(96 characters -- 4 remaining, all unique against title/subtitle)

Example: Photo editing app

Title: PixelPop -- Photo Editor (24 chars used) Subtitle: Filters & Retouch Tools (23 chars used)

Keyword field -- do not repeat: pixelpop, photo, editor, filter, retouch, tool

selfie,portrait,collage,crop,blur,preset,enhance,adjust,brightness,contrast,saturation,beauty,skin

(99 characters -- all unique against title/subtitle)

Allocation principles

  • Each comma costs 1 character. Fewer, longer keywords are not inherently better than more, shorter ones -- Apple matches individual words, not phrases.
  • If two terms are searched as a phrase (e.g., "meal prep"), use the phrase when it matches real query behavior; use separate terms when each word is independently valuable.
  • Reserve 5-10 characters for experimental keywords that rotate each release based on performance data.

Seasonal Keyword Rotation

Some keywords have seasonal search volume spikes. Plan rotation around predictable events:

Season/Event Example keywords to add When to deploy
New Year resolution,goal,habit,new year December release
Back to school student,school,study,planner July/August release
Holiday shopping gift,holiday,deal,wish list October/November release
Summer fitness outdoor,running,summer,beach April/May release
Tax season tax,receipt,expense,deduction January/February release

Rotate 2-3 keyword slots per seasonal cycle. Keep the core 70-80 characters stable and use the remaining 20-30 characters for seasonal experimentation.

Before and After Examples

Problem: Wasted characters

Before:

fitness tracker, workout app, best exercise, health and wellness, gym

Issues: spaces after commas (-5 chars wasted), "fitness" and "tracker" may duplicate title, "best" and "app" have no search value, "and" is a stop word.

After:

gym,health,run,step,calorie,weight,strength,cardio,hiit,yoga,plank,squat,routine,progress,streak

Fixes: no spaces, no duplicates of title/subtitle, no filler words, all terms are genuine search queries.

Problem: Duplicate keywords

Before (title is "RunMate -- Running Tracker"):

running,tracker,run,jog,marathon,race,pace,distance,route,gps,heart,rate,training,fitness,health

Issues: "running", "tracker", and "run" duplicate the title -- 17 characters wasted.

After:

jog,marathon,race,pace,distance,route,gps,heart,rate,training,fitness,health,stride,tempo,interval

Fixes: removed title duplicates, added 3 new high-value terms with the recovered space.

Source: SKILL.md on GitHub

No alerts16d3 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill consists of documentation and reference materials for App Store Optimization (ASO). It contains no executable code, network-active components, or instructions that interact with sensitive system data.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

Signed by skilld at 45c9085. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Steadyupdated 3 months ago

README badge

README badge for dpearson2699/swift-ios-skills/app-store-optimization