Google Play store listing optimization: title, short and long description (2026)

Google's own help page says that stuffing extra keywords into your 80-character short description "will not impact ranking and provides a bad user experience" (Play Console Help, Add preview assets to showcase your app, 2026). Plenty of Google Play ASO guides still tell you to load it.

Google Play store listing optimization comes down to three fields of 30, 80 and 4,000 characters that have to rank and convert at once. The density advice contradicts itself, and in 2026 an AI reads your long description too. This guide goes field by field: policy lines, a density answer measured on 23 top listings, a teardown, then localization and testing. For the ranking signals beyond your metadata, see our separate breakdown.

What are Google Play's listing text fields and character limits?

As of September 2026, Google Play indexes three text fields: the app name (30 characters), the short description (80) and the full description (4,000). Those limits apply to "both full-width and half-width characters" (Play Console Help, Create and set up your app). The title cap fell from 50 characters to 30 in 2021.

Google announced that cut on April 29, 2021 (Android Developers Blog), and AppTweak dates enforcement to September 29, 2021 (AppTweak, 2023). Each field also carries rules Google enforces:

Sources: Metadata policy; Add preview assets; Best practices for your store listing (Google, 2026).

The stakes go beyond a rejected update. Google warns that "repetitive or irrelevant use of keywords" can "result in an app being suspended on Google Play" (Play Console Help, 2026). Count all three fields as you write, and see every metadata limit on both stores if you ship on iOS too.

Top listings use nearly all of the room. In our September 2026 audit of 23 category leaders, the median title used 29 of 30 characters, the median short description 77 of 80, and the median full description 3,682 of 4,000. The method is in Step 5.

Step 1: How do you decide which keywords each field carries?

Build a keyword map before you write copy: one or two head terms for the title, a benefit phrase for the short description, and the long tail plus use cases for the full description. In 2026, Play Console's acquisition reports include a "Search term" dimension, and Google suggests reviewing "search terms driving the most visits" (Play Console Help, Understand and grow your app's user base).

Start there, because those queries already reach your listing. Since Google I/O in May 2026, the Grow overview also shows keyword recommendations. Click one and "Gemini creates a new custom store listing automatically tailored to that keyword" (Android Developers Blog, I/O 2026: What's new in Google Play). Treat it as a draft when you turn a keyword cluster into its own listing.

Don't let the AI features pull you off head terms. In June 2026, AppTweak noted that short and mid-tail searches "still make up the bulk of search volume" (AppTweak, Google I/O 2026: what the Gemini era means for Google Play ASO).

Step 2: How do you write a Google Play title that ranks?

Use your brand plus your strongest one or two head terms, inside 30 characters. In our September 2026 audit, 22 of 23 top listings did exactly that, from "Airalo: eSIM for travel & data" to "MyFitnessPal: Calorie Counter." Google asks for a title that's "unique and accessible," avoids common terms and reinforces "what your app is about" (Play Console Help, Get discovered on Google Play search).

Google's own bad example is "Crane: travel PLANNER!! 🌞": capitals that aren't the brand, repeated punctuation and an emoji in one title (Play Console Help, Best practices for your store listing). "Free" and "No Ads" "promote deals and don't belong in app titles." Google also warns against "subtle misspellings of general terms," since users may correct the search.

Truncation is the practical limit. "Long titles may be shortened on some devices," so put the head term right after the brand, where it survives a cut. Preview the truncation in Play mode before you ship. Only 7 of 23 top titles use all 30 characters.

Brand-forward titles cost less on Play than on iOS, because Google indexes the full description and it can carry secondary terms. Is your brand strong enough to stand alone? That's the keyword-versus-brand call.

Step 3: What should the Google Play short description say?

One benefit-led sentence that makes the install decision easy. Google's 2026 help page calls it "a quick synopsis meant to spark user interest by outlining your app or game's key value." Adding "unnecessary keywords in an attempt to improve search results," it says, "will not impact ranking and provides a bad user experience" (Play Console Help, Add preview assets).

It's "the first text users see" on your details page, and it "can appear in locations beyond your store listing." So treat it as conversion copy. Google rules out calls to action, "Best," "#1," "Top" or "New," emoji, special characters and slang. Don't repeat what your screenshots say either, because "these assets may be shown side by side."

Top listings follow two patterns. In our audit, 13 of 23 short descriptions reinforce a non-brand word from the title. Airalo's reads: "Buy and manage your travel eSIM easily with Airalo, from fixed to unlimited data." The other 10 extend into new terms or pure benefit. Todoist, titled "To Do List & Calendar," writes: "Organize tasks, capture ideas by voice, and keep your teamwork on the same page."

Read Google's sentence closely. It says extra keywords won't help ranking, not that the field is ignored. So allow at most one keyword, written as part of the benefit, and use the space: the median in our sample ran 77 of 80 characters.

Step 4: How do you structure the full description for search, Ask Play and readers?

Front-load, then cover. Google's 2026 guidance warns that "users may only read the first few sentences" and asks you to keep "the most important text" visible "on the top half" of the page (Play Console Help). A model reads it too. In June 2026, AppTweak wrote that "your long description is now being parsed by a language model, not only skimmed by a user" (AppTweak, 2026).

Here's a structure you can copy:

1. Opening (first 500 to 700 characters): who it's for, the situation and the outcome, in plain sentences.
2. Feature sections with plain headers: one use case each, with its long-tail terms.
3. How it works: numbered steps.
4. FAQ block: real user questions, one-sentence answers. Airalo does this.
5. Proof: attributed quotes only. Google bans "unattributed or anonymous user testimonials."
6. Contact and legal.

Write in "everyday language, not a list of keywords." Google's own violation example is a block like "Car racing, car driving, race cars, car races…" (Play Console Help, Best practices). Google does say to "use SEO best practices" in the description, while avoiding "keyword spamming" and excessive emoji, which trip up screen readers.

The opening matters for a second reason. AppTweak's August 2026 tests point to the long description as Ask Play's main input, and Ask Play is English-device-first and US-led as of September 2026. We cover how Ask Play and Gemini read your long description separately. If you ship on both stores, here's why Google reads the whole description and Apple doesn't.

How long should the full description be?

Use most of the 4,000 characters, as long as every line earns its place. Top listings use a median 3,682 characters, about 92% of the limit (our audit, September 2026). Google's Metadata policy counters that "shorter descriptions tend to result in a better user experience." Both hold if the deciding sentences come first and the coverage comes after.

Step 5: How much keyword density does Google Play want?

Google publishes no number. It only says to avoid "repetition of words" and to write in "everyday language, not a list of keywords" (Play Console Help, 2026). In our September 2026 audit of 23 top listings, the most-repeated non-brand word ran at a median 3.2% of words, about 17 mentions. The most-repeated two-word phrase appeared a median four times.

The middle half sits between 1.9% and 3.8%. The lowest figures belong to the strongest brands: Airbnb at 1.0%, Revolut and Strava at 1.2%. Challengers in crowded categories run hotter, such as Canva at 4.3% and Duolingo's chess push at 4.7%.

Why does the density advice contradict itself?

Because it counts two different things. Percentage advice describes a single word: AppTweak recommends "between 2.5% and 3%" (AppTweak, April 2026), and MobileAction's checker says "2-3.5%" (MobileAction, undated). Count advice describes an exact phrase: MobileAction's 2024 guide says "up to 5 times" (MobileAction, 2024), and SemNexus suggests "two to three natural mentions" (SemNexus, July 2026).

At our sample's 6.4 characters per word, 4,000 characters is roughly 625 words. The percentage advice then means about 13 to 22 mentions, and the count advice 2 to 5. So who's wrong? Nobody, really. A head word like "eSIM" recurs inside many phrases, so it lands near 3% while each exact phrase shows up about four times.

What density rule should you follow?

1. Phrases: use each exact target phrase three to five times, plus natural variants such as plurals and synonyms.
2. Head word: keep any single keyword around 2% to 3% of words. The leaders' 3.2% median shows a little above that is normal, so don't chase a decimal.
3. Ceiling: never let a single word pass about 5%. Rephrase instead.
4. Brand-led lows: Airbnb's 1.0% reflects its brand. It isn't a target.

Run your draft through the Keyword Density Checker, which uses the same tokenizer as our audit. One caveat: these apps also rank on brand, installs and ratings, so the audit shows common practice, not what causes rank.

Teardown: what does a strong Google Play listing look like next to a weak one?

The strong listing puts brand plus head term in the title, a benefit in the short description and a use-case sentence first in the full description. The weak one loads keywords into every field and breaks policy in its first line. Airalo's live listing, fetched September 24, 2026, shows the strong pattern (Google Play, Airalo listing).

Its full description opens: "With an eSIM from Airalo, get connected the moment you arrive at your destination, without worrying about roaming fees, SIM card hunting, or untrustworthy airport wifi." A definition, plan types, a numbered "How it works" and an FAQ block follow, in 3,820 characters with no emoji. The weak column is an illustrative composite, not a real app.

Two cautions. Even Airalo isn't a template in every line: its plan list quotes a starting price, and Google's best-practices page says listing text shouldn't carry "price and promotional information." And several leaders still use "#1" (Calm, MyFitnessPal and Yazio) or emoji (8 of 23) in their descriptions. A smaller app shouldn't treat that as precedent.

Step 6: How do you localize a Google Play listing?

Write a native listing for each priority language instead of leaning on automatic translation. As of September 2026, users can view an automated translation where you haven't added their language. Google still says "using a professional translation service for your 'Description' can lead to better search results and discoverability" (Play Console Help, Get discovered on Google Play search).

Play Console lists 86 store-listing language codes (our count, September 24, 2026). Its free machine translation covers only 10 languages, "not reviewed or approved by humans." Paid human translation costs "as little as USD 0.07 per word," done "within seven days" (Play Console Help, Translate and localize your app). That's about $44 for a 625-word description, by our arithmetic. For budgets beyond one field, see what each localization tier costs.

Since I/O 2026, Gemini can "pre-populate your listings across different languages for your review" from a CSV or Google Sheet (Android Developers Blog, 2026). Take "for your review" literally. Then run these checks:

• Research keywords per locale. Don't translate your English keyword list.
• Use the character rule. Full-width characters count the same as half-width, so a Japanese title fits more meaning into 30.
• Apply policy everywhere. The Metadata policy applies "to all translations."
• Watch CTR by language. If one trails its peers, Google says to "investigate whether your listing is correctly translated."

Listings vary by language, so country-specific copy belongs in custom store listings. For where to start, see which languages to localize first.

Step 7: How do you test and measure listing changes in 2026?

Test copy in a localized store listing experiment, judge it on unique install clicks, and track rankings separately. Google's help page, fetched September 24, 2026, limits default graphics experiments to the icon, feature graphic and screenshots. Descriptions can be tested only in localized experiments, "in up to five languages" (Play Console Help, Run A/B tests on your store listing).

A single-language listing runs localized experiments in its default language. The app name isn't on Google's list of testable assets, and Google recommends testing "one asset at a time."

The variant cap is in flux. Google's page still says "you can choose up to 2 variants." On August 7, 2026, Phiture reported that in late July, multi-variant testing "appears to have been removed," leaving "standard two-way (A/B) testing" (Phiture, ASO Monthly #121). Check your own console, and plan for one variant against control.

The metrics changed too. From June 2026, Google measures store listing performance on unique clicks on Install, Open and Pre-register, and CTR "replaces the legacy 'Conversion Rate' metric" (Play Console Help, 2026). Phiture also reports new Total, User and Device impression metrics. Impressions show discoverability; CTR shows your copy.

After you apply a winner, keep tracking positions. Play rankings take six to eight weeks to settle after a metadata change, longer than most teams wait.

What are the most common Google Play listing mistakes?

The costly ones treat a conversion field as a keyword slot, or read a conversion result as a ranking result. Six to avoid:

• A keyword list in the short description. Google says it won't help ranking, and it costs conversion.
• Opening the full description with the short description. Google says don't, and 0 of 23 top listings do.
• Chasing a density percentage without naming the unit. Words and phrases behave differently.
• Machine-translating and walking away. Free machine translation isn't human-reviewed.
• Reading an experiment win as a ranking win. Experiments measure install clicks.
• Promo or ranking words in the title. "Free," "#1" and "Best" break the Metadata policy.

The bottom line

Each Google Play text field has one job:

• Title: brand plus head term, inside 30 characters.
• Short description: one benefit sentence. Extra keywords won't rank.
• Full description: use cases up front, then coverage.
• Density: exact phrases three to five times; any single keyword around 2% to 3%, never above about 5%. Google publishes no number.
• Localization and testing: native listings per language; localized experiments for copy, with rank tracked separately.

Check your draft in the free Keyword Density Checker and Metadata Character Counter. For a field-by-field review across every market, book a free 30-minute call, or start with the fixed-price ASO audit.