keyword-research
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
What this skill does
# Keyword Research You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy. ## Initial Assessment 1. Check for `app-marketing-context.md` — read it for app context, competitors, and goals 2. Ask for the **App ID** (to understand current rankings) 3. Ask for **target country** (default: US) 4. Ask for **seed keywords** — 3-5 words that describe the app's core function 5. Ask about **intent**: Are they optimizing for downloads, revenue, or brand awareness? ## Research Process ### Phase 1: Seed Expansion Start with the user's seed keywords and expand using multiple methods: **Apple Search Suggestions** - Use each seed keyword to get autocomplete suggestions - Try variations: "[keyword] app", "[keyword] for [audience]", "best [keyword]" - Note long-tail suggestions — these often have lower competition **Competitor Keywords** - Pull keyword rankings for top 3-5 competitors - Identify keywords competitors rank for that the user doesn't - Look for keywords where competitors rank poorly (opportunity) **Category Analysis** - What keywords do top apps in the category target? - Are there category-specific terms the user is missing? **Synonym & Related Terms** - Generate synonyms and related terms for each seed keyword - Consider how users actually describe the problem (not the solution) - Think about misspellings and abbreviations users might search ### Phase 2: Keyword Evaluation For each keyword candidate, evaluate: | Signal | What to check | Why it matters | |--------|--------------|----------------| | **Search Volume** | Volume score (1-100) or traffic estimate | Higher volume = more potential impressions | | **Difficulty** | Competition score (1-100) | Lower difficulty = easier to rank | | **Relevance** | How closely it matches the app's function | Irrelevant traffic doesn't convert | | **Intent** | Is the searcher looking to download? | "how to edit photos" vs "photo editor app" | | **Current Rank** | Where the app currently ranks (if at all) | Easier to improve existing rank than start from zero | ### Phase 3: Opportunity Scoring Calculate an **Opportunity Score** for each keyword: ``` Opportunity = (Volume × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3) ``` Where: - Volume: 1-100 scale - Difficulty: 1-100 scale (inverted — lower difficulty = higher score) - Relevance: 1-100 scale (manual assessment) ### Phase 4: Keyword Grouping Group keywords into strategic buckets: **Primary Keywords (3-5)** - Highest opportunity score - Must appear in title or subtitle - These define your core positioning **Secondary Keywords (5-10)** - Good opportunity but lower priority - Target in subtitle and keyword field - May rotate based on performance **Long-tail Keywords (10-20)** - Lower volume but very specific intent - Fill remaining keyword field space - Often easier to rank for **Aspirational Keywords (3-5)** - High volume, high difficulty - Long-term targets as the app grows - Track but don't sacrifice primary keywords for these ## Output Format ### Keyword Research Report **Summary:** - Total keywords analyzed: [N] - High-opportunity keywords found: [N] - Estimated total monthly search volume: [N] **Top Keywords by Opportunity:** | Keyword | Volume | Difficulty | Relevance | Opportunity | Current Rank | Action | |---------|--------|------------|-----------|-------------|--------------|--------| | [keyword] | [1-100] | [1-100] | [1-100] | [score] | [rank or —] | Primary | **Keyword Strategy:** ``` Title (30 chars): [primary keyword 1] + [primary keyword 2] Subtitle (30 chars): [secondary keywords] Keyword Field (100): [remaining keywords, comma-separated] ``` **Competitor Keyword Gap:** | Keyword | Your Rank | Competitor 1 | Competitor 2 | Competitor 3 | Gap? | |---------|-----------|-------------|-------------|-------------|------| **Recommendations:** 1. Immediate changes to make 2. Keywords to start tracking 3. Content/feature opportunities based on keyword demand ## Tips for the User - **Don't repeat keywords** across title, subtitle, and keyword field — Apple indexes each field separately - **Use singular forms** — Apple automatically indexes both singular and plural - **No spaces after commas** in the keyword field — save characters - **Avoid "app" and category names** — Apple already knows your category - **Update quarterly** — Search trends change with seasons and culture - **Track weekly** — Monitor rank changes to measure impact ## Related Skills - `metadata-optimization` — Implement the keyword strategy into actual metadata - `aso-audit` — Broader audit that includes keyword performance - `competitor-analysis` — Deep dive into competitor keyword strategies - `localization` — Keyword research for international markets
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.