
Android Aso
- 1.7k installs
- 1.7k repo stars
- Updated July 27, 2026
- eronred/aso-skills
android-aso is an agent skill that 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 menti
About
android-aso is an agent skill from eronred/aso-skills that 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 pla. # 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 | |--------|------------|----------------| | * Developers invoke android-aso during ship/testing work for testing & qa tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments.
- | 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 |
Android Aso by the numbers
- 1,697 all-time installs (skills.sh)
- +70 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #449 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
android-aso capabilities & compatibility
- Capabilities
- | factor | google play | apple app store | · | | | | · | **keyword indexing** | title + short desc + fu · | **hidden keyword field** | ✗ none | ✓ 100 char · | **description indexed** | ✓ full 4000 chars |
- Use cases
- orchestration
What android-aso says it does
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?**
npx skills add https://github.com/eronred/aso-skills --skill android-asoAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.7k |
|---|---|
| repo stars | ★ 1.7k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | eronred/aso-skills ↗ |
What it does
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 Pla
Who is it for?
Developers working on testing & qa during ship tasks.
Skip if: Tasks outside Testing & QA scope described in SKILL.md.
When should I use this skill?
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 Pla
What you get
Completed testing & qa workflow aligned with SKILL.md steps.
- Optimized listing copy
- Keyword strategy
- Play Console metadata recommendations
By the numbers
- Documented at metadata version 1.0.0
Files
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:
GET /v1/keywords/metrics?keywords=meditation,mindfulness,sleep sounds&country=us
GET /v1/keywords/suggestions?term=meditation&country=usPlay-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 ratingrating-prompt-strategy— In-App Review API timing and strategyab-test-store-listing— Play Experiments methodologylocalization— Per-language listing optimization
Related skills
How it compares
Use android-aso for Google Play indexed descriptions; use iOS-focused aso-audit skills when optimizing Apple App Store metadata.
FAQ
What does android-aso do?
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 Pla
When should I use android-aso?
During ship testing work for testing & qa.
Is android-aso safe to install?
Review the Security Audits panel on this listing before production use.