Full description

Expert: with sources and numbers. Plain: the same, without them, for beginners.

4,000 indexed characters, and the field where Google states most directly that keyword stuffing is against policy.

Verified 2026-09-18 · 38 days ago android metadata keywords indexing policy

The main indexed body text on Google Play, and the field where the difference from iOS is largest. Apple does not name the description as a search input. Google does.

The rules

A The full description is limited to 4,000 characters. (Create and set up your app, verified 2026-09-18)

A It is part of the metadata Google uses to identify what an app is. (App Discovery and Ranking)

A Google’s guidance: “Make sure your app’s description accurately describes its functionality and content” and “Keep your app’s description succinct and straightforward.” (Best practices, verified 2026-09-18)

Google tells you not to keyword-stuff, in its own words

This is unusually direct for platform documentation and worth having verbatim.

A Google advises avoiding “excessive length, detail, improper formatting, and repetition of words”, and gives an example of what not to write:

“Car racing, car driving, race cars, car races, race track, driving, drive, race, cars, vehicles, automobiles, trucks”

Instead: “Provide a well-written, succinct description of your app and what makes it special.” (Best practices, verified 2026-09-18)

A The Metadata policy makes it enforceable, prohibiting “misleading, improperly formatted, non-descriptive, irrelevant, excessive, or inappropriate metadata” and “repetitive or unrelated keywords or references”. (Metadata policy, verified 2026-09-18)

A The same policy prohibits unattributed or anonymous user testimonials in the description, along with ranking claims, price and promotional text, and Google Play program badges. Same source.

So the common advice to repeat a target term a fixed number of times across the description is advice to do the thing Google names as a policy violation, using an example Google itself supplies.

The density question

B That Google weighs term frequency in the description to some degree is widely and consistently reported by independent practitioners, and is consistent with Google naming the description as a metadata input. It is not documented, and no reliable figure for an optimal count exists.

C Specific density targets (“repeat your main keyword five times”, “aim for 2–3% density”) are claims in circulation. Single-source or unevidenced, they vary wildly between sources, and following them produces exactly the text Google’s own example warns against.

The workable position: use your important terms naturally where they belong, in text a person would want to read. If a term appears often, it should be because the app genuinely is about that thing. Writing to a density number optimises for a mechanism nobody has demonstrated, against guidance Google has published.

How to work with it

Front-load. Only the first lines show before “Read more”. Whatever earns the expand goes there.

Short paragraphs and restraint. Basic formatting is supported, but Google’s guidance is against improper formatting and excessive detail. Walls of text and bullet lists forty items long fail on both counts.

Structure it around use cases. Natural coverage of the way people describe what they want, which also happens to be how they search.

Say what is free and what is paid. Removes a large class of one-star reviews.

Localize it. It is 4,000 characters of indexed text; a machine translation is both a ranking and a credibility problem, 30-05.

What goes wrong

Keyword lists at the bottom. The single most common Play metadata violation, and Google’s documentation contains the counter-example.

Importing the iOS “first 245 characters” rule. That claim is wrong on iOS (CONFLICT-002) and only loosely descriptive on Play, where what matters is that the visible portion earns the expand, not a specific character count.

Unattributed testimonials. “Users love it!” with no attribution is explicitly prohibited.

Copying the iOS description across. It was written for a field that is not indexed. See 20-08.

Never revisiting it. It is not release-bound. There is no structural reason for it to be three years old.

In short

Every fact on this page in one line, with its evidence tier, source and verification date, 4 A · 1 B · 1 C. Generated from the claim register, so it cannot drift from the page above.

A Google Play app name is limited to 30 characters; short description to 80; full description to 4000.
PLAY-MD-001 · verified 2026-09-18
A Google advises avoiding excessive length, detail, improper formatting and repetition of words in the full description, and publishes a keyword-list example of what not to write.
PLAY-MD-004 · verified 2026-09-18
A Google Play's Metadata policy prohibits misleading, improperly formatted, non-descriptive, irrelevant, excessive or inappropriate metadata, and repetitive or unrelated keywords or references.
PLAY-POL-003 · verified 2026-09-18
A Google Play prohibits unattributed or anonymous user testimonials in an app's description.
PLAY-POL-004 · verified 2026-09-18
B Google Play weighs term frequency in the full description to some degree.
PLAY-DENS-001 · verified 2026-09-18
C Repeat your main keyword a specific number of times, or to a stated density percentage, in the Google Play description.
KW-DENS-C01 · verified 2026-09-18

Think your app deserves better?

Send the App Store link.
The audit comes back within two working days, whether you hire us or not.

Free, and we mean it. No card, no call required.