App Store Keyword Optimization 2026 — How to Rank Inside the 100-Character Limit
A practical 2026 ASO guide to ranking inside App Store's 100-character keyword field. Covers keyword selection, comma-packing rules, App Name + Subtitle weighting, localization, tracking tools, and common mistakes.
목차 (11)
April 2026 · App Store Optimization
The App Store keyword field is capped at 100 characters. How you fill those 100 characters decides about half of your app's search visibility. The other half comes from App Name, Subtitle, reviews, and installs. Of these, developers can change App Name, Subtitle, and the Keyword field at submission time. Get these three wrong and a great app lands on page 20 of search results.
Here's a 2026 practical ASO guide: Apple's field weighting, how to pack the most keywords into 100 characters, using App Name and Subtitle, per-country localization, common mistakes, and keyword tracking tools. Follow this once and your initial setup is done.
Bottom line: 100 characters isn't "space for many keywords" — it's "space for combinable puzzle pieces." Once that principle clicks, every other rule in this guide makes sense.
- Keyword field is 100 chars — commas only, no spaces, no duplicates
- App Name (30) + Subtitle (30) carry more ranking weight than the Keyword field
- Combination coverage beats single keywords — Apple auto-matches
A,Bas "A B" and "B A" - Mix three types: function + situation + alternative keywords for long-tail coverage
- Per-country localization requires re-picking keywords from that market's search data
- Competitor names, trademarks, and banned terms are rejection triggers
- Rankings shift daily — automated tracking (Apsity, etc.) is practical baseline
1. The 100-Character Rule
App Store Connect's Keyword field is exactly 100 characters. Spaces count. Only commas act as separators — using spaces, dots, or slashes makes Apple treat it as a single long word. Mixing English and other languages is fine, but each localization is a separate field.
The rules are simple: commas only, no duplicates, 100 chars max. Break them and you get a rejection. The most common mistake is "space after comma": app,analytics,tools works, but app, analytics, tools wastes 2 extra characters on spaces. It's like filling a 100-square-foot room with furniture and leaving 3 random empty slots for no reason.
Apple blocks submission past 100 characters. Hitting exactly 100 leaves no room to swap in new keywords later without removing existing ones. Aim for 95–98 characters and keep a buffer for future iterations.
2. App Name and Subtitle Matter More
Apple's ranking algorithm weights fields differently. App Name (up to 30 chars) > Subtitle (30 chars) > Keyword field (100 chars). A keyword placed in App Name or Subtitle outranks the same keyword sitting in the Keyword field. The exact weight multiplier isn't public but multiple ASO experiments confirm the ordering.
Example for a personal finance app:
- App Name:
Qash - Budget & Expense Tracker(3 core keywords) - Subtitle:
Monthly spending · Payday planner(situation keywords) - Keywords:
money,wallet,receipts,savings,debt,statement,assets,bills,income,payments
App Name carries budget·expense·tracker; Subtitle adds spending·payday. The Keyword field fills with complementary terms that aren't already in Name/Subtitle. Duplicating keywords across fields wastes characters — same word in three fields doesn't triple the weight, and can trigger keyword-stuffing flags.
Stuffing too much in App Name hurts branding. Something like Budget Tracker Expense Manager Finance might rank but won't stick in users' minds. A brand word + 2–3 core features is the balance point.
3. Combination Coverage — Apple Auto-Matches
If your Keyword field contains expense,tracker, searches for "expense tracker" match too. Apple auto-combines keywords for matching — order doesn't matter. Use that and a single word covers multiple compound queries.
Don't waste space writing expensetracker as one word. Write expense,tracker — it matches "expense", "tracker", "expense tracker", and "tracker expense". Four queries covered with two keywords.
One level deeper: adding a situation keyword stacks to 8–12 covered queries. expense,tracker,payday covers "expense tracker", "payday tracker", "expense payday", "payday expense tracker", etc. Three words deliver 8+ search queries.
CamelCase or space-less compounds like
signUp,signIn,userManagement get parsed as single tokens by Apple. Breaking them to sign,up,in,user,management gives you 5 tokens covering 10+ queries like "sign up", "sign in", "user management", "sign in management". Maximum efficiency inside 100 characters.
4. Mix Three Keyword Types
A strong keyword mix blends three categories. Stacking one category floods competitive red-ocean keywords and kills ranking overall.
| Type | Example (budget app) | Search volume | Competition |
|---|---|---|---|
| Function | budget,expense,statistics | High | Very high |
| Situation | payday,monthly,receipts | Medium | Medium |
| Alternative | wallet,money,finance | High | Low–medium |
Function-only keyword lists get crushed by competition. Getting into top 10 is brutal. Situation and alternative keywords have slightly lower volume but lower competition — often it's easier to rank #3–5. The long-tail total frequently beats top-rank traffic on competitive keywords.
In my own apps, being #2 on "payday tracker" drove more installs than being #10 on "budget." Users typing "payday tracker" have a clearer intent — conversion rates are higher. Don't just look at search volume — look at intent density per query.
5. Per-Country Localization
Each language in App Store has its own Keyword field. Korean (ko) and English (en-US) are separate inputs. Machine-translating the same list ignores per-country search trends. Apple references only the Keyword field matching the user's device language.
An English budget app leans on budget,expense,money tracker. Korean works better with 가계부,지출,월급. Japanese users type 家計簿. Each market needs keywords re-picked from that market's actual search demand. Direct translation often backfires.
Korean is particularly sensitive to spacing and variant spelling. "가계부" and "가계 부" are different tokens to Apple. You need real per-market search data to know which form users actually type. Tools like Apsity provide real search-trend data and automate this.
Country expansion checklist: (1) analyze 5 competitor apps in that market, (2) extract keywords from their App Name and Subtitle, (3) rank common words by frequency, (4) pick 8–12 that match your app from the top 20. Repeat per country.
6. Rankings Shift Daily — Monitor Them
Setting keywords is step one. Apple's ranking keeps adjusting based on installs, retention, and review scores. A keyword that ranked #10 the day you shipped might be #50 a week later. A competitor pushing a new version with stronger keywords drops you.
Daily checks are the baseline. App Store Connect doesn't show per-keyword rank directly — you need an external tool. For indie developers, the practical choices are Apsity, ASO index, and App Radar. Apsity has a free tier with no cost to start — 1 app, 5 keywords, 3 competitors on Free. Pro at $19/month removes the limits entirely.
The real value of automation is drop alerts. Manually eyeballing ranks daily isn't realistic. A rank drop of 5+ or a new keyword entering top 10 should page you. Apsity ships this by default.
7. Five Common Mistakes
| Mistake | Cost | Fix |
|---|---|---|
| Space after comma | ~10% of 100 chars wasted | Stick to app,analytics |
| Singular + plural dup | Apple matches either form | Pick one |
| Competitor brand names | Trademark rejection | Use alternatives |
| Category name dup | Overlaps Apple's auto-index | Skip "Finance"/"Productivity" |
| Full rewrites | Resets accumulated rank | Swap ≤20% per update |
The most common mistake is the "full rewrite." After an ASO consultation, people often replace the entire 100 characters — feels clean but risky. Any keywords you'd ranked top-10 on reset. Instead, swap ≤20% per update and observe for 2–3 weeks. Progressive replacement beats a full rewrite.
8. When to Push Keyword Changes
Keyword fields can only be updated at the moment of an app version submission — including patch versions (e.g., 1.0.1). To change only keywords, submit a patch update with no feature changes. Even a build-number-only bump works.
But too-frequent changes make App Review sensitive. Once a month is a safe upper bound. Faster than that and "keyword stuffing" or "review evasion" concerns kick in. In extreme cases, Expedited Review privileges get revoked.
Recommended cadence: one large quarterly overhaul + small monthly tweaks. Quarterly = adding new keywords + removing drops. Monthly = situation-keyword swaps. This balance holds Apple Review sensitivity and ASO effectiveness.
If you have two similar apps, apply the new keyword set to only one and compare over 4 weeks. Product Page Optimization also lets you A/B within the same app. Real performance data beats algorithm guessing.
9. Stage-Based ASO Strategy
ASO approach varies by app stage. A freshly launched app and one with 100k installs need different strategies.
| App stage | Strategy | Recommended tool |
|---|---|---|
| Post-launch (0–1k installs) | Long-tail niche capture | Apsity Free (1 app) |
| Growth (1k–10k) | Settle in top-10–20 on primary keywords | Apsity Starter $9 (3 apps) |
| Steady (10k–100k) | Country expansion · competitor defense | Apsity Pro $19 (unlimited) |
| Mature (100k+) | Full-market monitoring | Appfigures or higher |
Post-launch, skip the crowded single-word keywords. With no install signal, Apple's algorithm won't surface the app anyway. Ranking top-tier on long-tail queries to accumulate download signal is the faster growth path.
FAQ
Q. How many keywords fit in 100 characters?
Usually 15–20, depending on word length. Short Korean words fit 20 easily; longer English words limit you to 12–15. Don't pack to 100 exactly — 95–98 leaves space for later swaps.
Q. Should I put keywords in App Name and Subtitle?
Yes — highest ranking weight. Blend 2–3 core keywords naturally in App Name (30) and Subtitle (30). But App Name without a brand word is forgettable. Brand + 2–3 features is the balance.
Q. Can I use competitor app names as keywords?
Trademark risk. App Review might reject, or a competitor might request removal. Not recommended. Benchmark competitors' "functional keywords" but avoid their brand names.
Q. How often do rankings change?
Daily. Popular keywords shift hourly. Once-a-week snapshots miss trends. A competitor launching a new version can move your rank significantly within days. Automated tracking is effectively required.
Q. Are there tools to automate keyword rank tracking?
Apsity, ASO index, App Radar all offer automated tracking with per-country dashboards and drop alerts. For indie developers, Apsity's free tier is the lowest-cost entry. Pro at $19/mo removes app, keyword, and competitor limits entirely.
Closing
ASO keyword optimization is, fundamentally, cramming "what users actually search" into 100 characters while loading App Name and Subtitle with the core terms for higher weighting. Mix function + situation + alternative types. Re-verify per country. Follow these, and you'll land top-ranking long-tail keywords from day one.
Manual management breaks down once you hit 3+ apps and 100+ keywords tracked across countries. Tools like Apsity's AI growth agent automate the keyword optimization loop. For solo devs, start with the free tier on one app, learn the rhythm, then expand into paid tiers. Having the rules in this post baked into a tool removes the need to memorize checklists.
· App Store Marketing Guidelines — Apple Developer
· App Store Connect Help
· App Review Guidelines
Based on Apple's official App Store Connect guidelines and real-world ASO experience as of April 2026. Policies change — always cross-check with App Review Guidelines.
Numbers and recommendations reflect hands-on operating experience and may vary by app category and country.