Google Play store listing experiments: how to A/B test your listing
Play Console’s free A/B testing, explained: what you can test, how many variants, default vs localized experiments, how to write a hypothesis, how long to run, how to read results and the mistakes that create false winners.
Key takeaways
- Store listing experiments are free and built into Play Console.
- Test up to three variants against your current listing.
- Default graphics experiments test graphics in your default language; localized experiments can also test text, in up to five languages.
- Test one idea per variant, run at least a week, and wait for a conclusive result.
- Experiments measure conversion — track keyword rankings separately when you change text.
Guessing which icon or screenshot converts best is expensive. Store listing experiments let you show different versions of your listing to different visitors and measure which one gets more installs — for free, on real Google Play traffic. Used well, they are the most reliable way to improve conversion.
What you can test
| Element | Default graphics experiment | Localized experiment |
|---|---|---|
| App icon | Yes | Yes |
| Feature graphic | Yes | Yes |
| Screenshots | Yes | Yes |
| Promo video | Yes | Yes |
| Short description | — | Yes |
| Long description | — | Yes |
Setting up an experiment
- In Play Console, go to Store presence → Store listing experiments and create a new experiment.
- Choose the type: default graphics or localized.
- Pick the element to test and upload up to three variants.
- Choose the share of visitors who see the experiment (many teams start around 50%).
- Launch, and don’t change your listing while the experiment runs.
Write a hypothesis first
A good experiment starts with a reason. “Variant B will win because…” forces you to test ideas, not random pixels.
“Let’s try a blue icon.”
“A first screenshot that shows the result (a finished budget) will convert better than one showing the empty home screen, because visitors decide on outcomes.”
How long to run and how to read results
- Run for at least 7 days to include weekdays and weekends.
- Wait until Play Console reports a conclusive result; don’t stop early because one variant looks ahead on day two.
- Small apps need longer — fewer visitors means more time to reach confidence.
- After applying a winner, check retention and ratings too: a variant that attracts the wrong users isn’t a real win.
What to test first
- Screenshot one (biggest impact on conversion).
- Icon.
- Short description (localized experiment).
- Screenshots two and three.
- Promo video vs no video.
- Test one idea per variant.
- Test big differences first.
- Keep a log of every experiment and result.
- Re-test winners occasionally as the market changes.
- Change several elements in one variant.
- Stop at the first sign of a winner.
- Edit your listing during an experiment.
- Assume a win in one country applies everywhere.
+Are store listing experiments free?
Yes. They’re built into Play Console at no cost.
+How many variants can I test?
Up to three variants against your current listing in one experiment.
+Can I test my app title?
Store listing experiments focus on graphics and descriptions. Title changes are best measured by tracking keyword positions and conversion before and after.
+How much traffic do I need?
There’s no fixed number; lower-traffic apps simply need to run experiments longer to reach a conclusive result.
Sources
Specifications and figures are as published by Google and the listed sources at the time of writing; check Play Console for the latest.
Practise this lesson on your app.
Track keywords, run the listing audit and see what your changes do — free.