App Store metadata assembler
App Store metadata is 160 visible characters across three constrained fields. Most apps waste 15–30 of them on duplicates, stop words, or stemming repeats Apple ignores anyway. Keypack finds those gaps and fills them.
The problem
You're duplicating words across fields — and losing indexing coverage for it
Apple deduplicates at index time. A word in your title doesn't need to be in your keyword field. Most apps repeat 3–6 words across fields, burning character budget on terms that are already indexed.
title: "Time Out — Screen Time Tracker" + keywords: "screen,time,tracker" → 3 wasted terms Stop words and stemming variants are quietly eating your 100-character keyword field
Apple ignores "app", "free", "the", "and", "for". It also collapses stems — "track", "tracker", "tracking" all index as one. Using all three burns 18 characters to get one keyword's worth of coverage.
"track,tracker,tracking,app" → Apple sees "track" · 20 chars wasted You can't see which keyword combinations your three fields actually index for
App Store indexes multi-word phrases by combining terms across title, subtitle, and keyword field. You might be indexing for "screen time limit" without realising it — or missing "limit screen" because you used both words in the same field.
How it works
Paste your researched keywords
Keypack is the assembly step, not the research step. Use whatever keyword tool you already have — Sensor Tower, AppFollow, your own instinct. Bring the list.
The engine runs the constraints
Exact character counts per field (title ≤30, subtitle ≤30, keywords ≤100). Cross-field deduplication. Apple stemming rules. Stop word removal. Combination-coverage enumeration. Deterministic — same input, same output, every time.
Get 2–3 validated variants with plain-English trade-offs
Each variant shows exact character counts, waste recovered, and a full list of indexed keyword combinations. Every variant has passed the engine — no violations reach you.
Title
Time Out: Screen Limit
Subtitle
Focus & Daily Usage Tracker
Keyword field
block,parental,control,downtime,productivity,wellbeing,digital,detox,manage,habit
Pricing
€9
one-time per app · keep forever
Early access: sign up now, pay when it ships.
FAQ
Why not just use ChatGPT?
LLMs are unreliable at exact character counting. Ask GPT-4 for a 30-character title and check it — it's off by 2–5 characters consistently. It can't enumerate stemming rules or catch cross-field duplicates deterministically either. Keypack's engine handles the constraints first; language generation only handles phrasing, and its output is validated before you see it.
Do I need to do keyword research first?
Yes. Keypack is the assembly step, not the research step. You bring the keywords you've already identified. Keypack figures out how to fit them into 160 characters without waste.
Can you see my keyword field after I submit?
The App Store keyword field is private — Apple doesn't expose it publicly. Your metadata is used only to run the engine and is not stored or shared beyond your session.
iOS only?
v1 is iOS only. The Apple-specific indexing rules (stemming, stop words, field weighting) are the core of the engine. Google Play has a different character model and different rules — a separate product, not a checkbox.
What's the free self-audit?
Paste your current title and subtitle (public fields — 60 characters total). Get a scored teardown: duplicate words, stemming waste, stop words, coverage gaps. No keyword field required. Coming soon.