Google Play

Google Play keyword custom store listings: how to use Gemini drafts and the new metrics

Google Play can now draft a custom store listing for a search keyword with Gemini. Here is how keyword listings work, what the Console reports, and how to test them.

Google Play lets you show a different store listing to people who find your app through a chosen search keyword. At Google I/O in May 2026, Google added a shortcut: click a keyword recommendation on the Grow overview page and Gemini builds a tailored custom listing that you can deploy in one click.

For small teams this is the most practical Google Play ASO lever of the year, because it turns keyword research into a listing change without a designer or a translator. It is also easy to misuse. This guide explains how keyword listings work, what the Console now reports, and a safe way to test them.

How keyword-targeted custom listings work

A custom store listing is an alternate version of your Play page. According to Google's Play Console Help, you can create up to 50 of them, and your original listing becomes the default that everyone else sees. Each custom listing can target one audience type.

Audience typeWho sees the listing
Country or regionUsers in the countries you assign (a country can belong to only one custom listing)
User stateChurned, lapsed, non-buyer, repeat buyer or pre-registered users, among others
Search keywordsUsers who find your app on Play through the search terms you choose
Ads trafficUsers arriving from your ads (needs approval)
Unique URLAnyone who opens your link with a unique parameter

For keyword listings, you pick the audience type Search keywords, then choose terms from the suggested list or search for new ones. You can review spelling variations and translations of each keyword bundle. Play may also offer to write descriptions with Gemini, based on your default listing and the chosen keywords. You can edit or discard the suggestion.

What Gemini does and does not do for you

The Grow overview flow starts from a recommended keyword and produces a draft listing. Google's I/O announcement also says Gemini can pre-populate store listings in several languages from a CSV or Google Sheet for you to review.

Treat every draft as a first version. One developer who tried the flow reported on DEV Community that description generation failed once and asked them to retry later, so do not build a process that depends on it. More importantly, a draft written from keywords tends to repeat those keywords. Google's own guidance for the short description (80 characters) warns against unnecessary keywords added to improve search results, saying they do not help ranking and give users a poor experience.

The metrics changed, so set a new baseline

Third-party ASO agency Moburst reports that Play Console store listing performance now centres on unique users who click Install, Open or Pre-register, with Conversion Analysis showing visitors, clicks and click-through rate instead of acquisitions and conversion rate. That source also dates the change to around July 2026 but gives two different timings, and the Google documents reviewed here do not describe it, so check the exact date in your own Console before you annotate reports.

Google's I/O post lists the related additions: a Reach metric for total visibility on Play, traffic source breakdowns that show downstream engagement, retention and monetization, and cart conversion rates in the core performance metrics. Custom listing data only appears in the store listing performance report once a listing has enough visitors, so small listings may show nothing for a while.

A safe way to test a keyword listing

  1. Pick one keyword bundle that already brings some traffic and has a clear intent, such as a specific feature or use case.
  2. Create the custom listing from your default listing, change only the elements that match that intent (the opening description lines and the first screenshots), and keep the rest identical.
  3. Write down the date and your current reach, clicks and click-through rate for that keyword before you publish.
  4. Wait until the listing has enough visitors to appear in the report, then compare click-through rate and, using traffic source breakdowns, retention for the Search source.
  5. Keep the winner, retire the loser, and move to the next keyword bundle.

Write for AI search as well as keywords

Google also announced Ask Play, a conversational search overlay that handles follow-up questions, and discovery of apps inside the Gemini app. Appbot argues in its May 2026 analysis that keywords are now one signal among many and that clear statements of purpose, audience and use cases matter more than repetition. Google has not published which sources Ask Play draws on, so that is an informed view, not a confirmed rule.

The practical conclusion is cheap to act on: describe what the app does in plain sentences, keep the description consistent with your screenshots and reviews, and reply to reviews in public.

What to do now

  • Open Grow users, then Store presence, then Custom store listings, and check that a default listing is published first.
  • Create one keyword listing for your best search term and edit the Gemini draft by hand.
  • Update dashboards that still assume conversion rate, and label the date Console switched to click-through rate.
  • Review the traffic source breakdown to see whether Search users retain better than other sources.
  • Rewrite the first lines of your default description in plain language for Ask Play and Gemini.
  • Add translations yourself where needed, because custom listings are not translated automatically.

App Traction tracks keyword rank on Google Play search and the history of your store listing changes next to ratings and traffic, which helps you see whether a custom listing moved anything. See Google Play ASO, and read App Store vs Google Play ASO for how the two stores differ.

Frequently asked questions

How many custom store listings can I create on Google Play?

Google's Play Console Help says up to 50. Your original listing becomes the default shown wherever no custom listing applies.

Are custom store listings translated automatically?

No. Google states that listings are not automatically translated, so you pick a default language and add translations yourself.

Does Gemini write the listing for me?

Play may offer to generate descriptions from your default listing and chosen keywords. You can edit or discard them, and a draft should be reviewed before you publish.

Sources