Asc Aso Audit
Audit App Store metadata against ASC indexing and keyword-field rules before you submit or refresh a listing.
Overview
asc-aso-audit is an agent skill for the Launch phase that checks App Store listing metadata against ASC indexing and keyword-field rules.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-aso-auditWhat is this skill?
- Enforces rules that title, subtitle, and keyword field are indexed while description and promo text are conversion-only
- Keyword-field hygiene: comma-separated with no spaces after commas and no duplicate words from title/subtitle
- Cross-field combo guidance so single tokens in keywords combine with title/subtitle for Full Text Search
- Treats description keyword coverage as conversion leverage even though description is not indexed
- Documents June 2025 screenshot-caption OCR indexing as informational context beyond automated checks
Adoption & trust: 873 installs on skills.sh; 845 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship or update an App Store listing but are unsure which fields Apple indexes and how keyword budget is wasted across title, subtitle, and keywords.
Who is it for?
Indie iOS or Mac app builders validating metadata against documented ASC indexing and keyword rules immediately before submission or a major listing update.
Skip if: Teams that only need Google Play ASO, paid user-acquisition creative strategy, or automated screenshot-caption OCR verification without manual review.
When should I use this skill?
When auditing or preparing App Store Connect title, subtitle, keyword field, description, or promotional text against ASC indexing rules.
What do I get? / Deliverables
You get a rules-aligned ASO audit framing indexed fields, keyword formatting, cross-field search combos, and conversion-oriented description guidance before you publish metadata.
- ASO rules-aligned audit notes against indexing and keyword-field constraints
- Action list for keyword duplication, spacing, and cross-field combo opportunities
Recommended Skills
Journey fit
ASO audits belong on the Launch shelf because they govern App Store title, subtitle, keyword field, and conversion copy—not core product build. The subphase aso is the canonical home for store-listing optimization checks tied to Apple search indexing behavior.
How it compares
Use as a structured ASC rules checker rather than generic SEO blog advice that treats app store copy like web meta tags.
Common Questions / FAQ
Who is asc-aso-audit for?
Solo and indie mobile app builders who manage their own App Store Connect listings and want agent-guided checks against Apple indexing and keyword-field conventions.
When should I use asc-aso-audit?
Use it in Launch (aso) when refreshing keywords, rewriting subtitle or title, or pre-submit review; it is phase-specific to store listing optimization, not general web SEO.
Is asc-aso-audit safe to install?
Review the Security Audits panel on this Prism page for install counts, license, and any published audit results before adding the skill to your agent workflow.
SKILL.md
READMESKILL.md - Asc Aso Audit
# ASO Rules Reference Rules enforced by the asc-aso-audit skill. Each rule links to the check that tests it. ## Indexing Rules - **Title, subtitle, and keyword field are indexed** for App Store search. - **Description and promotional text are NOT indexed.** Description is for conversion (users see search terms reflected → higher download rate); promotional text is for seasonal messaging. - **Description keyword coverage still matters** — while not indexed, descriptions that naturally include keyword terms improve conversion rate, which indirectly boosts search rankings. - **Screenshot captions are OCR-indexed** (since June 2025 algorithm update). Use high-value keywords in caption text. *(Informational — not checked by this audit.)* - **Apple Full Text Search combines words across title + subtitle + keywords.** Single words enable more combinations than multi-word phrases. Example: "quran" + "recitation" in separate fields still matches "quran recitation". - **Cross-field combo optimization:** When adding keywords, consider what search queries they enable in combination with words already in title/subtitle. Example: adding "holy" to keywords when "Quran" is in subtitle enables the search "holy quran". ## Keyword Field Rules - **Comma-separated, no spaces after commas.** Spaces waste characters. `quran,recitation` not `quran, recitation`. - **Do not duplicate words already in title or subtitle.** Apple indexes all three fields together; repeating a word wastes keyword budget. - **Do not use the app name in keywords.** It is already indexed. - **Avoid plurals if the singular is already present** — Apple handles stemming. - **Prefer single words over multi-word phrases** — single words enable more cross-field combinations and use fewer characters. - **Always validate with popularity data** — never guess keyword value. Use Astro MCP or similar tools to check popularity scores before making swaps. ## Character Limits | Field | Limit | |-------|-------| | Name | 30 | | Subtitle | 30 | | Keywords | 100 | | Description | 4,000 | | What's New | 4,000 | | Promotional Text | 170 | ## Localization Rules - **Localize keywords per market** — do not just translate your primary keywords. Research what users in each locale actually search for. - **English (US) keywords may carry into other English-speaking storefronts** but dedicated localization always outperforms. - **Identical keyword fields across locales** usually indicates untranslated/unlocalized metadata. - **Track keywords in each locale's store** — keyword popularity varies dramatically across territories. A keyword with 70 popularity in the US store may have 5 popularity in France. Use Astro `add_keywords` to set up tracking per store before analyzing. - **Use competitor analysis per store** — top competitors differ by market. Run `extract_competitors_keywords` with locale-relevant competitor apps. ## Non-Latin Script Rules - **Arabic ال-prefix:** Apple likely normalizes the definite article ال. Treat "القرآن" (with ال) and "قرآن" (without) as probable duplicates when checking subtitle/keyword overlap. - **Arabic hamza variants:** Users commonly search without hamza diacritics. "قران" (no hamza) and "قرآن" (with hamza) target different search queries — both may be worth including. - **Chinese tokenization:** Chinese text has no word-separating spaces. Subtitle tokens are separated by `、` (enumeration comma) or `，` (full comma). Do not use whitespace tokenization for Chinese metadata. - **Cyrillic transliteration:** Including the Latin spelling of terms (e.g., "quran" in a Russian keyword field) targets users who search in Latin script on Cyrillic storefronts. ## Utilization Guidelines - **Keyword field:** aim for 90%+ character usage (90+ of 100 chars). - **Subtitle:** aim for 65%+ character usage (20+ of 30 chars). Short subtitles waste indexing opportunity. - **Name:** balance branding with keyword inclusion. --- name: asc-aso-audit description: Run an offline ASO a