Android Aso

作者 appeeky3919d7c27402無授權條款2.1K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫2 天前更新

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.

僅含說明Marketing & Sales
AI 產生的概覽

指導 Google Play 商店商店資訊最佳化:中繼資料、關鍵字、精選圖片、評分與 A/B 測試。

功能
此技能提供 Google Play ASO 指引,涵蓋與 iOS 的差異,以及標題、簡短說明和完整說明的字元限制與索引規則。它會產出商店資訊草稿、關鍵字定位說明,以及附評分和前三項改進建議的 Play 商店 ASO 稽核。內容也涉及精選圖片需求、評分策略、Play 商店實驗和發布前搶先體驗。
適用情境
當使用者想要最佳化 Google Play 商店資訊時使用,包括標題、簡短說明、完整說明、關鍵字、評分或 Play 特有功能。適合提到 Google Play、Android、Play Console 或 Play Store ASO 的需求。若要做 iOS App Store 最佳化,此技能會指向其他技能。
執行需求
不含指令碼,僅為指示文件。它提到選用的 app-marketing-context.md 檔案、用於取得關鍵字資料的 Play Console 存取權,以及以範例 HTTP 請求形式呈現的 Appeeky 關鍵字工具 API 呼叫。

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

FactorGoogle PlayApple App Store
Keyword indexingTitle + 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
RatingsContinuous — never resetReset per version (can request reset)
A/B testingPlay Store Experiments (native)Product Page Optimization
Screenshots2–8 per languageUp to 10 per language
Feature graphicRequired (1024×500px)Not applicable
Algorithm signalsInstalls, engagement, ratings, keywordsKeyword match, ratings, conversions
Review indexingReviews and replies indexedNot indexed

Character Limits

FieldLimitIndexedWeight
Title30 chars✓Highest
Short description80 chars✓High
Full description4000 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=usGET /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

來源與署名

來源:appeeky/aso-skills位於skills/android-aso提交3919d7c

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架