# Product Page Optimization: your first screenshot test

Sam · Published November 4, 2026 · Canonical: https://rankaso.app/blog/app-store-ppo-test/


A first Product Page Optimization test is two screenshot sets that differ in one idea, run against each other on the App Store until the result is clear, which for a small app is usually two to four weeks. The idea to vary first is the story the frames tell: features, or outcomes. Everything else, the colour, the device, the layout, stays the same so that the result means something. We built exactly that pair for RankASO's own listing, and here is the method, including what to look at while the test runs.

![The Today screen in RankASO](https://rankaso.app/assets/device-05.png)

## One idea per test

A test that changes the titles, the colours and the order at once tells you that something worked and not what. For a first test, keep the design identical and change the message. Set A says what the app does, one feature per frame. Set B says what the user gets, one outcome per frame, with a number from the screen where there is one. Same frames, same device render, same ground, different titles.

For RankASO we shipped set A as the default page, feature-led: daily ranks, the wall, rivals, Today, Studio, honest numbers, privacy. Set B is the treatment, outcome-led: see what moved before coffee, know who is above you, get above your rivals, one score for the whole listing, fix the words that earn nothing. Same seven frames.

## Build the treatment to the same standard

A treatment that is visibly cheaper than the default loses for the wrong reason. Both sets should pass the same design checklist: the phone lower in the frame so the title has room, centred titles large enough to read at a glance, one detail lifted out of each screen so the eye has somewhere to land, no third-party app visible, and a consistent ground across frames. [The checklist in full.](/blog/app-store-screenshot-optimization/)

## Run it long enough, and read the right number

The result is conversion from product page view to download, by treatment. Small apps get few views a day, so the test needs weeks, not days, to separate signal from noise. Do not stop at the first lead; wait until the store's own confidence reading is high, or until two weeks have passed with the lead stable. Meanwhile, do not change the title, subtitle or keyword field; a metadata update during a test changes who arrives at the page and spoils the comparison.

## Watch the ranks while it runs

Conversion is half of what a page does; the other half is how many people reach it, which is the ranks. A test that lifts conversion while ranks fall for an unrelated reason can look like a loss. Keep the daily tracker running and read the two side by side: ranks flat and conversion up is a win; ranks down and conversion flat is a listing problem elsewhere, not a failed test. RankASO's Today screen gives the rank side in one number, the visibility score, so the test is read against a steady baseline.

## After the result

The winning set becomes the default. The next test changes the next single idea: the first frame alone, since most viewers never see the second; then the order; then a frame with a number against one without. One idea at a time, two to four weeks each, and in a year the page has been improved five or six times with evidence each time.

RankASO on the App Store: https://apps.apple.com/app/id6830350753?ct=blog-en-28&mt=8 (Free to start. No account. Data Not Collected.)

## Questions

### What should I test first in Product Page Optimization?

The story the screenshots tell: features versus outcomes, with the design held identical. It is the biggest single difference and the easiest to attribute.

### How long should a PPO test run for a small app?

Two to four weeks, until the lead is stable and the store's confidence reading is high. Few daily views means slow signal; stopping early picks noise.

### Can I update my keywords during a PPO test?

Better not. A metadata change alters who reaches the page and breaks the comparison. Keep the tracker running so you can see that ranks stayed flat during the test.