Storeboard

Storeboard/Blog/Google Play ASO

Google Play ASO: how indie devs optimize for Play, not just Apple

ASO By Sanket Singh · 12 November 2026 · 6 min read

Google Play ASO cover: a made-up app called Sip: Water Reminder with its 30-character title, 80-character short description and 4,000-character full description, tagged No keyword field and A/B tests built in

Google Play ASO is the work of getting your Android app found and installed on Google Play, and it isn't a copy of your App Store listing. Play has no keyword field: your 30-character title, 80-character short description and 4,000-character full description carry the words people search for. It also has built-in A/B tests, and it can show your app less if it crashes too often. Most of what I've written here is about the App Store, so this is the Play side for indie developers shipping on both: what's different, where the keywords go, what graphics Play wants, how to test without guessing, and what my own app does for Play today.

Checked against Google

Every rule here comes from Google Play Console Help, Google Play policy and Android Developers documentation, read on 12 November 2026. Google doesn't publish a full list of Play ranking factors, so I only say what Google itself says.

On this page

  1. How is Google Play ASO different from App Store ASO?
  2. Where do keywords go if Play has no keyword field?
  3. What screenshot sizes and assets does Play expect?
  4. How do you test a Play listing without guessing?
  5. What can Storeboard do for a Play listing today?
  6. Questions

How is Google Play ASO different from App Store ASO?

The goal is the same, but the fields, the testing tools and even the ranking signals are different. The biggest difference: the App Store has a hidden keyword field, and Google Play doesn't.

App StoreGoogle Play
Name30 charactersTitle, 30 characters
Line under the nameSubtitle, 30 charactersShort description, 80 characters
Hidden keywordsKeyword field, 100 charactersNone
Long description4,000 characters. Not on Apple's list of search factors4,000 characters, written for people, in everyday language
Change text without an updateOnly promotional textThe whole listing, in Play Console
Banner graphicNone1024 × 500 feature graphic
Built-in A/B testsProduct page optimizationStore listing experiments
App quality and visibilityNot on Apple's listCrash and ANR rates over Google's thresholds can reduce visibility
What store search reads. App Store: app name, 30 characters; subtitle, 30; keyword field, 100, hidden; primary and secondary category; plus downloads, ratings and reviews. Google Play: title, 30 characters; short description, 80; full description, 4,000; no keyword field; and Google's advice to use everyday language, not keyword lists.

Two things follow from that table. You can't copy your App Store listing across and call it done, because your App Store keywords live in a field Play doesn't have. And Play rewards you for iterating, because you can change and test the listing whenever you like.

Where do keywords go if Play has no keyword field?

Into your title, short description and full description, written as normal sentences. Google's guidance is direct: describe your app "using everyday language, not a list of keywords", and its metadata policy bans "repetitive or unrelated keywords".

A useful habit if you ship on both stores: keep a list of the terms your App Store keyword field targets, and check each one appears somewhere sensible in your Play text. That's a different job from stuffing them in, and it's the one that actually helps.

What screenshot sizes and assets does Play expect?

Screenshots between 320 and 3,840 pixels a side with a long side no more than twice the short one, a 1024 × 500 feature graphic and a 512 × 512 icon. The full detail is in my Google Play screenshot size guide and the icon size table, so here's only what matters for ASO.

Raw phone captures often break the 2:1 rule. 1080 by 1920 has a ratio of 1.78, fits, and meets the promotion minimum. 1080 by 2400, a common 20:9 Android capture, has a ratio of 2.22 and is too tall. 1320 by 2868, an iPhone 6.9-inch screenshot, has a ratio of 2.17 and is too tall.

How do you test a Play listing without guessing?

With store listing experiments, which are built into Play Console at no extra cost. For a small team they're one of the biggest advantages Play has: you can test a new icon or screenshot set on real visitors before committing to it.

Google Play A/B tests: test 2 variants against your current listing; run one default graphics test or up to five localized ones at a time; default tests cover the icon, feature graphic and screenshots; localized tests can include descriptions in up to five languages; experiments end after six months; and you can create up to 50 custom store listings for different audiences.
Crashes cost you Play visibility: a user-perceived crash rate over 1.09% overall, or 8% on any single phone model, and a user-perceived ANR rate over 0.47% overall, or 8% on any single phone model, are bad behavior thresholds. Play checks a 28-day average daily, and over the line it may reduce visibility and show a warning on your listing.

One more Play-only factor before you test anything: app quality. Google says core Android vitals "affect your app's visibility on Google Play". If your user-perceived crash rate goes over 1.09% overall (or 8% on any single phone model), or your ANR rate over 0.47% (or 8% on one model), "Play may reduce the visibility of your title" and may show users a warning on your listing. Play judges this on a rolling 28-day average. No listing test will beat a crash fix.

Five mistakes when porting an App Store listing to Play

  1. Pasting the keyword field into the description. A comma list of terms is exactly the "word blocks" Google's metadata policy calls out.
  2. Leaving the short description as an afterthought. It shows in search results, so it's closer to your App Store subtitle than to your description.
  3. Reusing iPhone screenshots. They fail the 2:1 rule, and an iPhone frame on an Android listing looks out of place anyway.
  4. Copying ranking or price claims. "#1", "Best" and "10% off" are banned in Play's title and graphics, just as price words cause trouble on the App Store.
  5. Translating the App Store text word for word. Play's fields are different lengths, so a translated 30-character subtitle doesn't make an 80-character short description.

A Play listing checklist

What can Storeboard do for a Play listing today?

It makes the Play listing from the App Store work you've already done, and exports it for Play Console. It doesn't publish to Google Play directly.

Storeboard: ASO Assistant is my Mac app for App Store listings, and Google Play is part of Storeboard Pro. Turn it on and you get:

To be clear about the limits: it doesn't make tablet, Chromebook, Wear OS or TV screenshots, it doesn't run Play experiments, and you upload the export in Play Console yourself. For the free side of keyword research, the keyword check on this site works on the App Store, and Play Console's own acquisition reports show how people find your Play listing.

Make the Play listing from your App Store one

Storeboard: ASO Assistant (Pro) adds an Android phone set that starts from your iPhone screenshots, the 1024 × 500 feature graphic and your Play title, short and full description in every language, exported ready for Play Console. Free to start on the Mac App Store, Pro is a one-time US$49.99.

Google Play screenshot sizes Download Storeboard free

Questions

Can I copy my App Store description onto Google Play?

You can start from it, but don't stop there. Google Play has no keyword field, so the terms in your App Store keyword field need to appear naturally in your Play title and descriptions, and Play's 80-character short description has no App Store equivalent.

Does Google Play have a keyword field?

No. Your title (30 characters), short description (80) and full description (4,000) carry your keywords. Google asks for everyday language, and its metadata policy bans repetitive or unrelated keywords.

Does Storeboard publish directly to Google Play?

No. Storeboard: ASO Assistant exports your Android screenshots, feature graphic and Play listing text ready to upload in Play Console yourself. It publishes directly only to App Store Connect.

Are Storeboard's Play tools part of Free or Pro?

Pro. Storeboard Pro, a one-time US$49.99 purchase, includes Google Play: Android screenshots, the feature graphic and the Play listing.

Do crashes affect Google Play rankings?

Google says core Android vitals affect your app's visibility on Google Play. Above a 1.09% user-perceived crash rate or a 0.47% ANR rate overall, Play may reduce your visibility and show a warning on your listing.

Sources

Pages read on 12 November 2026 (Melbourne time).

Keep reading