App Store Optimization (ASO) Skill
Comprehensive optimization for iOS App Store and Google Play Store visibility.
Quick Reference
| Element | iOS App Store | Google Play Store |
|---|---|---|
| App Name | 30 characters | 30 characters |
| Subtitle | 30 characters | N/A |
| Short Description | N/A | 80 characters |
| Full Description | 4,000 characters | 4,000 characters |
| Keywords | 100 characters (hidden) | In description (indexed) |
| Screenshots | Up to 10 | Up to 8 |
| Preview Video | Up to 3 (30s each) | 1 (30s-2min) |
| Promotional Text | 170 characters | N/A |
ASO Fundamentals
How App Store Algorithms Work
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
| Factor | iOS Weight | Android Weight |
|---|---|---|
| App Name/Title | Very High | Very High |
| Keyword Field | Very High | N/A |
| Description | Low | High |
| Downloads | High | High |
| Rating/Reviews | High | High |
| Update Frequency | Medium | Medium |
| Engagement | Medium | High |
| Backlinks | N/A | Low |
iOS App Store Optimization
App Name (30 characters)
Strategy:
- •Brand name + primary keyword
- •Most important ranking factor
- •Visible in search results
Format:
[Brand Name] - [Primary Keyword] [Brand Name]: [Benefit Statement]
Examples:
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:
[Secondary Keyword] + [Benefit/Feature]
Examples:
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:
keyword1,keyword2,keyword3,keyword4,misspelling,variant
Research Process:
- •Brainstorm seed keywords
- •Analyze competitor keywords (tools: AppTweak, Sensor Tower)
- •Check search volume estimates
- •Assess difficulty/competition
- •Select mix of high-volume and long-tail
Prioritization:
| Priority | Keyword Type | Example |
|---|---|---|
| 1 | High volume, medium competition | "meditation" |
| 2 | Medium volume, low competition | "sleep sounds" |
| 3 | Long-tail specific | "anxiety relief app" |
| 4 | Misspellings | "mediation" |
Full Description (4,000 characters)
Note: iOS description is NOT indexed for search. Focus on conversion.
Structure:
[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:
"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
| Device | Size (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:
- •Hero shot with main value proposition
- •Key feature 1
- •Key feature 2
- •Social proof / testimonials
- •Key feature 3
- •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:
[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:
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:
[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:
[Action verb] + [benefit] + [keyword] + [differentiator]
Examples:
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
[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
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
| Type | Size (pixels) | Ratio |
|---|---|---|
| Phone | 1080 x 1920 | 16: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:
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
| Rating | Impact |
|---|---|
| 4.5+ | Significantly higher conversion |
| 4.0-4.4 | Competitive |
| 3.5-3.9 | Negative impact begins |
| Below 3.5 | Major 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
Limits: 3 prompts per 365-day period Best practice: Let Apple decide when to show
Google In-App Review API
Limits: Quota managed by Google Best practice: Request after positive interactions
Responding to Reviews
Positive Reviews (4-5 stars)
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)
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
| Market | Store | Language |
|---|---|---|
| United States | Both | English (US) |
| United Kingdom | Both | English (UK) |
| Germany | Both | German |
| France | Both | French |
| Japan | Both | Japanese |
| South Korea | Both | Korean |
| China | iOS only | Simplified Chinese |
| Brazil | Both | Portuguese (BR) |
| Spain | Both | Spanish (ES) |
| Mexico | Both | Spanish (MX) |
Localization Elements
| Element | Localize? | Notes |
|---|---|---|
| App Name | Optional | Consider local keywords |
| Subtitle | Yes | Include local keywords |
| Keywords (iOS) | Yes | Research local search terms |
| Short Description | Yes | Local keywords crucial |
| Full Description | Yes | Full translation + local keywords |
| Screenshots | Yes | Translate text, consider cultural elements |
| Video | Optional | Subtitles or voice-over |
| What's New | Yes | Shows localized text |
Keyword Research by Market
Process:
- •Identify top competitors in market
- •Analyze their keywords
- •Research local search behavior
- •Validate with native speakers
- •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:
- •Create variant in Play Console
- •Set traffic allocation (50/50 recommended)
- •Run for statistically significant period
- •Measure install conversion rate
- •Apply winner
iOS Product Page Optimization
Testable Elements (up to 3 treatments):
- •App icon
- •Screenshots
- •App preview videos
Setup:
- •Create treatments in App Store Connect
- •Set traffic allocation
- •Run test (minimum 7 days)
- •Review results
- •Apply best performer
Test Ideas
| Element | Variation Ideas |
|---|---|
| Icon | Color scheme, character focus, abstract vs literal |
| Screenshot 1 | Different value props, with/without device frame |
| Screenshot Order | Feature priority, benefit focus |
| Description | Different hooks, feature emphasis |
| Short Description | Benefit 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