metadata-optimization

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "metadata-optimization" with this command: npx skills add eronred/aso-skills/eronred-aso-skills-metadata-optimization

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

  1. Check for app-marketing-context.md — read it for positioning and target audience
  2. Ask for the App ID (to see current metadata)
  3. Ask for target keywords (or suggest running keyword-research first)
  4. Ask for platform (iOS / Android / Both)
  5. Ask for target country (default: US)

Platform-Specific Limits

Apple App Store (iOS)

FieldLimitIndexed for Search?Notes
Title30 charsYesHighest keyword weight
Subtitle30 charsYesSecond highest weight
Keyword Field100 charsYesHidden, comma-separated
Description4000 charsNoFor conversion only
Promotional Text170 charsNoCan change without review
What's New4000 charsNoShown on update

Google Play (Android)

FieldLimitIndexed for Search?Notes
Title30 charsYesHighest keyword weight
Short Description80 charsYesVisible on listing
Full Description4000 charsYesKeyword 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:

  1. Hook (first 3 lines) — This is all users see before "more". Make it count.
  2. Social proof — Awards, press mentions, user count, rating
  3. Key features — 4-6 bullet points with benefits, not just features
  4. How it works — Simple 3-step explanation
  5. Testimonial or review quote — Real user voice
  6. 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:

  1. Recommended version (primary recommendation)
  2. Alternative A (different keyword emphasis)
  3. Alternative B (different positioning angle)

Include for each:

  • Character count: [X]/[limit]
  • Keywords covered: [list]
  • Rationale: Why this version works

Keyword Coverage Matrix

KeywordTitleSubtitleKeyword FieldTotal Coverage
[kw1]Title
[kw2]Subtitle
[kw3]Keyword Field

Before/After Comparison

FieldCurrentRecommendedImprovement
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 keywords
  • aso-audit — Broader audit that includes metadata quality
  • localization — Adapt metadata for international markets
  • ab-test-store-listing — Test metadata variations
  • competitor-analysis — See how competitors write their metadata

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

aso-audit

No summary provided by upstream source.

Repository SourceNeeds Review
General

monetization-strategy

No summary provided by upstream source.

Repository SourceNeeds Review
General

app-analytics

No summary provided by upstream source.

Repository SourceNeeds Review