AgentSkillsCN

app-store-optimization

iOS App Store 和 Google Play Store 的应用商店优化(ASO)技能。适用于以下优化场景:(1) 应用标题、副标题与描述;(2) 应用关键词与元数据;(3) 截图与预览视频;(4) 评分与评论策略;(5) 针对国际市场的本地化。可通过“ASO”、“应用商店优化”、“Play Store 上架”、“App Store 上架”或应用可见性相关请求触发。

SKILL.md
--- frontmatter
name: app-store-optimization
description: "App Store Optimization (ASO) skill for iOS App Store and Google Play Store. Use when optimizing: (1) App titles, subtitles, and descriptions, (2) App keywords and metadata, (3) Screenshots and preview videos, (4) Ratings and review strategies, (5) Localization for international markets. Triggers on 'ASO', 'app store optimization', 'Play Store listing', 'App Store listing', or app visibility requests."
license: Proprietary

App Store Optimization (ASO) Skill

Comprehensive optimization for iOS App Store and Google Play Store visibility.

Quick Reference

ElementiOS App StoreGoogle Play Store
App Name30 characters30 characters
Subtitle30 charactersN/A
Short DescriptionN/A80 characters
Full Description4,000 characters4,000 characters
Keywords100 characters (hidden)In description (indexed)
ScreenshotsUp to 10Up to 8
Preview VideoUp to 3 (30s each)1 (30s-2min)
Promotional Text170 charactersN/A

ASO Fundamentals

How App Store Algorithms Work

code
User Search Query
      │
      ├── Keyword Matching
      │   ├── App Name/Title
      │   ├── Subtitle (iOS) / Short Description (Play)
      │   ├── Keywords (iOS) / Description (Play)
      │   └── Developer Name
      │
      ├── Relevance Signals
      │   ├── Category match
      │   ├── Keyword density
      │   └── Search-to-install correlation
      │
      └── Quality Signals
          ├── Download velocity
          ├── Ratings & reviews
          ├── Engagement metrics
          ├── Retention rates
          └── Crash rates

Key ASO Ranking Factors

FactoriOS WeightAndroid Weight
App Name/TitleVery HighVery High
Keyword FieldVery HighN/A
DescriptionLowHigh
DownloadsHighHigh
Rating/ReviewsHighHigh
Update FrequencyMediumMedium
EngagementMediumHigh
BacklinksN/ALow

iOS App Store Optimization

App Name (30 characters)

Strategy:

  • Brand name + primary keyword
  • Most important ranking factor
  • Visible in search results

Format:

code
[Brand Name] - [Primary Keyword]
[Brand Name]: [Benefit Statement]

Examples:

code
Good: "Headspace: Sleep & Meditation"
Good: "Calm - Meditate, Sleep, Relax"
Bad:  "The Best Sleep and Meditation App for Relaxation" (too long)

Rules:

  • Use full 30 characters
  • Include top keyword
  • Keep brand recognizable
  • No keyword stuffing
  • No generic terms alone

Subtitle (30 characters)

Strategy:

  • Secondary keywords
  • Explain app function
  • Differentiator or benefit

Format:

code
[Secondary Keyword] + [Benefit/Feature]

Examples:

code
Good: "Daily Mindfulness & Sleep"
Good: "Focus Timer & Habit Tracker"
Bad:  "The Best App Ever Made" (no keywords)

Keyword Field (100 characters)

Strategy:

  • Hidden from users
  • Comma-separated (no spaces after commas)
  • No duplicates (already in name/subtitle)
  • Include misspellings and variants
  • Use singular forms (Apple finds plurals)

Format:

code
keyword1,keyword2,keyword3,keyword4,misspelling,variant

Research Process:

  1. Brainstorm seed keywords
  2. Analyze competitor keywords (tools: AppTweak, Sensor Tower)
  3. Check search volume estimates
  4. Assess difficulty/competition
  5. Select mix of high-volume and long-tail

Prioritization:

PriorityKeyword TypeExample
1High volume, medium competition"meditation"
2Medium volume, low competition"sleep sounds"
3Long-tail specific"anxiety relief app"
4Misspellings"mediation"

Full Description (4,000 characters)

Note: iOS description is NOT indexed for search. Focus on conversion.

Structure:

code
[Hook - compelling first line visible before "more"]

[Core Benefits - bullet points or short paragraphs]
• Benefit 1
• Benefit 2
• Benefit 3

[Social Proof]
"Featured by Apple" / "10 million downloads"

[Key Features]
Feature 1: Description
Feature 2: Description

[Subscription Details - if applicable]
Pricing, trial information

[Call to Action]
Download now and start [benefit]

[Legal/Contact]
Terms, privacy, support contact

Promotional Text (170 characters)

Strategy:

  • Can be updated without review
  • Use for timely promotions
  • Seasonal messaging
  • Feature announcements

Examples:

code
"New: Sleep Stories narrated by celebrities. Try our 7-day free trial!"
"Holiday Special: 50% off annual subscription. Limited time offer."

Screenshots (Up to 10)

iOS Screenshot Sizes

DeviceSize (pixels)
iPhone 6.7"1290 x 2796
iPhone 6.5"1284 x 2778
iPhone 5.5"1242 x 2208
iPad 12.9"2048 x 2732

Screenshot Strategy

Order of Screenshots:

  1. Hero shot with main value proposition
  2. Key feature 1
  3. Key feature 2
  4. Social proof / testimonials
  5. Key feature 3
  6. Differentiator 7-10. Additional features

Design Best Practices:

  • Clear headline text (large, readable)
  • Actual app UI shown
  • Consistent design language
  • Show real content, not placeholders
  • Highlight key actions/features
  • Use captions that explain benefits

Caption Formula:

code
[Benefit/Outcome] + [Feature that delivers it]

Examples:
"Fall Asleep Faster with Guided Sleep Stories"
"Track Your Progress with Beautiful Statistics"
"Stay Focused with Customizable Timers"

App Preview Videos (Up to 3, 30s each)

Structure:

code
0-5s:  Hook - show main benefit
5-15s: Key feature 1 demo
15-25s: Key feature 2 demo
25-30s: Call to action + app icon

Rules:

  • No external footage (only app capture)
  • Can include device frame
  • Text overlays allowed
  • Music/voiceover allowed
  • Must reflect actual app experience

Google Play Store Optimization

App Title (30 characters)

Same strategy as iOS, but more weight given to keywords.

Format:

code
[Brand Name]: [Primary Keyword]
[Brand Name] - [Keyword Phrase]

Short Description (80 characters)

Strategy:

  • Indexed for search (important for rankings)
  • Visible in search results
  • Include 2-3 target keywords
  • Compelling benefit statement

Formula:

code
[Action verb] + [benefit] + [keyword] + [differentiator]

Examples:

code
Good: "Meditate daily with guided sessions. Reduce stress & sleep better."
Good: "Learn languages fast with AI. Spanish, French, German & more."
Bad:  "Download our amazing app today!" (no keywords)

Full Description (4,000 characters)

Important: Unlike iOS, Play Store description IS indexed for search.

Keyword Strategy

  • Include keywords naturally throughout
  • Repeat important keywords 3-5 times
  • Use variations and synonyms
  • Front-load keywords in first paragraph
  • Don't keyword stuff (readability matters)

Structure

code
[First paragraph - keyword rich, benefit focused]
Include your most important keywords naturally in the first
2-3 sentences. This is what users see before expanding.

[Features section with keywords]
✓ Feature 1 with [keyword]
✓ Feature 2 with [keyword]
✓ Feature 3 with [keyword]

[How it works / Use cases]
Describe common use cases using keyword variations.

[Social proof]
• 10M+ downloads
• 4.8★ average rating
• Featured in [publications]

[Detailed features]
**[Keyword] Feature Name**
Description of feature with natural keyword usage.

**Another Feature**
Description continuing keyword integration.

[Subscription/pricing info if applicable]

[Contact and support information]

Formatting

code
Use these elements:
• Bullet points (✓ ★ • ►)
• Bold for emphasis (limited use)
• Short paragraphs (2-3 lines)
• Clear section breaks
• Emojis sparingly 😊

Screenshots (Up to 8)

Play Store Screenshot Sizes

TypeSize (pixels)Ratio
Phone1080 x 192016:9
Tablet 7"1200 x 1920-
Tablet 10"1800 x 2560-

Play Store Specifics

  • First 3 screenshots most important
  • Landscape mode supported
  • Feature graphic prominently displayed
  • A/B testing available through Play Console

Feature Graphic (1024 x 500)

Requirements:

  • Displayed at top of listing
  • Used in promotional placements
  • No text required (but can include)
  • Brand-focused design

Best Practices:

  • Bold, eye-catching design
  • Consistent with brand
  • Works at various sizes
  • No essential text (may be cropped)

Promo Video (30s - 2 minutes)

YouTube hosted (linked to Play Store listing)

Structure:

code
0-5s:   Hook with main benefit
5-30s:  Feature demonstrations
30-60s: Extended features (if longer)
Final:  Download CTA with Play Store badge

Ratings & Reviews Strategy

Importance

RatingImpact
4.5+Significantly higher conversion
4.0-4.4Competitive
3.5-3.9Negative impact begins
Below 3.5Major conversion issue

Generating Reviews

In-App Review Prompts

Best Practices:

  • Ask after positive moment (completed task, achievement)
  • Don't ask on first use
  • Don't ask immediately after crash
  • Limit frequency (once per version or 30+ days)
  • Use native review dialogs

Timing Triggers:

  • After completing onboarding successfully
  • After achieving a goal/milestone
  • After using app X times
  • After positive feedback/emoji selection
  • After feature discovery moments

iOS SKStoreReviewController

code
Limits: 3 prompts per 365-day period
Best practice: Let Apple decide when to show

Google In-App Review API

code
Limits: Quota managed by Google
Best practice: Request after positive interactions

Responding to Reviews

Positive Reviews (4-5 stars)

code
Template:
"Thank you [Name] for your kind words! We're glad [specific mention
from their review]. Your feedback motivates our team. Enjoy using
[App Name]!"

Negative Reviews (1-2 stars)

code
Template:
"Hi [Name], we're sorry to hear about your experience with [issue].
We'd love to help resolve this. Please contact us at [support email]
with details, and our team will assist you directly. We're committed
to making [App Name] better."

Response Best Practices

  • Respond within 24-48 hours
  • Personalize each response
  • Address specific issues mentioned
  • Provide solution path (email, help center)
  • Update response if issue is resolved
  • Don't argue or be defensive
  • Thank users for feedback (even negative)

Localization

Priority Markets

MarketStoreLanguage
United StatesBothEnglish (US)
United KingdomBothEnglish (UK)
GermanyBothGerman
FranceBothFrench
JapanBothJapanese
South KoreaBothKorean
ChinaiOS onlySimplified Chinese
BrazilBothPortuguese (BR)
SpainBothSpanish (ES)
MexicoBothSpanish (MX)

Localization Elements

ElementLocalize?Notes
App NameOptionalConsider local keywords
SubtitleYesInclude local keywords
Keywords (iOS)YesResearch local search terms
Short DescriptionYesLocal keywords crucial
Full DescriptionYesFull translation + local keywords
ScreenshotsYesTranslate text, consider cultural elements
VideoOptionalSubtitles or voice-over
What's NewYesShows localized text

Keyword Research by Market

Process:

  1. Identify top competitors in market
  2. Analyze their keywords
  3. Research local search behavior
  4. Validate with native speakers
  5. Test and iterate

Cultural Considerations:

  • Different features may resonate
  • Visual preferences vary
  • Pricing expectations differ
  • Review styles vary by culture

A/B Testing

Google Play Experiments

Testable Elements:

  • App icon
  • Feature graphic
  • Screenshots
  • Short description
  • Full description

Setup:

  1. Create variant in Play Console
  2. Set traffic allocation (50/50 recommended)
  3. Run for statistically significant period
  4. Measure install conversion rate
  5. Apply winner

iOS Product Page Optimization

Testable Elements (up to 3 treatments):

  • App icon
  • Screenshots
  • App preview videos

Setup:

  1. Create treatments in App Store Connect
  2. Set traffic allocation
  3. Run test (minimum 7 days)
  4. Review results
  5. Apply best performer

Test Ideas

ElementVariation Ideas
IconColor scheme, character focus, abstract vs literal
Screenshot 1Different value props, with/without device frame
Screenshot OrderFeature priority, benefit focus
DescriptionDifferent hooks, feature emphasis
Short DescriptionBenefit vs feature focus, CTA variations

ASO Audit Checklist

Metadata

  • App title uses full 30 characters
  • Primary keyword in title
  • Subtitle (iOS) optimized with secondary keywords
  • Short description (Android) keyword-rich
  • Full description comprehensive and formatted
  • Keywords field (iOS) fully utilized, no duplicates
  • All locales have translated metadata

Visual Assets

  • All screenshot slots filled
  • Screenshots have compelling captions
  • First screenshot shows main value prop
  • Consistent design across screenshots
  • App preview video created (if applicable)
  • Feature graphic (Android) optimized
  • App icon distinctive and recognizable

Ratings & Reviews

  • Overall rating above 4.0
  • Recent reviews are positive
  • Review response strategy in place
  • In-app review prompt implemented
  • Negative reviews addressed promptly

Competitive

  • Competitor keywords analyzed
  • Differentiation clear in listing
  • Category ranking tracked
  • Keyword rankings monitored

Updates

  • Regular update schedule (2-4 weeks)
  • What's New text optimized
  • Seasonal updates planned
  • Feature releases communicated

Tools & Resources

Keyword Research

  • App Annie / data.ai
  • Sensor Tower
  • AppTweak
  • Mobile Action
  • AppFollow

Analytics

  • App Store Connect (iOS)
  • Google Play Console (Android)
  • Firebase Analytics
  • Mixpanel / Amplitude

Competitor Analysis

  • SimilarWeb
  • Sensor Tower
  • App Annie
  • AppFollow

Review Management

  • AppFollow
  • Appbot
  • ReviewBot
  • App Store Connect / Play Console native

File References

  • references/keyword-research.md - Keyword research methodology
  • references/screenshot-specs.md - Screenshot specifications
  • checklists/aso-launch.md - New app launch checklist
  • checklists/aso-monthly.md - Monthly maintenance checklist