plugins/seo/skills/aso-optimization/SKILL.md
Optimizes App Store and Google Play listings for maximum visibility and conversion, covering keyword optimization, screenshot design, icon testing, description writing, and A/B testing (PPO, Store Listing Experiments). Based on Advanced ASO Book by Phiture and AppTweak. Use when an app is not appearing in search results, has low impression-to-download conversion, planning app store listing optimization, creating/updating screenshots and icons, or launching a new app. Trigger phrases include "app store optimization", "ASO", "app keywords", "app screenshots". NOT for web SEO (use on-page-seo), in-app conversion optimization, or app review/ratings management.
npx skillsauth add petrogurcak/skills aso-optimizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
App Store Optimization (ASO) skill for maximizing app visibility and conversion in iOS App Store and Google Play. Based on the Advanced App Store Optimization Book by Phiture and AppTweak.
Philosophy:
ASO = SEO for apps
Visibility (keywords) + Conversion (creative assets) = Downloads
Unlike web SEO, you can A/B test everything.
Announce: "I'm using aso-optimization to improve your app store listing."
USE this skill:
DON'T use this skill:
on-page-seo instead)ASO has 4 interconnected layers:
┌─────────────────────────────────────────────────────────┐
│ 1. VISIBILITY LAYER │
│ How users FIND the app │
│ - Search (keywords) │
│ - Browse & Explore (categories, similar apps) │
│ - Featuring (editorial) │
│ - Store Ads (Apple Search Ads, Google UAC) │
├─────────────────────────────────────────────────────────┤
│ 2. CONVERSION LAYER │
│ How users DECIDE to download │
│ - Visual: Icon, Screenshots, Video │
│ - Text: Title, Subtitle, Description │
│ - Social: Ratings, Reviews │
│ - Technical: App size, update frequency │
├─────────────────────────────────────────────────────────┤
│ 3. TOOLS LAYER │
│ What you use to optimize │
│ - Keyword research: AppTweak, Sensor Tower, MobileAction│
│ - A/B testing: PPO (iOS), Store Listing Experiments │
│ - Analytics: App Store Connect, Google Play Console │
├─────────────────────────────────────────────────────────┤
│ 4. SUPPORTING INSIGHTS LAYER │
│ Context for decisions │
│ - Seasonality (holidays, events) │
│ - Organic uplift (correlation paid → organic) │
│ - Cannibalization (brand vs generic keywords) │
│ - Benchmarks (category averages) │
└─────────────────────────────────────────────────────────┘
Goal: Get found for the right search terms.
Sources for keywords:
Score each keyword on 3 metrics:
| Metric | How to Measure | Weight | | -------------- | -------------------------------------------------- | -------- | | Volume | Apple Search Popularity (5-100, exponential scale) | HIGH | | Relevance | Manual score 0-5 (is this what our app does?) | CRITICAL | | Difficulty | Analyze top 10 results, ASO tool scores | MEDIUM |
Selection Formula:
Search Term Value = Volume × Relevance × (Max Competition / Your Competition Score)
Rule: Relevance is CRITICAL. Ranking for irrelevant keywords hurts conversion and wastes indexing slots.
iOS App Store:
| Field | Limit | Weight | Tactics | | ----------------- | --------- | ----------- | ---------------------------------- | | Title | 30 chars | HIGHEST | Primary keyword + brand | | Subtitle | 30 chars | HIGH | Secondary keywords + value prop | | Keyword Field | 100 chars | HIGH | Hidden, comma-separated, NO spaces | | Promotional Text | 170 chars | NOT INDEXED | For announcements only | | Description | Unlimited | NOT INDEXED | For conversion, not keywords |
iOS Keyword Field Tactics:
fitness,sport,běh not fitness, sport, běhGoogle Play:
| Field | Limit | Weight | Tactics | | --------------------- | ---------- | ------- | ---------------------------------------- | | Title | 30 chars | HIGHEST | Primary keyword + brand | | Short Description | 80 chars | HIGH | Keywords + CTA | | Long Description | 4000 chars | MEDIUM | Natural keyword density, HTML formatting |
Google Play Tactics:
<b>bold</b>, bullet pointsGoal: Convert impressions into downloads.
┌────────────┐
│ 1. Research │ ──► Look inside (analytics), outside (competitors), up (seasonality)
└─────┬──────┘
▼
┌────────────┐
│ 2. Hypothesize │ ──► "Adding social proof to first screenshot will increase trust"
└─────┬──────┘
▼
┌────────────┐
│ 3. Prioritize │ ──► RICE model: Reach × Impact × Confidence / Effort
└─────┬──────┘
▼
┌────────────┐
│ 4. Create │ ──► Design assets based on hypothesis
└─────┬──────┘
▼
┌────────────┐
│ 5. Test │ ──► A/B test (PPO, Store Listing Experiments)
└─────┬──────┘
▼
┌────────────┐
│ 6. Measure │ ──► Track conversion rate, organic uplift
└─────┴──────┘
│
└──────► Repeat
Apply these 3 psychological layers to all creative assets:
P - Persuasion (Cialdini Principles)
| Principle | App Store Application | | ---------------- | ------------------------------------------- | | Authority | Awards, press mentions, "Featured by Apple" | | Social Proof | "10M+ downloads", user testimonials | | Scarcity | "Limited offer", seasonal content | | Reciprocity | Free features highlighted | | Consistency | Design matches brand expectations | | Liking | Relatable screenshots, friendly tone |
E - Emotion
| Emotion | How to Trigger | | --------------- | ------------------------------------ | | Joy/Delight | Happy imagery, humor, achievements | | Aesthetic | Beautiful, polished design | | Fresh Start | "New you", transformation messaging | | FOMO | What they're missing without the app | | Relief | Pain point solved |
T - Trust
| Trust Signal | Implementation | | ------------------- | ------------------------------ | | Privacy | "Your data stays on device" | | Quality Content | Recent screenshots, current UI | | Testimonials | Real user quotes | | Certifications | Security badges, compliance | | Design Quality | Professional, polished assets |
Critical Rules:
Screenshot Checklist:
Screenshot Structure (recommended):
Best Practices:
Icon Checklist:
iOS Requirements:
Video Checklist:
What you can test:
What you CANNOT test:
Setup:
Limitations:
What you can test:
Advantages over iOS:
Setup:
| Aspect | iOS App Store | Google Play | | -------------------------- | -------------------------- | ---------------------- | | Description indexed? | NO | YES | | Keyword field? | YES (100 chars, hidden) | NO | | A/B test descriptions? | NO | YES | | A/B test approval | Requires review | Instant | | Video format | App Preview (strict rules) | YouTube link | | Conversion tracking | Impressions → Downloads | Page views → Downloads | | HTML in description? | NO | YES |
| Metric | What it Measures | Target | | ---------------------- | --------------------------------- | --------------------------- | | Impressions | How often app appears | Volume indicator | | Product Page Views | Clicks to detail page | Interest indicator | | Conversion Rate | Views → Downloads | > 30% good, > 50% excellent | | Keyword Rankings | Position for target keywords | Top 10 for priority terms | | Organic Uplift | Organic growth after optimization | 10-30% typical |
| Purpose | Tool | Notes | | ---------------------------- | ------------------------------- | ------------------------------------------- | | Keyword Research | AppTweak | Keyword Relevancy Score, accurate estimates | | Keyword Research | Sensor Tower | Competition alerts | | Competitor Analysis | Asodesk | Organic attribution | | A/B Testing (pre-launch) | SplitMetrics, Storemaven | Fake landing pages | | Analytics | App Store Connect, Play Console | Native, free |
Keyword Optimization:
Screenshot Optimization:
A/B Testing:
General:
| Skill | When to Use Together |
| ------------------ | -------------------------------------------- |
| product-copy | Writing App Store descriptions |
| keyword-research | Initial keyword discovery (adapt for mobile) |
| on-page-seo | Cross-reference web SEO keywords |
| ux-optimization | Screenshot UX principles |
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).