Review a Store Listing With Accented Keywords
Admin ·
Check a draft in the same fields your team will paste into the publishing consoles. Apple and Google Play share some limits, while their short listing fields differ. The worked example includes an accented Apple keyword, a duplicate, and an extra space.
App Store Metadata Character Counter
Measure the keyword list before removing duplicates
Select Load example with the combined profile. The Apple keyword list reads routes,café, CAFÉ,地図,go. The report shows 29 of 100 UTF-8 bytes. The third entry includes a leading space and repeats the second entry. The final two entries receive short-term advisories.
Open Show Unicode counts. The keyword list has 23 code points. Turn on Compare counts without whitespace to see 28 bytes after removing the single space. The limit result continues to count all 29 bytes. Removing the duplicate term from the editor changes the actual listing budget.
Compare fields that share copy and fields that use separate limits
In the combined profile, App name and Full description use the same draft text for both stores. Subtitle and Promotional text belong to Apple. Short description belongs to Google Play. The two store rows for App name also check Apple's two-character minimum.
The sample Play short description uses 60 of 80 code points. Set the near-limit threshold to 75% to flag it at the boundary. Switch to the Apple Version update check to include What’s New. Clear that field to see the missing-text result for an update.
| Store | Common field limits |
|---|---|
| Apple App Store | Name 30, Subtitle 30, Promotional text 170, Full description and update notes 4,000, Keywords 100 UTF-8 bytes |
| Google Play | App name 30, Short description 80, Full description 4,000 |
Apple App Store Connect, App informationApple App Store Connect, Platform version informationGoogle Play Console, Add product details
Save the checks and compare counts in the console
Flag advisories in strict mode when your local review includes near-limit text and keyword cleanup. Download JSON report to record the metrics and advisory positions. The file records the checks without including the draft sentences.
Use one draft per language. A visible emoji or accented letter can contain several Unicode code points. The report shows code points, UTF-16 units, grapheme clusters and UTF-8 bytes. Confirm character-count differences in App Store Connect or Play Console before submitting.
Unicode Standard Annex #29, Grapheme Cluster BoundariesApple App Store Connect, Platform version informationGoogle Play Console, Add product details
Common questions
Why does the app name count differ between code points and UTF-16 units?
A Unicode code point above U+FFFF takes two UTF-16 units. A name with a supplementary-plane emoji can use more units than the number shown in the code-point column.
Will changing the near-limit percentage shorten the listing?
The percentage controls when the checker shows an advisory. The editor text and store limit stay the same.
Sources
Put it into practice.
- App Store Metadata Character Counter
- App Store Metadata Character Counter
- Unicode Code Point Viewer
- Word & character counter