ASO keyword combiner
Dedupe, merge, and compress App Store’s 100-byte keyword field. Uses the browser segmenter; everything stays local. No search-volume data — order follows your input.
2. Paste candidates on the right (stronger terms first). Put brand names and unsplit terms under Protected.
3. You get Safe and Max-coverage plans, plus removed terms and risky merges.
When done, re-check field lengths in . Title & keyword counter
What this tool does
Pack App Store’s 100-byte keyword field: dedupe against title/subtitle, merge overlapping tokens with re-segmentation checks, skip risky merges. No search volume — order is your priority.
How to use
- Fill title/subtitle; put brands in Protected.
- Paste candidates (stronger first).
- Compare Safe vs Max coverage; copy one.
How it works
- Official caps/rules from Apple Search / Connect docs.
- Bag-of-words merge model from industry ASO practice.
- Dedupe removes tokens already in title/subtitle.
- UTF-8 bytes: Latin/comma 1, common CJK 3.
- Intl.Segmenter can over-split brands — use Protected.
FAQ
Official Apple rules?
≤100 bytes, comma-separated no spaces, don’t repeat name/subtitle/category terms, >2 chars each, no competitor marks.
Do fields combine in search?
Apple doesn’t publish exact combo rules; industry assumes bag-of-words within a localization. Long-tail preview is an estimate.
Why skip some merges?
Re-segmentation must still recover original tokens — otherwise search breaks (classic ASO “组词” risk).
Remove all commas?
We keep commas in both plans — safer for review and exact matches.
Safe vs Max?
Safe: protected alone, merge cap (default 5). Max: unlimited merges; drops short terms covered by longer ones.
Same as Apple’s segmenter?
No — we use Intl.Segmenter. Protect brands; verify in ASO tools after shipping.
Related guides & tools
More tools in thedeveloper toolbox. For store preview shots, try theApp Store screenshot maker.