See what a metadata change does before you ship it
Writing app metadata is guesswork right up until someone shows you the arithmetic. ASOnest drafts variants from your winnable keyword list and tells you exactly which keywords each one gains and loses.
You get 160 characters. Most apps waste forty of them.
Thirty characters of title, thirty of subtitle, one hundred in the keyword field. Repeat a word between them and you have thrown away the second copy. Include your category name and you have spent characters on something the store already knows.
Duplicate detection
Any word repeated across title, subtitle and keyword field is flagged and the wasted characters counted.
Real tokenisation
Your keyword field is split the way the store splits it, so you can see the combinations you actually earn.
Rule checks
Category names, plurals the store handles for you, competitor trademarks and banned terms all get flagged.
Locale inheritance
App Store locales that inherit keywords from each other are handled so you never pay twice for a term.
An ASO score that tells you what to fix
Every app gets a 0–100 ASO score with the reasons attached. Not a vanity gauge — a checklist ordered by how much each item is costing you in coverage.
- Character usage across every field and locale
- Keyword coverage against your tracked set
- Screenshot count, caption text and preview video presence
- Rating count and recency versus your competitive set
- Localisation coverage for the countries you sell in
- Keyword field only 61 of 100 characters used
- "planner" repeated in title and keyword field
- No subtitle set for de-DE and fr-FR
- Screenshots present for all device sizes
- Preview video present on primary locale
Let your AI assistant do the ASO busywork
ASOnest ships an MCP server on every paid plan. Point Claude, Cursor or any MCP client at it and your assistant can query live keyword, rank, competitor and review data instead of answering from training data that is two years old.
- "Which keywords did I lose this week?" — answered from live ranks
- "Draft three subtitles using my top winnable terms" — with real scoring
- "Add these five competitors and show me the gap" — it does the setup too
“cookbook app” #47 → #71
“dinner ideas” #38 → #59
“food diary” #44 → #63
What actually happens when you use it
- 01
Start from your winnable list
The generator only draws on keywords ASOnest believes you can reach, so drafts do not quietly spend characters on terms you will never rank for.
- 02
Generate constrained variants
Several title, subtitle and keyword field options, each obeying the character limits and content rules of the store and locale you are drafting for.
- 03
Score every variant
Each draft is tokenised the way the store tokenises it, expanded into the keyword combinations it makes you eligible for, and compared with your current coverage.
- 04
Review the gains and losses
Keywords gained, keywords lost, character usage and duplicate detection, shown per variant so the trade-off is explicit.
- 05
Export and ship
Copy the winning variant per locale straight into App Store Connect or Play Console, then let rank tracking confirm the result over the following weeks.
No. Suggestions are generated from your own winnable keyword list and constrained by store rules — 30 characters for App Store title and subtitle, 100 for the keyword field, no repeated words, no category names, no competitor trademarks. Each variant is then scored against your tracked keywords, so you are choosing between measured options rather than accepting a guess.
ASOnest tokenises your draft the way the store does, builds the set of keyword combinations it would make you eligible for, and compares that to your current set. "Gain +18, lose −2" means eighteen tracked keywords become newly targetable and two you currently target would be dropped. It is a coverage projection, not a rank prediction.
It will not, and any tool that claims to is guessing. Store ranking depends on download velocity, conversion rate and retention as well as metadata. ASOnest shows you the coverage change with confidence and leaves rank to the rank tracker, which measures it.
Yes, because the stores work differently. The App Store has a hidden 100-character keyword field and ignores the description for ranking. Google Play has no keyword field and does index the description. Suggestions follow the correct model per store rather than producing one draft for both.
Every locale is drafted in its own language with the correct tokenisation, including languages that do not separate words with spaces. Cross-locale keyword inheritance on the App Store is accounted for too, so you do not waste characters repeating terms an adjacent locale already covers.
Not yet. ASOnest produces export-ready copy per locale that you paste into App Store Connect or Google Play Console. Direct publishing is on the roadmap.
The rest of the toolkit
Start ranking for keywords you can actually win
Add your app, see your real keyword positions in under two minutes, and get a prioritised list of what to change first. 7 days free, no card required.