ASO in 2027: what changes on Google Play and how to prepare

The short answer: 7 shifts for ASO in 2027

ASO in 2027 is still about being found and chosen on Google Play, but the inputs are changing. The biggest shifts, based on Google's own announcements up to September 2026:

1. Search becomes a conversation. Ask Play, AI review summaries and app discovery inside Gemini reward listings that answer intent, not listings that repeat keywords.
2. Technical quality is a visibility gate. Battery (wake locks) joined crashes and ANRs in 2026; memory and code optimization follow in February 2027.
3. Many listings, measured by clicks. Keyword-targeted custom store listings that Gemini can generate, and reports built on install clicks, click-through rate and reach.
4. AI makes localization cheap. Gemini translates app strings and pre-fills listings in other languages, so everyone can localize. Quality becomes the difference.
5. Your listing becomes a content channel. Promotional content, carousels, Play Shorts and Engage SDK content put fresh material on and around the listing.
6. Identity, trust and review integrity. Developer verification starts in four countries on September 30, 2026 and goes global in 2027; AI-generated assets get labels; spam reviews are filtered at scale.
7. New rules by country. In the US, listings are shared with third-party stores and external links are allowed; age-verification laws add obligations in some states.

How to read this guide

Every statement about Google Play is labelled, so you know how much weight to give it:

• Now Already true, checked against an official Google source (linked).
• Announced Google has announced it with a date, but it isn't fully in effect yet. Dates are as Google states them.
• Prediction Our reasoning about where things are going. Treat it as an informed guess, not a fact.

We checked all sources in late September 2026. Google changes Play features often, so we will update this page, at the latest after Google I/O 2027.

1. Search becomes a conversation: Ask Play, review summaries and Gemini

What it is

Now Google Play already shows AI-generated content on listings. Google's December 2024 year-end post says it integrated Gemini models for AI-generated app review summaries, FAQs and app highlights. Play Console Help explains that review summaries are built from common themes in your reviews, need enough similar reviews around more than one theme, and that users may see them on your listing in English.

Now Discovery also happens outside the store. Inside the Gemini app on Android, the Google Play connected app lets people ask for app suggestions, find and install apps, and buy in-app items. It requires users aged 18+ with Keep Activity on.

Announced At I/O 2026 (May 19, 2026) Google described Ask Play as an AI-powered overlay that "turns discovery into a natural conversation", understands the full context of a question and adapts to follow-ups. It added Ask Play highlights, a summary of complex searches on the results page. The same post said app discovery in the Gemini app on Android and the web would arrive "in the coming weeks", with entertainment content and deep links into apps later. Google hasn't published how widely each of these has rolled out by country or language, so check what your users actually see.

Why it matters

Classic Play search matches a short query ("budget app") against your title and descriptions. A conversational query is longer and more specific ("an app to split rent with roommates that works offline"). The AI has to decide whether your app is a good answer, and Google doesn't document which inputs it uses.

Prediction We expect the listing text, review themes and in-app content you expose to Google (for example through deep links and the Engage SDK) to feed these answers. Our reasoning: those are the only structured sources Google has about what an app does, and review summaries already turn reviews into listing content. If that holds, a listing that plainly states who the app is for, what problems it solves and what it doesn't do will be easier to recommend than one built around keyword repetition.

Keywords don't disappear. Play Console itself now recommends keywords and builds listings for them (see shift 3). What changes is that keywords become the vocabulary of a clear explanation instead of the explanation itself.

What to do now

• Rewrite the first two lines of your full description as a direct answer: what the app does, for whom, and the one reason to pick it.
• Add a short "Who it's for" or "What you can do" block with the real use cases people describe in reviews and support emails. Use their words.
• Read your review themes monthly. Negative themes can end up in an AI summary on your listing, so fix the causes and reply to the reviews (see the ratings guide).
• Test your category the way users do: ask Gemini (and Ask Play, where you have it) the questions your users would ask, and note which apps it suggests and why.
• Check keyword coverage without stuffing. The Play Store ASO Tweak extension shows the character budget of each field and 1, 2 and 3-word keyword density on any listing, so you can compare your wording with the apps that get recommended.

2. Technical quality is a visibility gate

What it is

Now Google's Android vitals documentation states that core vitals affect your app's visibility on Google Play. If an app exceeds a bad behavior threshold, Play "may reduce the visibility of your title" and "may also show users a warning on your store listing". Play assesses the last 28 days. The current core vitals and overall thresholds are:

For wake locks, Google's November 2025 announcement said that from March 1, 2026 titles that miss the threshold may be excluded from prominent discovery surfaces such as recommendations, and may get a battery-drain warning on the listing.

Announced Play Console's technical quality requirements page lists what comes next, and says that not meeting a requirement "can affect an app's visibility and publishing capabilities":

• February 2027: memory usage thresholds and a minimum of 25% DEX code optimization (R8 or an equivalent shrinker) for app uploads above the size limits.
• April 2027: apps that support sign-in must support Zero-Tap Sign-In restoration, so users stay signed in after moving to a new device. Games and enterprise apps are exempt.

Now The same page lists 64-bit and 16 KB memory page size support as current requirements. The target API level rule requires new apps and updates to target Android 16 (API level 36) from August 31, 2026, with extensions available to November 1, 2026. Existing apps must target at least Android 15 (API level 35) to stay available to new users on newer Android versions.

Why it matters

This turns engineering metrics into ASO metrics. An app that crashes, drains battery or uses too much memory can lose recommendation traffic and show a warning that hurts conversion, whatever its keywords. A new phone owner who has to log in again after switching devices is also a churn risk, which is why Zero-Tap Sign-In restoration becomes a requirement.

Prediction The list of quality signals keeps growing: stability (crashes, ANRs), then battery (2026), then memory and code size (2027). We expect more of Android vitals to move from "report" to "visibility factor", and ASO owners to need a seat in release planning.

What to do now

• Open Android vitals and check every core vital, overall and per device model. Fix any metric near a threshold before your next big marketing push.
• Check memory and DEX optimization now. February 2027 is only a few releases away; make sure R8 (or another shrinker) runs on release builds, and measure memory on low-RAM devices.
• If your app has sign-in, implement Zero-Tap Sign-In restoration with the Restore Credentials API before April 2027.
• Keep your target API level current, and make sure your extension (if you asked for one) doesn't lapse.
• Add vitals to your ASO report next to rankings and click-through rate. When visibility drops without a listing change, check vitals first.

3. Many listings, measured by clicks

What it is

Now Custom store listings let you show different text and graphics to different audiences. Targets include country or region, pre-registration, search keywords, ads traffic, several churned and lapsed user groups, buyer segments and custom audiences, with up to 50 custom listings per app. For keyword targeting, Play Console shows keywords known to bring you traffic, and can offer to "Generate descriptions using Gemini" from your default listing and the keywords you choose.

Announced At I/O 2026 Google went further: when you click a keyword recommendation on the Grow overview page, "Gemini creates a new custom store listing automatically tailored to that keyword—ready to deploy with just one click." Google didn't state a rollout schedule for this.

Now Measurement changed too. According to Play Console Help, since June 2026 store listing performance is based on unique clicks: users who tap Install, Open or Pre-register on your listing. Click-through rate (CTR) replaces the legacy conversion rate. Completed acquisitions are still available on the Grow users overview page, in Statistics and in downloadable reports. I/O 2026 also added a reach metric for your app's total visibility on Play.

Now Store listing experiments still let you A/B test the default and custom listings.

Why it matters

Keyword-targeted custom listings are the closest thing Google Play has to landing pages per search intent. Someone searching "offline maps for hiking" and someone searching "GPS speedometer" can see different first screenshots and a different short description from the same app. With Gemini drafting the text, the cost of creating these listings is close to zero, so competitors will have them too.

Click-based metrics also isolate what the listing controls: the moment of intent. A failed download or a slow install no longer hides a good listing.

Prediction Because AI makes drafting free, the advantage moves to choosing the right keywords and proving which listing wins. Teams that combine custom listings with experiments and read CTR by traffic source will pull ahead of teams that accept every generated draft.

What to do now

• List your 5 to 10 highest-intent search terms (the keyword research guide shows how) and create a custom listing for the top 2 or 3 that need a different pitch.
• Treat Gemini drafts as drafts. Check claims, tone and policy before publishing. Metadata policy still applies: a 30-character title, and no ranking or price claims, emojis or ALL CAPS in the title.
• Rebuild your dashboards around unique install clicks, CTR by traffic source (search, explore, ads and referrals) and the new reach metric. Keep acquisitions for business reporting.
• Run one experiment at a time per listing, starting with the first screenshot and the short description, and let it run long enough to reach a result.
• Save a snapshot of your listing before each change. The extension exports a listing as text or data files plus its images, which makes before and after comparisons easy.

4. AI makes localization cheap

What it is

Now Play Console can translate app strings with Gemini at no cost. When you upload a bundle to a draft release, translations of your strings.xml are generated and added, and you can preview and edit them. Free machine translation of store listings is available for a set of languages, and users can view an automatic translation of a listing that has no translation in their language.

Now At I/O 2026 Google said you can upload a structured file (such as a CSV or Google Sheet) and "Gemini models enable Play Console to pre-populate your listings across different languages for your review."

Why it matters

For years, localization was a real advantage because it cost money and time. When translation is free and automatic, most apps in a category can appear in dozens of languages. Coverage stops being a differentiator; relevance is what's left.

Prediction Direct translations rarely match what people search for in each language, and they don't change screenshots. We expect the winners in each market to be apps that research local keywords, use local examples and show localized screenshots, while machine-only listings converge on the same generic text.

What to do now

• Before localizing, confirm the app is actually available in the target market. The free Country Availability Checker scans 141 Google Play markets, and this guide explains why an app can be missing from a country.
• Use Gemini translations as the first draft, then have a native speaker review the title, short description and first screenshot captions of your top 3 to 5 markets.
• Redo keyword research per language instead of translating your English keywords.
• Localize screenshots for the markets that matter most. They carry more of the conversion than the description does.
• Check what users in each country really see. The extension's country and language switcher reloads a listing for another market and language and shows whether the app is available there.

5. Your listing becomes a content channel

What it is

Now Several features put changing content on and around your listing:

• Promotional content (formerly LiveOps): events, offers and major updates shown on your listing and, if featured, on Home and search. It is available for all games and for apps that meet the Premium growth tools criteria. You can submit up to 60 days ahead; approval can take up to 4 days, and featuring requests need 14 days.
• Carousels: since July 2025, all app developers can add a hero content carousel and a YouTube playlist carousel to their store listings.
• Engage SDK: brings your in-app content (continue watching, recommendations) to Collections and other Google surfaces. Google says Engage SDK surfaces reach over 30 million monthly active users and drive millions of app opens a month.
• Play Points: in October 2025 Google added consolidated Play Points reporting and, for games in the Level Up program, Play Points coupons on the You tab.

Announced At I/O 2026 Google announced Play Shorts, a full-screen short-form video feed, rolling out to US users and select developers first, and said Engage SDK content would appear directly on store listings, expand to Android tablets and cover over 80 Play markets. Check Play Console for what's available to your app.

Why it matters

A static listing is the same every day. These features let the listing reflect what's new in the app, which gives returning visitors and lapsed users a reason to come back, and gives Google fresh material to show on its own surfaces.

Prediction Video and in-app content will count for more in discovery as Play adds feeds such as Play Shorts. Apps without a real video or regular updates will have less to offer these surfaces.

What to do now

• Plan a simple content calendar: one promotional content event per real update or seasonal moment, submitted at least 14 days ahead if you want it featured.
• Make one honest 20 to 40 second video of the app in use, and add a YouTube playlist carousel if you publish tutorials.
• If your app has content people return to (media, courses, shopping, travel), evaluate the Engage SDK.
• Set up deep links and verify them on Play Console's Deep links page, so promotions, Gemini and Engage surfaces can open the right screen.

6. Identity, trust and review integrity

What it is

Announced Android developer verification takes effect on September 30, 2026 for users in Brazil, Indonesia, Singapore and Thailand, on certified devices running Android 7 and above, across Google Play and several other app stores. Apps must be registered by verified developers to be installed and updated there. Google says it will expand this globally in 2027. According to Google's June 2026 update, most Play developers are already verified and over 99% of their apps were registered automatically; the rest can be registered from the Play Console Home page.

Now Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers for 14 days before they can publish to production.

Now Play Console asks you to declare AI-generated images and videos in store listings and promotional content. Google says declared assets "will be AI-labeled on the Google Play Store and other surfaces where used."

Now Enforcement is large-scale. In its 2025 safety report (February 2026), Google said it prevented over 1.75 million policy-violating apps from being published, banned more than 80,000 bad developer accounts and blocked 160 million spam ratings and reviews.

Why it matters

Ratings and reviews are the most visible trust signal on a listing, and Google filters fake ones at scale. Buying reviews or gating them was always against policy; it is now also increasingly likely to be caught and removed, often along with the rating it was meant to lift. Verified identity and AI labels move trust from "take our word for it" to something Google can check and show.

Prediction AI labels on screenshots will matter most in categories where users need to trust what they see (photo editors, games, shopping). We expect real in-app screenshots to convert better there than generated art, though Google hasn't published data on this.

What to do now

• Check the Play Console Home page for any app that still needs registering, especially apps you also distribute outside Google Play.
• Ask for ratings only through the In-App Review API, after a positive moment. Don't ask "Do you like the app?" first, don't put the prompt behind a button, and never offer rewards. The ratings guide has the details.
• Declare AI-generated assets honestly, and prefer real screenshots for your first two images.
• Keep your Data safety form, privacy policy and permissions consistent with what the app does. The extension shows these, grouped, on any listing, so you can compare yours with the category norm.
• If you monetise with ads, keep a developer website on your listing and a correct app-ads.txt at its root: that is how AdMob and other buyers verify authorised sellers.

7. New rules by country

What it is

Now In the US, after the Epic v. Google court order, Google stopped prohibiting developers from linking users to external downloads and transactions, and from offering other in-app payment methods, from October 29, 2025. Since December 2025 these options run through programs that include service fees. From July 22, 2026, unless you opt out in Play Console (Settings → Catalog settings), Google Play provides your US app name, icon, description, screenshots and videos to third-party US Android app stores enrolled in its program.

Now Age-verification laws for app stores are arriving in US states. Google Play says Texas SB 2420 is now in effect after an appeals court stayed an injunction, and offers the Play Age Signals API (beta) to help apps get age signals for eligible users. Google notes that similar laws are coming in other states.

Now Regional rules also affect where you can be found at all: device targeting, legal removals and local requirements. The country availability guide covers them, and the removed-app guide covers what happens after a policy removal.

Why it matters

Your US listing text and screenshots may now appear in other stores, so they have to work without Google Play's layout around them. Age rules can change which users see or buy what in some states. None of this is keyword work, but all of it changes who can find and install your app.

What to do now

• Decide deliberately about US catalog sharing in Play Console instead of accepting the default.
• If you serve US users and sell digital goods, review the external links and alternative billing programs with someone who understands the fees and reporting.
• If your app may have users under 18 in affected states, read Google's state-law page and check whether you need the Age Signals API.
• Audit your market coverage twice a year, for your app and your main competitors.

Timeline of dated changes

Dates as Google has published them, plus one clearly marked prediction:

1. Mar 1, 2026 Now Excessive partial wake locks can reduce visibility and add a battery warning.
2. Jun–Jul 2026 Now Store listing reports switch to unique clicks and CTR.
3. Jul 22, 2026 Now US listings shared with third-party US stores unless you opt out.
4. Aug 31, 2026 Now New apps and updates must target API level 36 (extensions to Nov 1, 2026).
5. Sep 30, 2026 Announced Developer verification enforced in Brazil, Indonesia, Singapore and Thailand.
6. Feb 2027 Announced Memory and DEX code optimization thresholds can affect visibility.
7. Apr 2027 Announced Zero-Tap Sign-In restoration required for apps with sign-in.
8. 2027 Announced Developer verification expands globally.
9. Aug 2027 Prediction A new target API level deadline, if Google keeps its yearly pattern. Not announced as of September 2026.

What doesn't change

Now The basics still hold, and most apps still get them wrong:

• Google Play has no hidden keyword field. It reads your title (30 characters), short description and full description, and the metadata policy still bans repetitive or unrelated keywords, ranking claims and emojis in titles.
• Your icon and first screenshots still do most of the converting.
• Ratings are still weighted towards recent ratings, so fixing today's problems shows up in the rating users see.
• Competitor research is still the fastest way to learn what works in a category. The competitor research guide shows a repeatable method, and the ASO glossary explains the terms.

If you're new to ASO, read What is ASO? The Google Play guide first; this page assumes the basics.

The 2027 ASO checklist