appeeky/aso-skills

seasonal-aso

When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/appeeky/aso-skills --skill seasonal-aso

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Seasonal ASO

You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments.

Key Principle

Seasonal rankings are competitive and time-sensitive. Metadata takes 1–3 days to index. Plan changes 2 weeks before the event; revert 3–5 days after peak.

Seasonal Calendar (iOS — US)

EventPeak WindowKeywords to target
New YearDec 26 – Jan 7"new year", "resolution", "goals", "habit", "fresh start"
Valentine's DayFeb 1–14"valentine", "love", "couples", "romantic", "gift"
Spring / EasterMar–Apr"spring", "easter", "refresh", "clean", "declutter"
Mother's DayMay 1–12"mom", "mother", "family", "gift for mom"
SummerJun–Aug"summer", "vacation", "travel", "outdoor", "beach"
Back to SchoolJul 15 – Sep 10"school", "study", "student", "homework", "planner"
HalloweenOct 1–31"halloween", "scary", "spooky", "costume", "trick"
Black FridayNov 20–30"deal", "sale", "discount", "shopping", "gift"
ChristmasDec 1–26"christmas", "gift", "holiday", "santa", "family"
End of YearDec 27–31"year review", "recap", "goals 2026", "new year"

Workflow

Step 1 — Identify Relevant Event

  1. Check for app-marketing-context.md
  2. Ask: Which event or season are you targeting?
  3. Ask: What does your app do? (to assess keyword relevance)
  4. Determine if the event is a good fit — not every seasonal moment applies

Step 2 — Research Seasonal Keywords

Use Appeeky to find volume on seasonal terms:

bash
GET /v1/keywords/metrics?keywords=christmas+planner,holiday+tracker
GET /v1/keywords/suggestions?term=christmas&country=us
GET /v1/keywords/trending?country=us&days=7

Filter by:

  • Volume spike (compare to baseline 30 days prior)
  • Difficulty < 60 preferred (seasonal keywords are crowded)
  • Relevance to your app's core function

Step 3 — Plan Metadata Changes

Keyword field (100 chars, iOS):

  • Swap out low-performing keywords for seasonal terms
  • Add 2–4 seasonal keywords while preserving your best evergreen terms
  • Remove seasonal terms that are irrelevant to your core use case

Subtitle (30 chars):

  • Consider a seasonal hook if it fits: "Your Holiday Planner" or "New Year Goal Tracker"
  • Only change if the original subtitle is not keyword-critical

Promotional text (170 chars — no review required):

  • Always update for seasonal events — instant, no review
  • Use for: seasonal call-to-action, limited-time feature highlights, event tie-ins

Screenshots:

  • Add a seasonal frame or theme to the first 2 screenshots
  • Use screenshot-optimization skill for creative guidance

Step 4 — Timing Checklist

Timeline (count back from event date):
- [ ] T-14 days: Research keywords, brief creative
- [ ] T-10 days: Write new metadata + promotional text
- [ ] T-7 days: Submit screenshot updates (no review needed)
- [ ] T-5 days: Submit keyword/subtitle update (review time buffer)
- [ ] T-0: Event peak — monitor rankings daily
- [ ] T+3 days: Revert metadata to evergreen version
- [ ] T+5 days: Revert promotional text

Output Format

Seasonal Opportunity Brief

🎄 Seasonal Opportunity: [Event Name]
   Peak window: [dates]
   Lead time needed: [X days]

Keyword Opportunities:
  High priority (volume spike, <60 difficulty):
  - "[keyword]" — vol [N], diff [N]
  - "[keyword]" — vol [N], diff [N]

  Secondary (relevant but competitive):
  - "[keyword]" — vol [N], diff [N]

Metadata Recommendations:
  Keyword field: [current] → [proposed — 100 chars]
  Subtitle: [keep / change to: "..."]
  Promo text: "[seasonal copy — 170 chars]"

Screenshots: [suggest seasonal theme or keep as-is]

Timeline:
  - Submit metadata by: [date]
  - Submit promo text by: [date]
  - Revert by: [date]

Seasonal vs Evergreen Trade-offs

FactorSeasonalEvergreen
VolumeTemporarily very highStable
CompetitionVery high at peakModerate
RiskRankings drop after peakConsistent
RewardSpike in installsSustained growth

Rule: Only swap evergreen keywords that are already underperforming. Never sacrifice a high-ranking keyword for seasonal speculation.

Trending Moments (Non-Calendar)

For viral/trending moments (news events, viral content, app store trends):

  1. Use GET /v1/keywords/trending?country=us&days=3 to spot emerging terms
  2. Act within 24–48 hours (trending windows are short)
  3. Only update promotional text (instant, no review)
  4. Revert after the trend fades (typically 3–7 days)

Related Skills

  • keyword-research — Deep keyword analysis for seasonal candidates
  • metadata-optimization — Rewrite full metadata with seasonal terms
  • screenshot-optimization — Design seasonal screenshot themes
  • market-pulse — Spot trending keywords and market movements in real time

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
appeeky
コミュニティ

rating-prompt-strategy

When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.

1時間の導入数
1
GitHub Stars
2316
更新日
11月13日
appeeky
コミュニティ

android-aso

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.

1時間の導入数
1
GitHub Stars
2291
更新日
11月10日
appeeky
コミュニティ

app-icon-optimization

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

1時間の導入数
1
GitHub Stars
2288
更新日
11月10日
appeeky
コミュニティ

ab-test-store-listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

1時間の導入数
2
GitHub Stars
2256
更新日
10月6日