Asc Aso Audit
Audit App Store Connect listing fields against Apple ASO indexing and keyword-budget rules before you ship or refresh an iOS app page.
Overview
asc-aso-audit is an agent skill for the Launch phase that applies App Store ASO indexing and keyword-field rules when auditing App Store Connect listing metadata.
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-aso-auditWhat is this skill?
- Enforces indexing model: title, subtitle, and keyword field indexed; description and promotional text not indexed
- Keyword field rules: comma-separated with no spaces after commas; no duplicate words already in title/subtitle
- Cross-field Apple Full Text Search: single tokens across fields combine into more query matches than stuffed phrases
- Description guidance for conversion (keyword reflection) even though description is not indexed
- Documents June 2025 OCR indexing for screenshot captions (informational; not automated in this audit)
- Keyword field: comma-separated, no spaces after commas
- Indexed fields: title, subtitle, keyword field; not indexed: description, promotional text
Adoption & trust: 1.2k installs on skills.sh; 845 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are unsure which App Store fields affect search, how to pack the keyword field, or whether you are wasting characters duplicating title and subtitle tokens.
Who is it for?
Solo builders shipping or updating an iOS app listing who use ASC CLI workflows and want deterministic ASO rule checks.
Skip if: Google Play ASO, web-only SEO, or teams that need full creative/screenshot design review without ASC metadata context.
When should I use this skill?
User is editing or validating App Store Connect title, subtitle, keywords, or description against ASO rules, or running an ASC ASO audit.
What do I get? / Deliverables
You get rule-aligned metadata feedback—indexing, comma formatting, deduplication, and cross-field combo awareness—before you publish listing changes in App Store Connect.
- ASO rule violations report tied to documented checks
- Actionable fixes for keyword formatting and cross-field duplication
Recommended Skills
Journey fit
ASO metadata decisions are Launch work: they directly affect App Store search visibility and conversion at go-live or seasonal updates. The skill encodes App Store Optimization rules—indexed fields, keyword hygiene, cross-field combos—not general marketing copy or web SEO.
How it compares
Structured ASO rule checker for App Store fields, not a broad App Store marketing strategy playbook.
Common Questions / FAQ
Who is asc-aso-audit for?
Indie iOS developers and small teams preparing App Store Connect metadata who want automated checks against documented Apple ASO indexing and keyword rules.
When should I use asc-aso-audit?
In Launch (ASO) before submission or metadata refreshes—when you need to validate title, subtitle, keywords, and related conversion copy against indexing and keyword-field constraints.
Is asc-aso-audit safe to install?
Review the Security Audits panel on this Prism page; the skill references listing rules and CLI checks—confirm any ASC credentials and CLI access follow your secret-handling policy.
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