Google Play vs App Store metadata, what differs
A field-by-field comparison of Google Play and App Store metadata, from titles and keyword fields to screenshots, experiments and custom pages, with practical advice for each store.

On this page
For search, the App Store reads the app name, the subtitle and a hidden 100-character keyword field, and does not use the description. Google Play has no keyword field and reads the title, short description and full description instead. Visual assets, update rules, experiments and custom pages differ as well, so a listing copied unchanged from one store to the other leaves results on the table.
Key takeaways
- Both stores give you a 30-character title, but the supporting fields differ: a 30-character subtitle and a 100-character keyword field on the App Store, an 80-character short description and a 4,000-character full description on Google Play.
- Write the App Store description for people, and the Google Play description for people and search.
- Google Play lets you change listing text and graphics at any time. On the App Store most metadata changes ship with a new app version, with promotional text as the main exception.
- Both stores support A/B tests and audience-specific pages, with different scopes.
- Plan metadata per store and per country, not once.
Side by side
The table reflects each store's rules as of November 2026.
| Field | App Store | Google Play |
|---|---|---|
| Title | App name, up to 30 characters, used for search | Title, up to 30 characters, used for search |
| Subtitle versus short description | Subtitle, up to 30 characters, used for search | Short description, up to 80 characters, used for search and shown to visitors |
| Keyword field | 100 characters, hidden from users, comma separated | No keyword field |
| Description indexing | Up to 4,000 characters, not used for search ranking | Up to 4,000 characters, used for search |
| Promotional text | Up to 170 characters, editable without a new version, not used for search | No equivalent field, promotional content covers time-limited events and offers |
| Feature graphic | None | 1024 x 500 banner used in featured placements |
| Screenshots | Up to 10 per device size | 2 to 8 per device type |
| Video | Up to 3 app previews per localization, up to 30 seconds each | One YouTube promo video |
| Categories | A primary and an optional secondary category | One category plus up to 5 tags |
| In-app purchase names | Promoted in-app purchases can appear on the product page and in search results | Not a documented search factor |
| Release notes | What's New text, not documented as a search factor | Up to 500 characters per language, not documented as a search factor |
| Updating without a release | Promotional text, plus in-app events, custom product pages and test treatments, which are reviewed separately | All listing text and graphics, subject to review |
| Experiments | Product page optimization, up to 3 treatments of the icon, screenshots and previews against the original | Store listing experiments, up to 3 variants of graphics and localized text against the current listing |
| Custom pages | Custom product pages with their own URLs, and since 2025 keywords can be assigned so they can appear in search | Custom store listings by country, by URL, for pre-registration and for other audiences |
Practical advice per field
Title
Both stores give you 30 characters, so lead with your brand and add your single most important keyword if it reads naturally. Google Play's metadata policy bans words that suggest store performance or promotion in the title, such as "best", "#1" or "free", and it bans emoji there too. Apple's guidelines rule out packing metadata with trademarked terms, popular app names or pricing information.
Subtitle and short description
The App Store subtitle has 30 characters and counts for search, so use it for a second keyword and a clear benefit rather than repeating the name. Google Play's short description has 80 characters and is both read by search and seen by visitors, so write one natural sentence that contains your main term and says what the app does.
Keyword field
The App Store's 100-character keyword field has no Google Play equivalent. Separate terms with commas and no spaces, skip words already in your name or subtitle, and leave out competitor names. Our App Store keyword field guide goes deeper.
Descriptions
Apple does not use the description for App Store search ranking, so write it to convert. Only the first lines show before the "more" link, so lead with the main benefit. On Google Play the full description counts for search. Cover your shortlist of terms in natural sentences, mention the most important ones a few times where they fit, and use short paragraphs and lists. Google Play's metadata policy prohibits keyword lists, repetition that serves no reader and anonymous user testimonials in the description.
Promotional text and its Google Play counterparts
App Store promotional text sits above the description, holds 170 characters and can change at any time without a new version, but it is not used for search. Use it for timely messages such as an event, a sale or a new feature. Google Play has no such field. The closest tools are promotional content for events and offers, and the short description, which you can update without a release.
Visual assets
- Feature graphic. Google Play only. Keep it simple, and keep key elements away from the edges in case a placement crops it.
- Screenshots. On the App Store, the first three portrait screenshots, or an app preview, can appear in search results, so they carry most of the weight. On Google Play, make the first screenshots tell the story on their own. Our screenshot best practices cover layouts and captions.
- Video. App Store previews autoplay without sound on the product page and in search results, so the first seconds must work silently. Google Play takes a YouTube link, so the video lives on YouTube.
Categories and tags
On the App Store your primary category matters most: it decides where you appear when people browse and which category charts you can rank in. On Google Play, pick one category and up to five tags that describe your app's content and features accurately. Our guide to choosing the right app category covers the trade-offs.
In-app purchase names and release notes
On the App Store, promoted in-app purchases have their own display names and images and can show on the product page and in search, so name them for what the user gets. Neither store documents release notes as a search factor, but people who check updates read them. Replace "bug fixes and improvements" with one specific line about what changed.
Update rhythm
On the App Store, metadata changes ride on app releases, so plan one meaningful metadata change per release where you can and note what changed. On Google Play you can edit whenever you like, but the same discipline applies: one change, then two to four weeks of rank and conversion data before the next. Our guide on measuring the impact of ASO changes explains how to read the result.
Experiments and custom pages
Test before you roll out, with product page optimization on the App Store and store listing experiments on Google Play. For campaigns and distinct audiences, use custom product pages and custom store listings. Our guide to store listing experiments and custom product pages walks through both.
Common mistakes when you port a listing
- Copying the App Store description to Google Play. It was written for people only, so your search terms may be missing from the one store that reads the description.
- Copying a keyword-heavy Google Play description to the App Store. It does nothing for App Store search and reads worse for visitors.
- Repeating title words elsewhere. On the App Store, words already in the name gain nothing from a second appearance in the subtitle or keyword field.
- Forgetting localizations. Each App Store localization has its own name, subtitle, keyword field and screenshots, and Google Play takes translated text and graphics per language. Research terms per language rather than translating them, as our guide to localization for ASO explains.
- Leaving time-bound copy in place. Promotional text about an event that ended last month tells visitors the listing is not maintained.
How AppMetis helps
The AppMetis ASO tools check your title, subtitle and descriptions against each store's limits and best practice with a metadata score, suggest keywords from store autocomplete and our rank data, and track your keyword ranks daily, so you can see whether a metadata change moved anything. The free keyword pages show which apps rank for a term in each country we cover.
Next steps
Put your current listings side by side using the table above, and mark every field that is empty, duplicated across fields or written for the wrong store. Fix the search fields first, then the conversion assets, then start testing. The ASO checklist for 2026 and the glossary entry on metadata cover the rest.
