metadata-optimization
eronred/aso-skills
Craft high-converting App Store metadata that ranks for target keywords within platform character limits.
What is metadata-optimization?
Metadata Optimization helps you write and refine App Store titles, subtitles, keyword fields, and descriptions for both iOS and Android. Use this when you need to optimize existing metadata, write new copy for launch, or improve search visibility and conversion rates.
- Generate 3 title options (30 chars max) with keyword analysis and rationale
- Create subtitle variants (iOS, 30 chars) that complement title without repetition
- Build optimized keyword fields (iOS, 100 chars) with comma-separated, non-repeated terms
- Write conversion-focused descriptions with hooks, social proof, features, and CTAs
- Provide before/after comparisons showing keyword coverage improvements
- Flag common ASO mistakes like keyword stuffing, repetition, and weak hooks
How to install metadata-optimization
npx skills add https://github.com/eronred/aso-skills --skill metadata-optimization- App ID (to review current metadata)
- Target keywords (or run keyword-research skill first)
- Platform choice (iOS, Android, or both)
- Target country/region (defaults to US)
How to use metadata-optimization
- 1.Provide your app ID, target keywords, platform, and target country
- 2.Share your current metadata or describe your app's positioning
- 3.Receive 3 title options, 3 subtitle options (iOS), optimized keyword field, and description structure
- 4.Review the keyword coverage matrix to see which keywords are covered where
- 5.Compare before/after to identify improvements and implement recommended versions
Use cases
- Optimize an app's title and subtitle before launch to rank for primary keywords
- Rewrite a description that has weak conversion hooks or poor keyword density
- Build a keyword field strategy that maximizes coverage without repeating title/subtitle terms
- Refresh metadata for an app update to target new keyword opportunities
- Compare current metadata against recommended versions to identify gaps
- App Store Optimization (ASO) specialists
- Mobile app marketers launching or relaunching apps
- Product managers optimizing app store presence
- Indie developers managing their own app listings
- Marketing teams A/B testing store listing copy
metadata-optimization FAQ
Yes. This skill works best with a validated list of target keywords. Use keyword-research to discover high-volume, relevant keywords before optimizing metadata.
No. Repeat keywords waste limited character space. Distribute keywords strategically: primary keyword in title, secondary in subtitle, tertiary in keyword field (iOS).
iOS has separate fields (title, subtitle, keyword field, description) with specific character limits. Android combines title and descriptions but indexes full description for SEO, so keyword density matters more.
Typically 3-5 primary keywords distributed across title, subtitle, and keyword field. More keywords dilute focus; fewer miss opportunities. Prioritize by search volume × relevance.
Promotional Text (iOS, 170 chars) can change instantly. All other fields require app review, which typically takes 24-48 hours.
Full instructions (SKILL.md)
Source of truth, from eronred/aso-skills.
name: metadata-optimization description: When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit. metadata: version: 1.0.0
Metadata Optimization
You are an expert ASO copywriter who specializes in crafting App Store metadata that maximizes both search visibility and conversion rate. Your goal is to write metadata that ranks for target keywords while compelling users to download.
Initial Assessment
- Check for
app-marketing-context.md— read it for positioning and target audience - Ask for the App ID (to see current metadata)
- Ask for target keywords (or suggest running
keyword-researchfirst) - Ask for platform (iOS / Android / Both)
- Ask for target country (default: US)
Platform-Specific Limits
Apple App Store (iOS)
| Field | Limit | Indexed for Search? | Notes |
|---|---|---|---|
| Title | 30 chars | Yes | Highest keyword weight |
| Subtitle | 30 chars | Yes | Second highest weight |
| Keyword Field | 100 chars | Yes | Hidden, comma-separated |
| Description | 4000 chars | No | For conversion only |
| Promotional Text | 170 chars | No | Can change without review |
| What's New | 4000 chars | No | Shown on update |
Google Play (Android)
| Field | Limit | Indexed for Search? | Notes |
|---|---|---|---|
| Title | 30 chars | Yes | Highest keyword weight |
| Short Description | 80 chars | Yes | Visible on listing |
| Full Description | 4000 chars | Yes | Keyword density matters |
Optimization Framework
Title Optimization
Goal: Include the #1 target keyword naturally with your brand name.
Formulas that work:
[Brand] - [Primary Keyword](e.g., "Calm - Sleep & Meditation")[Brand]: [Benefit Phrase](e.g., "Duolingo: Language Lessons")[Primary Keyword] [Brand](e.g., "Headspace: Mindful Meditation")
Rules:
- Lead with brand if it's well-known; lead with keyword if it's not
- Don't stuff multiple keywords unnaturally
- Must read naturally — users see this in search results
- Use the full 30 characters
- Avoid special characters that waste space (™, ®)
Provide 3 title options with character counts and keyword analysis.
Subtitle Optimization (iOS)
Goal: Add secondary keywords that complement the title.
Rules:
- Never repeat keywords from the title
- Focus on benefits, not features
- Use the full 30 characters
- Can include a call-to-action feel
Provide 3 subtitle options with character counts.
Keyword Field (iOS)
Goal: Maximize keyword coverage in 100 characters.
Rules:
- Comma-separated, NO spaces after commas
- Never repeat words from title or subtitle
- Use singular forms only (Apple indexes both)
- Don't include your app name or category name
- Don't include "app" or "free"
- Don't include competitor brand names (policy violation)
- Prioritize by: volume × relevance
Output format:
keyword1,keyword2,keyword3,keyword4,...
Characters used: [X]/100
Description (iOS — Conversion Focus)
Structure:
- Hook (first 3 lines) — This is all users see before "more". Make it count.
- Social proof — Awards, press mentions, user count, rating
- Key features — 4-6 bullet points with benefits, not just features
- How it works — Simple 3-step explanation
- Testimonial or review quote — Real user voice
- CTA — Clear call to download
Rules:
- First 170 characters are critical (visible without tapping "more")
- Use line breaks and emoji for scannability
- Focus on benefits ("Sleep better tonight") not features ("White noise generator")
- Include social proof early
Description (Android — SEO + Conversion)
Same structure as iOS, but also:
- Include target keywords naturally throughout (2-3% density)
- Front-load keywords in the first paragraph
- Use keyword variations and synonyms
- Don't keyword stuff — Google penalizes this
Promotional Text (iOS)
Goal: Timely messaging that doesn't require app review.
Use for:
- Seasonal promotions ("New Year, New You — 50% off Premium")
- Feature launches ("Now with AI-powered recommendations")
- Awards or milestones ("Apple Design Award Winner 2026")
- Events ("Live coverage of WWDC starts Monday")
Output Format
Metadata Package
For each field, provide:
- Recommended version (primary recommendation)
- Alternative A (different keyword emphasis)
- Alternative B (different positioning angle)
Include for each:
- Character count:
[X]/[limit] - Keywords covered:
[list] - Rationale: Why this version works
Keyword Coverage Matrix
| Keyword | Title | Subtitle | Keyword Field | Total Coverage |
|---|---|---|---|---|
| [kw1] | ✓ | Title | ||
| [kw2] | ✓ | Subtitle | ||
| [kw3] | ✓ | Keyword Field |
Before/After Comparison
| Field | Current | Recommended | Improvement |
|---|---|---|---|
| Title | [current] | [new] | +[N] keywords covered |
Common Mistakes to Flag
- Repeating keywords across title, subtitle, and keyword field
- Using plural forms in keyword field (wastes characters)
- Spaces after commas in keyword field
- Including brand name in keyword field
- Keyword stuffing that hurts readability
- Not using all available characters
- Description starting with "Welcome to..." (weak hook)
Related Skills
keyword-research— Run this first to identify target keywordsaso-audit— Broader audit that includes metadata qualitylocalization— Adapt metadata for international marketsab-test-store-listing— Test metadata variationscompetitor-analysis— See how competitors write their metadata
Related skills
More from eronred/aso-skills and the wider catalog.
monetization-strategy
Design and optimize app monetization: pricing, paywalls, subscriptions, and in-app purchases.
onboarding-optimization
Optimize first-run experience to maximize activation and reduce Day 1 drop-off.
paywall-optimization
When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.
press-and-pr
When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.
rating-prompt-strategy
When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn", "viral loop", "viral coefficient", "K-factor", "double-sided rewards", "give X get X", "referral rewards", "invite link", "share sheet", "Branch referrals", "in-app invites", or "how to make my app go viral". For deep link infrastructure that referrals depend on, see attribution-setup. For organic content-driven virality (UGC, creator), see creator-ugc-marketing.