app-store-optimization
Optimize mobile app listings for discovery and conversion in Apple App Store and Google Play. Use when tasks involve ASO keyword research, title and subtitle optimization, screenshot and preview video design, A/B testing store listings, review management, localization for international markets, tracking keyword rankings, or improving download conversion rates. Covers both iOS and Android store algorithms and best practices.
What this skill does
# App Store Optimization (ASO) ## Overview Optimize mobile app visibility and conversion in App Store and Google Play. Cover keyword research, metadata optimization, creative assets, ratings management, and localization. ## Instructions ### How store algorithms work **Apple App Store** indexes: App Name (30 chars, highest weight), Subtitle (30 chars), Keyword field (100 chars, hidden), In-App Purchase names, Developer name. Apple does NOT index the description for search. **Google Play** indexes: App Title (30 chars, highest weight), Short Description (80 chars), Long Description (4000 chars, 2-5% keyword density), Developer name, Package name. Google also factors engagement metrics: install velocity, retention, crash rate, uninstall rate. ### Keyword research 1. **Seed list**: Features, use cases, competitor names, problem words 2. **Expand**: Use autocomplete in both stores 3. **Validate**: Check volume and difficulty (AppTweak, Sensor Tower, AppFollow) 4. **Prioritize**: Score each on `volume × relevance / difficulty` 5. **Map**: Assign keywords to metadata fields by priority **Keyword placement:** ``` App Store (iOS): - App Name (30 chars): Top 2-3 keywords, natural reading - Subtitle (30 chars): Supporting keywords, value prop - Keyword field (100 chars): Everything else, no duplicates across fields - Comma-separated, no spaces. Singular OR plural (Apple matches both) - Don't include "app" or category name. Don't use competitor brands. Google Play: - Title (30 chars): Primary keyword + brand - Short Description (80 chars): Key features with keywords - Long Description (4000 chars): Natural usage, 2-5% density, repeat 3-5x ``` ### Store listing creative assets **Screenshots** are the single biggest conversion factor. Design principles: - First 3 screenshots visible without scrolling — strongest value props here - Each screenshot = one clear message (feature + benefit) - Large, readable text overlay - Sequence: Hero shot → Core feature → Unique differentiator → Secondary feature → Social proof **Preview video**: iOS 15-30s (autoplays muted), Android 30s-2min (YouTube). Start with the wow moment, no long intros. **Icon**: Recognizable at 16×16px, single focal element, avoid text, A/B test variations. ### A/B testing store listings **Google Play Experiments**: Test up to 5 variants (icon, screenshots, descriptions). Minimum 7 days, recommend 14 days. **Apple Product Page Optimization**: Test up to 3 treatments (icon, screenshots, preview video). Cannot test title/subtitle. 90-day limit. **Priority order**: Screenshots → Icon → Short description/subtitle → Preview video. ### Ratings and reviews Each 0.5-star increase improves conversion by 10-20%. Apps below 4.0 lose significant traffic. **In-app review prompts**: Use native review API. Trigger after positive actions (completed goal, saved money). Pre-qualify: ask "Are you enjoying [App]?" — if yes, show review; if no, route to feedback form. Max 3 times per year (iOS enforced). **Responding**: Reply to all negative reviews within 24-48 hours. Be specific about fixes. Never argue or be defensive. ### Localization Localizing metadata (not the app) is the fastest ASO win. High-impact locales: Spanish, Portuguese (Brazil), Japanese, German, French, Korean. Localization is NOT translation — research keywords in each locale separately. Direct translations often aren't what locals search for. ### Monitoring Track weekly: keyword rankings (top 10 with position changes), category ranking, impressions, page view → install rate (benchmark: 25-35%), impression → install rate (benchmark: 3-8%), Day 1 retention, crash rate, current rating and trend. ## Examples ### Optimize an iOS app listing for more downloads ```prompt Our meditation app "ZenFlow" has 2,000 daily downloads but a 22% conversion rate from page views. Current title: "ZenFlow". We rank for "meditation" (#45) and "sleep sounds" (#78). Optimize our App Store metadata — title, subtitle, and keyword field — to improve keyword rankings and conversion. Research what top competitors in the meditation category use. ``` ### Plan a localization strategy for Google Play ```prompt Our fitness app has 100K downloads in the US and we want to expand internationally. Identify the top 5 markets by opportunity (considering competition, ARPU, and mobile fitness trends), then create localized metadata for each — not direct translations, but locally researched keywords and culturally adapted screenshots. ``` ### Design a screenshot A/B test ```prompt Our productivity app's screenshots haven't been updated in 8 months and conversion is declining. Design 3 screenshot variants to A/B test on Google Play. Include the messaging strategy, visual approach, and success metrics for each variant. Our current conversion rate from page view to install is 28%. ``` ## Guidelines - Always deduplicate keywords across title, subtitle, and keyword field on iOS — Apple deduplicates automatically - Use singular or plural forms but not both on iOS (Apple matches both) - Never include competitor brand names in the keyword field — risk of rejection - Update screenshots and metadata at least every 3-6 months to avoid conversion decline - Always pre-qualify users before showing the native review prompt - Respond to negative reviews with specific fix information, never defensively - Track keyword rankings weekly and iterate metadata based on position changes
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".