How to use it
Paste your full description. Review the top terms. If one term dominates or a keyword list appears, rewrite naturally.
No magic number
Google publishes no ideal density. The metadata policy prohibits repetitive or irrelevant keyword use. See metadata rejections.
For iOS
The App Store description isn't indexed for search; use the ASO title checker.
Get it written
How to use the density checker well
Follow these steps in order. Each one is something we do on client work.
- Paste the full description. Up to 4,000 characters.
- Look at top terms. Are they the ones you want?
- Check repeats. Repetitive keywords can lead to suspension.
- Rewrite naturally. Use synonyms and sentences.
- Check the short description. 80 characters, one benefit.
- Re-run. Confirm balance.
Worked example (hypothetical)
This example is illustrative. The app is made up, and so are any numbers in it.
Say BudgetBee's description uses "budget" 40 times. We'd cut repeats, add related terms like "expenses" and "savings", and keep sentences readable.
Google Play listing fields and their limits
Play Console enforces these limits for every language, full-width or half-width characters alike.
| Field | Limit | Policy notes |
|---|---|---|
| App name | 30 characters | No emojis, ALL CAPS (unless brand) or store-ranking claims |
| Short description | 80 characters | First text users see on the detail page |
| Full description | 4,000 characters | Repetitive or irrelevant keywords can lead to suspension |
| App icon | 512 × 512 px, 32-bit PNG, max 1,024 KB | No badges or text implying ranking |
| Feature graphic | 1,024 × 500 px, JPEG or 24-bit PNG | No alpha |
How we measure the result
A tool gets you a correct file or a quick check; it doesn't tell you whether the result converts. After you upload, watch conversion in App Analytics or Play Console, and use product page optimization or store listing experiments to compare versions. Re-run the tool whenever Apple or Google updates their specs, which they do when new devices ship. We re-check the official spec pages each time we update these tools.
iOS vs Google Play: where density matters
| Store | Description indexed for store search? | What to do |
|---|---|---|
| Google Play | Yes, title and descriptions carry the keywords | Use main terms naturally, avoid repetition |
| App Store | Apple uses it for web search results | Write for people; put search terms in name, subtitle and keyword field |
Common mistakes
- Chasing a magic percentage. There isn't one.
- Keyword lists. Policy risk.
- Ignoring readability. Hurts conversion.
- Same text on iOS. Different role there.
Checklist
Copy this list into your release notes or ticket and tick each item off before you ship.
- Description pasted
- Top terms reviewed
- Repeats cut
- Natural rewrite
- Short description checked
Sources
- Google Play Console Help: Metadata policy (accessed 26 October 2026)
- Play Console Help: Create and set up your app (accessed 26 October 2026)
- Play Console Help: Add preview assets to showcase your app (accessed 26 October 2026)
Questions
What density is safe?
There's no official number; write naturally.
Does it store my text?
No.
Does it work in other languages?
Yes for space-separated languages.
Phrases too?
Two- and three-word phrases.
Is it for iOS?
Mainly Play.
What keyword density is best for Google Play?
Google doesn't publish one. Mention main terms naturally and avoid repetition its metadata policy warns about.