Two fields do almost all the work
A Play listing has many fields; two of them decide installs. The title (30 characters) is what appears in search and under your icon. The short description (80 characters) is the line shown before "read more". Most visitors decide from those and the icon. The full description gets 4,000 characters and is read mostly by Play's index and the minority who scroll.
| Field | Limit | Appears |
|---|---|---|
| Title | 30 | Search results, home screen, listing header |
| Short description | 80 | Top of the listing, some search cards |
| Full description | 4,000 | Listing body, behind "read more" |
| Developer name | 50 | Under the title everywhere |
Wording Play bounces
The metadata policy is stricter than most people expect. In the title and short description you cannot use:
- rank or quality claims — "#1", "best", "top rated";
- promotions — "free", "sale", "discount", "50% off";
- calls to action — "download now", "install today";
- emoji or emoticons;
- ALL CAPS, unless the brand is genuinely written that way;
- keyword stuffing — repeating a term to game search.
The checker flags each as you type. None is permanent — they just cost a review cycle if you discover them the slow way.
A title that fits
Brand, then what it is works: "Acme — Shop & Delivery" reads well and tells a stranger what they are looking at. The failure modes are the extremes — a bare brand name that means nothing, or "Shop Online Store Buy Cheap Fast Delivery App", which Play treats as stuffing. Remember the home screen shows roughly 12 characters under the icon, so what comes first matters most.
The short description is the pitch
Eighty characters answering "what do I get?" rather than "what is this?". Compare:
Weak: "The official app of Acme Ltd, established 2009."
Better: "Browse the full Acme range, track orders and reorder in two taps."
The second is about the reader — and contains the words someone would search for.
The full description
Write for a person and the index follows: a paragraph on what the app does, a short list of what you can do with it, who it is for, then practical notes — offline support, accounts, regions. 500–1,500 characters is plenty; 4,000 is a ceiling. Repeat key terms naturally two or three times, not fifteen.
A preview, not a promise
The panel reproduces Play's limits and wording rules, which catches the common rejections. It cannot predict a reviewer's judgement on whether the app matches the listing — the usual cause of the harder rejections. The publishing checklist covers the rest.