App Store Optimization (ASO)
Keyword Research Workflow
Discover and evaluate keywords that drive app store visibility.
Workflow: Conduct Keyword Research
- 1. Define target audience and core app functions:
- Primary use case (what problem does the app solve)
- Target user demographics
- Competitive category
- 2. Generate seed keywords from:
- App features and benefits
- User language (not developer terminology)
- App store autocomplete suggestions
- 3. Expand keyword list using:
- Modifiers (free, best, simple)
- Actions (create, track, organize)
- Audiences (for students, for teams, for business)
- 4. Evaluate each keyword:
- Search volume (estimated monthly searches)
- Competition (number and quality of ranking apps)
- Relevance (alignment with app function)
- 5. Score and prioritize keywords:
- Primary: Title and keyword field (iOS)
- Secondary: Subtitle and short description
- Tertiary: Full description only
- 6. Map keywords to metadata locations
- Document keyword strategy for tracking
- Validation: Keywords scored; placement mapped; no competitor brand names included; no plurals in iOS keyword field
Keyword Evaluation Criteria
| Factor | Weight | High Score Indicators |
|---|
| Relevance | 35% | Describes core app function |
| Volume |
25% | 10,000+ monthly searches |
| Competition | 25% | Top 10 apps have <4.5 avg rating |
| Conversion | 15% | Transactional intent ("best X app") |
Keyword Placement Priority
| Location | Search Weight |
|---|
| App Title | Highest |
| Subtitle (iOS) |
High |
| Keyword Field (iOS) | High |
| Short Description (Android) | High |
| Full Description | Medium |
See: references/keyword-research-guide.md
Metadata Optimization Workflow
Optimize app store listing elements for search ranking and conversion.
Workflow: Optimize App Metadata
- 1. Audit current metadata against platform limits:
- Title character count and keyword presence
- Subtitle/short description usage
- Keyword field efficiency (iOS)
- Description keyword density
- 2. Optimize title following formula:
[Brand Name] - [Primary Keyword] [Secondary Keyword]
- 3. Write subtitle (iOS) or short description (Android):
- Focus on primary benefit
- Include secondary keyword
- Use action verbs
- 4. Optimize keyword field (iOS only):
- Remove duplicates from title
- Remove plurals (Apple indexes both forms)
- No spaces after commas
- Prioritize by score
- 5. Rewrite full description:
- Hook paragraph with value proposition
- Feature bullets with keywords
- Social proof section
- Call to action
- 6. Validate character counts for each field
- Calculate keyword density (target 2-3% primary)
- Validation: All fields within character limits; primary keyword in title; no keyword stuffing (>5%); natural language preserved
Platform Character Limits
| Field | Apple App Store | Google Play Store |
|---|
| Title | 30 characters | 50 characters |
| Subtitle |
30 characters | N/A |
| Short Description | N/A | 80 characters |
| Keywords | 100 characters | N/A |
| Promotional Text | 170 characters | N/A |
| Full Description | 4,000 characters | 4,000 characters |
| What's New | 4,000 characters | 500 characters |
Description Structure
CODEBLOCK1
See: references/platform-requirements.md
Competitor Analysis Workflow
Analyze top competitors to identify keyword gaps and positioning opportunities.
Workflow: Analyze Competitor ASO Strategy
- 1. Identify top 10 competitors:
- Direct competitors (same core function)
- Indirect competitors (overlapping audience)
- Category leaders (top downloads)
- 2. Extract competitor keywords from:
- App titles and subtitles
- First 100 words of descriptions
- Visible metadata patterns
- 3. Build competitor keyword matrix:
- Map which keywords each competitor targets
- Calculate coverage percentage per keyword
- 4. Identify keyword gaps:
- Keywords with <40% competitor coverage
- High volume terms competitors miss
- Long-tail opportunities
- 5. Analyze competitor visual assets:
- Icon design patterns
- Screenshot messaging and style
- Video presence and quality
- 6. Compare ratings and review patterns:
- Average rating by competitor
- Common praise themes
- Common complaint themes
- 7. Document positioning opportunities
- Validation: 10+ competitors analyzed; keyword matrix complete; gaps identified with volume estimates; visual audit documented
Competitor Analysis Matrix
| Analysis Area | Data Points |
|---|
| Keywords | Title keywords, description frequency |
| Metadata |
Character utilization, keyword density |
| Visuals | Icon style, screenshot count/style |
| Ratings | Average rating, total count, velocity |
| Reviews | Top praise, top complaints |
Gap Analysis Template
| Opportunity Type | Example | Action |
|---|
| Keyword gap | "habit tracker" (40% coverage) | Add to keyword field |
| Feature gap |
Competitor lacks widget | Highlight in screenshots |
| Visual gap | No videos in top 5 | Create app preview |
| Messaging gap | None mention "free" | Test free positioning |
App Launch Workflow
Execute a structured launch for maximum initial visibility.
Workflow: Launch App to Stores
- 1. Complete pre-launch preparation (4 weeks before):
- Finalize keywords and metadata
- Prepare all visual assets
- Set up analytics (Firebase, Mixpanel)
- Build press kit and media list
- 2. Submit for review (2 weeks before):
- Complete all store requirements
- Verify compliance with guidelines
- Prepare launch communications
- 3. Configure post-launch systems:
- Set up review monitoring
- Prepare response templates
- Configure rating prompt timing
- 4. Execute launch day:
- Verify app is live in both stores
- Announce across all channels
- Begin review response cycle
- 5. Monitor initial performance (days 1-7):
- Track download velocity hourly
- Monitor reviews and respond within 24 hours
- Document any issues for quick fixes
- 6. Conduct 7-day retrospective:
- Compare performance to projections
- Identify quick optimization wins
- Plan first metadata update
- 7. Schedule first update (2 weeks post-launch)
- Validation: App live in stores; analytics tracking; review responses within 24h; download velocity documented; first update scheduled
Pre-Launch Checklist
| Category | Items |
|---|
| Metadata | Title, subtitle, description, keywords |
| Visual Assets |
Icon, screenshots (all sizes), video |
| Compliance | Age rating, privacy policy, content rights |
| Technical | App binary, signing certificates |
| Analytics | SDK integration, event tracking |
| Marketing | Press kit, social content, email ready |
Launch Timing Considerations
| Factor | Recommendation |
|---|
| Day of week | Tuesday-Wednesday (avoid weekends) |
| Time of day |
Morning in target market timezone |
| Seasonal | Align with relevant category seasons |
| Competition | Avoid major competitor launch dates |
See: references/aso-best-practices.md
A/B Testing Workflow
Test metadata and visual elements to improve conversion rates.
Workflow: Run A/B Test
- 1. Select test element (prioritize by impact):
- Icon (highest impact)
- Screenshot 1 (high impact)
- Title (high impact)
- Short description (medium impact)
- 2. Form hypothesis:
If we [change], then [metric] will [improve/increase] by [amount]
because [rationale].
- 3. Create variants:
- Control: Current version
- Treatment: Single variable change
- 4. Calculate required sample size:
- Baseline conversion rate
- Minimum detectable effect (usually 5%)
- Statistical significance (95%)
- 5. Launch test:
- Apple: Use Product Page Optimization
- Android: Use Store Listing Experiments
- 6. Run test for minimum duration:
- At least 7 days
- Until statistical significance reached
- 7. Analyze results:
- Compare conversion rates
- Check statistical significance
- Document learnings
- 8. Validation: Single variable tested; sample size sufficient; significance reached (95%); results documented; winner implemented
A/B Test Prioritization
| Element | Conversion Impact | Test Complexity |
|---|
| App Icon | 10-25% lift possible | Medium (design needed) |
| Screenshot 1 |
15-35% lift possible | Medium |
| Title | 5-15% lift possible | Low |
| Short Description | 5-10% lift possible | Low |
| Video | 10-20% lift possible | High |
Sample Size Quick Reference
| Baseline CVR | Impressions Needed (per variant) |
|---|
| 1% | 31,000 |
| 2% |
15,500 |
| 5% | 6,200 |
| 10% | 3,100 |
Test Documentation Template
CODEBLOCK3
Before/After Examples
Title Optimization
Productivity App:
| Version | Title | Analysis |
|---|
| Before | "MyTasks" | No keywords, brand only (8 chars) |
| After |
"MyTasks - Todo List & Planner" | Primary + secondary keywords (29 chars) |
Fitness App:
| Version | Title | Analysis |
|---|
| Before | "FitTrack Pro" | Generic modifier (12 chars) |
| After |
"FitTrack: Workout Log & Gym" | Category keywords (27 chars) |
Subtitle Optimization (iOS)
| Version | Subtitle | Analysis |
|---|
| Before | "Get Things Done" | Vague, no keywords |
| After |
"Daily Task Manager & Planner" | Two keywords, benefit clear |
Keyword Field Optimization (iOS)
Before (Inefficient - 89 chars, 8 keywords):
CODEBLOCK4
After (Optimized - 97 chars, 14 keywords):
CODEBLOCK5
Improvements:
- - Removed spaces after commas (+8 chars)
- Removed duplicates (task manager → task)
- Removed plurals (reminders → reminder)
- Removed words in title
- Added more relevant keywords
Description Opening
Before:
CODEBLOCK6
After:
CODEBLOCK7
Improvements:
- - Leads with user pain point
- Specific benefit (not generic "boost productivity")
- Social proof included
- Keywords natural, not stuffed
Screenshot Caption Evolution
| Version | Caption | Issue |
|---|
| Before | "Task List Feature" | Feature-focused, passive |
| Better |
"Create Task Lists" | Action verb, but still feature |
| Best | "Never Miss a Deadline" | Benefit-focused, emotional |
Tools and References
Scripts
Validate metadata character limits and density |
python metadata_optimizer.py --platform ios --title "App Title" |
|
competitor_analyzer.py | Extract and compare competitor keywords |
python competitor_analyzer.py --competitors "App1,App2,App3" |
|
aso_scorer.py | Calculate overall ASO health score |
python aso_scorer.py --app-id com.example.app |
|
abtest_planner.py | Plan tests and calculate sample sizes |
python ab_test_planner.py --cvr 0.05 --lift 0.10 |
|
review_analyzer.py | Analyze review sentiment and themes |
python review_analyzer.py --app-id com.example.app |
|
launch_checklist.py | Generate platform-specific launch checklists |
python launch_checklist.py --platform ios |
|
localization_helper.py | Manage multi-language metadata |
python localization_helper.py --locales "en,es,de,ja" |
References
Optimization strategies, rating management, launch tactics |
|
keyword-research-guide.md | Research methodology, evaluation framework, tracking |
Assets
Platform Notes
| Platform / Constraint | Behavior / Impact |
|---|
| iOS keyword changes | Require app submission |
| iOS promotional text |
Editable without an app update |
| Android metadata changes | Index in 1-2 hours |
| Android keyword field | None — use description instead |
| Keyword volume data | Estimates only; no official source |
| Competitor data | Public listings only |
When not to use this skill: web apps (use web SEO), enterprise/internal apps, TestFlight-only betas, or paid advertising strategy.
Related Skills
Launch promotion campaigns |
|
marketing-strategy-pmm | Go-to-market planning |
Proactive Triggers
- - No keyword optimization in title → App title is the #1 ranking factor. Include top keyword.
- Screenshots don't show value → Screenshots should tell a story, not show UI.
- No ratings strategy → Below 4.0 stars kills conversion. Implement in-app rating prompts.
- Description keyword-stuffed → Natural language with keywords beats keyword stuffing.
Output Artifacts
| When you ask for... | You get... |
|---|
| "ASO audit" | Full app store listing audit with prioritized fixes |
| "Keyword research" |
Keyword list with search volume and difficulty scores |
| "Optimize my listing" | Rewritten title, subtitle, description, keyword field |
Communication
All output passes quality verification:
- - Self-verify: source attribution, assumption audit, confidence scoring
- Output format: Bottom Line → What (with confidence) → Why → How to Act
- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.
应用商店优化 (ASO)
关键词研究工作流程
发现并评估能够提升应用商店可见度的关键词。
工作流程:开展关键词研究
- 1. 定义目标受众和核心应用功能:
- 主要使用场景(应用解决什么问题)
- 目标用户人口统计特征
- 竞争类别
- 2. 从以下来源生成种子关键词:
- 应用功能和优势
- 用户语言(非开发者术语)
- 应用商店自动补全建议
- 3. 使用以下方式扩展关键词列表:
- 修饰词(免费、最佳、简单)
- 动作词(创建、追踪、整理)
- 受众词(面向学生、面向团队、面向企业)
- 4. 评估每个关键词:
- 搜索量(预估月搜索次数)
- 竞争度(排名应用的数量和质量)
- 相关性(与应用功能的匹配度)
- 5. 评分并优先排序关键词:
- 主要:标题和关键词字段(iOS)
- 次要:副标题和简短描述
- 第三:仅完整描述
- 6. 将关键词映射到元数据位置
- 记录关键词策略以便追踪
- 验证: 关键词已评分;位置已映射;未包含竞品品牌名称;iOS关键词字段中无复数形式
关键词评估标准
| 因素 | 权重 | 高分指标 |
|---|
| 相关性 | 35% | 描述核心应用功能 |
| 搜索量 |
25% | 月搜索量10,000次以上 |
| 竞争度 | 25% | 排名前10的应用平均评分<4.5 |
| 转化率 | 15% | 交易意图(最佳X应用) |
关键词放置优先级
高 |
| 关键词字段(iOS) | 高 |
| 简短描述(Android) | 高 |
| 完整描述 | 中等 |
参见:references/keyword-research-guide.md
元数据优化工作流程
优化应用商店列表元素以提升搜索排名和转化率。
工作流程:优化应用元数据
- 1. 对照平台限制审计当前元数据:
- 标题字符数和关键词存在情况
- 副标题/简短描述使用情况
- 关键词字段效率(iOS)
- 描述关键词密度
- 2. 按照以下公式优化标题:
[品牌名称] - [主要关键词] [次要关键词]
- 3. 撰写副标题(iOS)或简短描述(Android):
- 聚焦主要优势
- 包含次要关键词
- 使用动作动词
- 4. 优化关键词字段(仅限iOS):
- 移除标题中的重复词
- 移除复数形式(Apple对两种形式都建立索引)
- 逗号后不加空格
- 按评分优先排序
- 5. 重写完整描述:
- 价值主张钩子段落
- 带关键词的功能要点
- 社交证明部分
- 行动号召
- 6. 验证每个字段的字符数
- 计算关键词密度(目标主要关键词2-3%)
- 验证: 所有字段在字符限制内;标题中包含主要关键词;无关键词堆砌(>5%);保留自然语言
平台字符限制
| 字段 | Apple App Store | Google Play Store |
|---|
| 标题 | 30个字符 | 50个字符 |
| 副标题 |
30个字符 | 不适用 |
| 简短描述 | 不适用 | 80个字符 |
| 关键词 | 100个字符 | 不适用 |
| 推广文本 | 170个字符 | 不适用 |
| 完整描述 | 4,000个字符 | 4,000个字符 |
| 更新内容 | 4,000个字符 | 500个字符 |
描述结构
第1段:钩子(50-100字)
├── 解决用户痛点
├── 陈述主要价值主张
└── 包含主要关键词
第2-3段:功能(100-150字)
├── 前5个功能及优势
├── 要点列表便于浏览
└── 自然融入次要关键词
第4段:社交证明(50-75字)
├── 下载量或评分
├── 媒体报道或奖项
└── 用户评价摘要
第5段:行动号召(25-50字)
├── 明确的下一步操作
└── 保证(免费试用、无需注册)
参见:references/platform-requirements.md
竞品分析工作流程
分析主要竞品以发现关键词缺口和定位机会。
工作流程:分析竞品ASO策略
- 1. 确定前10名竞品:
- 直接竞品(相同核心功能)
- 间接竞品(重叠受众)
- 类别领先者(下载量最高)
- 2. 从以下来源提取竞品关键词:
- 应用标题和副标题
- 描述前100个词
- 可见的元数据模式
- 3. 构建竞品关键词矩阵:
- 映射每个竞品针对的关键词
- 计算每个关键词的覆盖率百分比
- 4. 识别关键词缺口:
- 竞品覆盖率<40%的关键词
- 竞品遗漏的高搜索量词
- 长尾机会
- 5. 分析竞品视觉素材:
- 图标设计模式
- 截图信息和风格
- 视频存在性和质量
- 6. 比较评分和评论模式:
- 各竞品平均评分
- 常见好评主题
- 常见差评主题
- 7. 记录定位机会
- 验证: 分析了10个以上竞品;关键词矩阵完整;识别出带搜索量估算的缺口;视觉审计已记录
竞品分析矩阵
字符利用率、关键词密度 |
| 视觉 | 图标风格、截图数量/风格 |
| 评分 | 平均评分、总数、变化速度 |
| 评论 | 主要好评、主要差评 |
缺口分析模板
| 机会类型 | 示例 | 行动 |
|---|
| 关键词缺口 | 习惯追踪(40%覆盖率) | 添加到关键词字段 |
| 功能缺口 |
竞品缺少小组件 | 在截图中突出显示 |
| 视觉缺口 | 前5名中无视频 | 创建应用预览 |
| 信息缺口 | 无人提及免费 | 测试免费定位 |
应用发布工作流程
执行结构化发布以获得最大初始可见度。
工作流程:向商店发布应用
- 1. 完成发布前准备(发布前4周):
- 确定关键词和元数据
- 准备所有视觉素材
- 设置分析工具(Firebase、Mixpanel)
- 构建媒体资料包和媒体列表
- 2. 提交审核(发布前2周):
- 完成所有商店要求
- 验证是否符合指南
- 准备发布沟通材料
- 3. 配置发布后系统:
- 设置评论监控
- 准备回复模板
- 配置评分提示时机
- 4. 执行发布日:
- 验证应用在两个商店均已上线
- 在所有渠道发布公告
- 开始评论回复周期
- 5. 监控初期表现(第1-7天):
- 每小时追踪下载速度
- 监控评论并在24小时内回复
- 记录任何问题以便快速修复
- 6. 进行7天回顾:
- 将表现与预测对比
- 识别快速优化机会
- 计划首次元数据更新
- 7. 安排首次更新(发布后2周)
- 验证: 应用在商店上线;分析追踪已启用;评论在24小时内回复;下载速度已记录;首次更新已安排
发布前检查清单
图标、截图(所有尺寸)、视频 |
| 合规性 | 年龄分级、隐私政策、内容版权 |
| 技术 | 应用二进制文件、签名证书 |
| 分析 | SDK集成、事件追踪 |
| 营销 | 媒体资料包、社交媒体内容、邮件准备就绪 |
发布时机考虑因素
目标市场时区的上午 |
| 季节性 | 与相关类别季节对齐 |
| 竞争 | 避开主要竞品发布日期 |
参见:[references