Play Store ASO checklist for an Android app in English and Hindi

In short

Play limits: 30-character title, 80-character short description, 4,000-character full description. Hindi (hi-IN) is a supported listing language but not in Google's free machine translation (Play Console Help, 2026).

App store optimisation (ASO) for Google Play is mostly three jobs: write a store listing that follows Google's rules, show the app honestly in the graphics, and keep the app's technical quality above the thresholds that affect how visible it is. This checklist uses Google's own Play Console Help and Android vitals pages, read on 1 November 2026, and adds the steps for a Hindi listing next to an English one. Google does not publish a ranking formula, so nothing below promises a rank. Where a point is our advice and not Google's rule, it says so.

1. Title and developer name

[ ] Keep the app title at 30 characters or less. The limit applies to translations too.
[ ] Make the title describe what the app does, and make it unique.
[ ] Leave out "Free", "No Ads", "#1", "Best" and similar words. Google treats them as deals or rank claims, and they do not belong in titles.
[ ] Do not use capitals unless your brand is written that way, and do not add emojis or special characters.
[ ] Do not imply a link to another company or app.

2. Short and full description

[ ] Write the short description in 80 characters or less. Say the main benefit in plain words. It is the first text users see on the app's page.
[ ] Leave out price, promotions, "download now", awards and download counts.
[ ] Do not stuff keywords. Google says unnecessary keywords added to improve search will not affect ranking and make a bad experience.
[ ] Use the full description's 4,000 characters for facts: what the app does, who it is for, what the main features are. Put the important points in the first few sentences, because users may read only those.
[ ] Do not copy the short description into the full description.
[ ] Do not quote anonymous user testimonials. Name the source of any quote.
[ ] Use the character counters in Play Console while you write.

3. Icon and feature graphic

[ ] Icon: 32-bit PNG with alpha, 512 by 512 pixels, at most 1024KB. No badges or text about rank or price.
[ ] Feature graphic: 1024 by 500 pixels, JPEG or 24-bit PNG with no alpha.
[ ] Keep key elements in the centre of the feature graphic, away from the edges where it may be cut off.
[ ] Avoid prominent branding in the feature graphic that looks like your icon, since the two appear together.
[ ] Add alt text to every graphic, in 140 characters or less, and describe what is shown.

4. Screenshots and video

[ ] Upload at least four screenshots at 1080px or more. For recommendation formats, Google asks for 9:16 portrait (at least 1080 by 1920) or 16:9 landscape (at least 1920 by 1080).
[ ] You can add up to 8 screenshots per device type. Add tablet and Chromebook screenshots if the app supports them.
[ ] Show the real app screens, and put the app's interface in the first three.
[ ] Keep taglines short: no more than 20% of the image.
[ ] Do not put price, offers or rank claims in images ("10% off", "#1").
[ ] Optionally add a YouTube trailer.

5. Hindi listing

[ ] In Play Console, open Store listing, then Manage translations, and add Hindi (hi-IN). Add English (India) en-IN too if your English copy differs from US English.
[ ] Write the Hindi title, short description and full description yourself or with a native speaker. Google's free machine translation does not list Hindi among its languages, and Google says native-speaker translations are best.
[ ] If you order a paid human translation, check on the order screen that Hindi is offered. Google says translations are not available for all language pairs, and quotes prices from USD 0.07 per word.
[ ] If you do nothing, Hindi-language users can choose to see an automated translation of your page, marked as such. Do not rely on it.
[ ] Check the 30, 80 and 4,000 limits on the Hindi text with the Play Console counters. The Metadata policy applies to every translation.
[ ] Make Hindi screenshots and videos if the images contain text. Google says to provide separate ones for each language you support.
[ ] Use words your users really use. Google's guidance is to avoid slang or jargon unless it comes naturally to your target users. Whether to write in Hindi, English or a mix is our advice to settle by how your audience writes.
[ ] Localise the feature graphic's branding text where it makes sense.

6. Test and target

[ ] Use store listing experiments to test icons, feature graphics, screenshots and, in a localised experiment, descriptions. A localised experiment can run in up to five languages.
[ ] Change one asset type at a time so you know what caused a change.
[ ] Run up to 2 variants against the current listing and choose a target metric such as install clicks. Experiments stop after 6 months.
[ ] Use custom store listings for different audiences, such as users from a given country, search keyword or ad campaign. Custom listings do not get automated translations, so add your own Hindi text.

7. Technical quality

[ ] Track the user-perceived crash rate. Google's bad-behaviour threshold is 1.09% of daily users overall, and 8% on a single device model.
[ ] Track the user-perceived ANR rate. The threshold is 0.47% overall and 8% on one device model.
[ ] Remember the effect: above these thresholds the app is likely to be less discoverable, and a warning may appear on its page. Google generally uses the last 28 days of data.
[ ] Check crash and ANR rates per device model, since one model above its threshold counts on its own.

8. Monthly routine

[ ] Re-read the listing against the Metadata policy for every language.
[ ] Remove time-bound claims and old festival graphics.
[ ] Review experiment results and vitals.
[ ] Update screenshots after every large UI change.

Questions people ask

What are the Play Store character limits?

Google's pages give 30 characters for the title, 80 for the short description and 4,000 for the full description.

Can I use Hindi keywords in my English listing?

Google's pages do not address that. They say unnecessary keywords will not affect ranking and hurt the experience, so write natural text and put Hindi copy in a Hindi translation.

Does Google translate my listing into Hindi automatically?

If you have not added a translation, users can choose to view an automated translation, marked as automatic. Google says native-speaker translations are best.

Does app quality affect how visible my app is?

Google says an app above the Android vitals bad-behaviour thresholds is likely to be less discoverable on Google Play.