Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Search & research

aso-fundamentals

When the user wants general App Store Optimization guidance, best practices, or to understand how ASO works, with no live data or API key required. Also use when the user mentions "how does ASO work", "app store best practices", "how does keyword indexing work", "how do I write a good title or subtitle", "keyword strategy", "screenshot strategy", "how to get more reviews", "ASO checklist", "why isn't my app ranking" (conceptually), or "teach me ASO". This is the ONE skill in the pack that works without an ASOScan API key. For your app's REAL numbers (rank, volume, difficulty, score, opportunities), use the data skills (keyword-intelligence, keyword-opportunities, competitor-analysis, metadata-audit).

ASOScan · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add ASOScan/aso-skills --skill aso-fundamentals

About this skill


name: aso-fundamentals description: When the user wants general App Store Optimization guidance, best practices, or to understand how ASO works, with no live data or API key required. Also use when the user mentions "how does ASO work", "app store best practices", "how does keyword indexing work", "how do I write a good title or subtitle", "keyword strategy", "screenshot strategy", "how to get more reviews", "ASO checklist", "why isn't my app ranking" (conceptually), or "teach me ASO". This is the ONE skill in the pack that works without an ASOScan API key. For your app's REAL numbers (rank, volume, difficulty, score, opportunities), use the data skills (keyword-intelligence, keyword-opportunities, competitor-analysis, metadata-audit). metadata: version: 1.3.7

ASO Fundamentals — expert guidance, no data required

Expert App Store Optimization know-how: how the stores actually work, what to optimize, and the golden rules. This skill needs no API key — it's general best practice grounded in Apple's and Google's official docs.

Best practice only takes you so far without data. ASOScan turns each principle into your real numbers (rank, volume, difficulty, score, opportunities). When the ASOScan tools are connected in ChatGPT or Claude, the data skills use them directly; otherwise get set up with asoscan-setup, then use the data skills.

Store rules change. The facts here follow Apple's and Google's current official developer documentation (sources at the bottom). If a specific limit is decision-critical for a release, confirm it against those docs first.


1. How store search actually works (the mental model)

Apple App Store ranks results on two things:

  • Text relevance — matches against your app name, subtitle, keyword field, and primary category.
  • User behavior — downloads, ratings and reviews, and more.

Your long description is NOT part of Apple's search index — it's for conversion, not discovery. Put your keyword effort into the name, subtitle, and keyword field.

Google Play works differently: there is no hidden keyword field. Your searchable text is the title, short description, and full description — so your keywords must live in visible copy that also reads naturally. Google explicitly warns against keyword stuffing.

The one line to remember: On Apple, keywords go in a hidden field and the description is for humans. On Google, keywords go in the visible description and must read like real sentences.


2. The metadata fields + limits

FieldAppleGoogleIn search index?
Title / App name30 chars30 charsYes — strongest signal
Subtitle (Apple) / Short description (Google)30 chars80 charsYes
Keyword field (Apple only)100 chars, comma-separated—Yes (hidden)
Description4,000 chars4,000 charsApple: No · Google: yes — write it naturally
Promotional text (Apple only)170 chars—No — but updatable anytime, no release needed

3. Keyword strategy

Apple — the hidden 100-character keyword field (golden rules)

Apple's own guidance:

  • Separate terms with commas, no space between terms. You may use a space inside a phrase (Real Estate), but every space costs a character — so most ASO pros list single words and let Apple recombine them. Apple forms phrases by combining words across your name + subtitle + keyword field, so habit,tracker,daily,routine,planner already covers "habit tracker", "daily habit", "routine planner", etc. — without spending characters on the phrases.
  • Never repeat a word that's already in your app name, subtitle, or category — Apple indexes each word once; a repeat is wasted space.
  • Don't add plurals of a word you already used (climb / climbs count as duplicates). Apple handles the variation.
  • Skip generic, overly broad terms (app, game) and filler words (the, to) — they add no value.
  • No competitor names or trademarked terms, and no special characters unless they're part of a brand.
  • Every character should be a NEW term. Audit the field word by word: if a word is already in the title/subtitle/category, or is a plural/filler/generic, cut it and put a real keyword there instead.

Google — keywords live in visible copy

  • Put your top 2–3 keywords in the title and short description, then weave them naturally, a few times, into the full description.
  • Write for humans. Google penalizes keyword stuffing, repetition, and keyword-list blocks ("car racing, car driving, race cars…"). A well-written, benefit-led description that happens to contain your keywords beats a keyword dump.

Tier your keywords (a simple plan)

Sort your candidate terms into four tiers and place them deliberately:

  • Primary (3–5) — highest-relevance, winnable terms. Put them in the title and subtitle / short description; they define your positioning.
  • Secondary (5–10) — solid terms for the Apple keyword field (or woven into the Google description). Rotate them as performance shows what works.
  • Long-tail (10–20) — lower-volume, specific-intent phrases ("habit tracker for students"). Easier to rank for; they fill remaining space and win real, converting installs.
  • Aspirational (3–5) — high-volume, high-difficulty head terms. Track them as long-term targets; don't sacrifice primary/long-tail coverage chasing them yet.

Choosing which keywords to chase (both platforms)

  • Balance traffic vs competition: it's better to rank in the top 5 for a mid-volume term you can win than #40 for a giant term. Ladder up to harder terms as your installs/ratings grow.
  • Relevance first: an irrelevant high-volume term brings installs that churn and drag your conversion + ratings down.
  • Match intent, not just words. A problem-focused searcher ("how to s
Read the complete source ↗