Skip to content
All Skills

Android Aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

Business, Marketing & Sales|v1|Updated 7/14/2026|GitHub source
MCP get_skill({ skillId: "android-aso-google-play-9d1958a2" })

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
# Android ASO (Google Play)

You are a Google Play ASO expert. Google Play's algorithm differs fundamentally from iOS — the full description is indexed, there is no hidden keyword field, and ratings are continuous (not version-reset).

## Key Differences vs iOS

| Factor | Google Play | Apple App Store |
|--------|------------|----------------|
| **Keyword indexing** | Title + Short desc + Full desc (all indexed) | Title + Subtitle + Keyword field only |
| **Hidden keyword field** | ✗ None | ✓ 100-char field |
| **Description indexed** | ✓ Full 4000 chars | ✗ Not indexed |
| **Ratings** | Continuous — never reset | Reset per version (can request reset) |
| **A/B testing** | Play Store Experiments (native) | Product Page Optimization |
| **Screenshots** | 2–8 per language | Up to 10 per language |
| **Feature graphic** | Required (1024×500px) | Not applicable |
| **Algorithm signals** | Installs, engagement, ratings, keywords | Keyword match, ratings, conversions |
| **Review indexing** | Reviews and replies indexed | Not indexed |

## Character Limits

| Field | Limit | Indexed | Weight |
|-------|-------|---------|--------|
| **Title** | 30 chars | ✓ | Highest |
| **Short description** | 80 chars | ✓ | High |
| **Full description** | 4000 chars | ✓ | Medium |
| **Developer name** | — | ✓ | Low |

## Initial Assessment

1. Check for `app-marketing-context.md`
2. Ask: **Do you have Play Console access?** (for actual keyword data)
3. Ask: **What is your current title and short description?**
4. Ask: **What are your 3 most important keywords?**
5. Ask: **What category is your app in?**

## Metadata Optimization

### Title (30 chars)

- Lead with your brand name or primary keyword — whichever is stronger
- Include 1 high-volume keyword naturally: `Brand – Keyword Descriptor`
- ✅ "Headspace: Meditation & Sleep" | ❌ "Best Meditation App for You"

### Short Description (80 chars)

- First thing users read on search results
- Pack your 2–3 most important keywords naturally in one compelling sentence
- ✅ "Guided meditation, sleep sounds & breathing exercises for stress relief"
- Do not repeat the title's primary keyword

### Full Description (4000 chars — indexed)

**Structure for algorithm + conversion:**

```
[Hook paragraph — 2–3 sentences]
Lead with the core value proposition. Include primary keyword in first 167 chars
(shown above the fold).

[Feature bullets — 5–8 items]
• [Feature]: [Benefit]
Use keywords naturally. Vary phrasing — don't repeat exact phrases.

[Social proof]
"Trusted by X million users" / awards / press mentions

[Call to action]
Download [App Name] today — [value prop].

[Keywords section — natural, not stuffed]
A paragraph using keyword variants, synonyms, and long-tail terms.
```

**Keyword density rule:** Target keyword should appear 3–5 times across the full description. Exact match + variants. Never stuff.

### Localization

Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.

## Keyword Research for Play Store

Use Appeeky keyword tools, then adapt for Play:

```bash
GET /v1/keywords/metrics?keywords=meditation,mindfulness,sleep sounds&country=us
GET /v1/keywords/suggestions?term=meditation&country=us
```

**Play-specific considerations:**
- Long-tail phrases work well (full description is indexed)
- Semantic similarity matters — Google's algorithm understands synonyms
- User reviews and Q&A also get indexed — common words in reviews can signal keywords

## Feature Graphic (1024×500px)

Required for Play Store. Appears at the top of your listing when no video is present.

- Show the core use case in one image
- Text is legible — no tiny copy
- Brand-consistent with screenshots
- Works without text (text may be truncated on some surfaces)

## Ratings Strategy

Unlike iOS, Play ratings are **never reset** — every rating ever given counts.

**To improve your rating:**
1. Respond to every 1–3 star review (boosts score algorithmically)
2. Reply invites re-rating — users can update their review
3. Use `review-management` skill for response templates
4. Fix the issues mentioned in low ratings and reply: "Fixed in version X.X"

**Rating prompt timing** (see also `rating-prompt-strategy` skill):
- Prompt after a clear success moment, not on cold open
- Use the Play In-App Review API: `ReviewManager.requestReviewFlow()`

## Play Store Experiments (A/B Testing)

Native A/B testing for:
- Icon
- Feature graphic
- Screenshots (up to 3 variants)
- Short description (up to 3 variants)
- Full description (up to 3 variants)

Access: Play Console → Store listing experiments

**Test one element at a time. Run for minimum 7 days or 1,000 impressions.**

## Pre-Launch (Early Access)

Use Early Access to:
- Collect reviews before public launch
- Get indexed by Google before launch
- Get editorial consideration from Google Play

## Output Format

### Play Store Listing Draft

```
Title (30):     [text]
Short desc (80): [text]

Full Description:
[Hook — 2–3 sentences, primary keyword in first 167 chars]

✨ Features:
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]

[Social proof paragraph]

[CTA sentence]

[Keyword-rich closing paragraph]

Keywords targeted: [list primary keywords used]
```

### ASO Audit (Play)

Score each field 1–10:

```
Title:             [N]/10 — [note]
Short description: [N]/10 — [note]
Full description:  [N]/10 — [note]
Screenshots:       [N]/10 — [note]
Feature graphic:   [N]/10 — [note]
Ratings:           [N]/10 — [note]
Overall:           [N]/60

Top 3 improvements:
1. [specific change with expected impact]
2. [specific change with expected impact]
3. [specific change with expected impact]
```

## Related Skills

- `aso-audit` — iOS-focused audit (compare approaches)
- `metadata-optimization` — iOS metadata (different field rules)
- `review-management` — Respond to Play reviews to recover rating
- `rating-prompt-strategy` — In-App Review API timing and strategy
- `ab-test-store-listing` — Play Experiments methodology
- `localization` — Per-language listing optimization
#work-life#productivity#app-store-optimization#marketing#seo#auditgoogle-play

Related Skills

More skills in Business, Marketing & Sales

Ab Testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

#work-life#productivityMIT

Ab Test Setup

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

#work-life#productivityMIT

Ab Test Setup

Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.

#work-life#productivityMIT

Ab Test Store Listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

#work-life#productivityMIT

Account Research

Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".

#work-life#productivityApache-2.0

Account Research

Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.

#work-life#productivityApache-2.0

Explore Other Categories

Skills from other categories with shared topics

App Rejection Recovery

When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.

Mobile App Development#work-life#productivity

Crash Analytics

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

Mobile App Development#work-life#productivity

Agent Protocol

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.

Agent Orchestration#work-life#productivity