The last pass over a listing is worth doing deliberately, because it is cheap and the alternative is a week in the review queue. This is the order to do it in. It takes about twenty minutes and it needs no tools beyond a browser and a phone.

1. Count and measure

One icon at 1200 × 1200. One feature image at 1600 × 900. Between three and six desktop screenshots, also 1600 × 900. Check the numbers in the file inspector rather than trusting the export preset, because a preset that was right last time is exactly the kind of thing that quietly changed.

2. Read the feature image alone

Open it full screen with nothing else visible and ask what a stranger learns. That image appears in search results and category pages, where none of your screenshots go. If it does not say what the app does without help, nothing further down the listing will get the chance to.

3. Hunt for numbers

Go through every image looking for a figure that is a claim: a percentage, a count of merchants, hours saved, a rating, a guarantee. Requirement 4.3.4 forbids stats, data and unsubstantiated claims such as guarantees in images, and it makes no exception for a number you can prove.

A number that is part of the interface - a quantity in a cart, a price in a product row of your own demo data - is a different thing from a claim about your app. The test is whether it is being used as evidence.

4. Hunt for prices

Separate pass, because it catches different things. Pricing may not appear anywhere in the images, including inside the icon. A plan badge, a "from $9" corner, a pricing table screenshot: all out.

5. Hunt for chrome

An address bar, a tab strip, a rounded window corner, a desktop wallpaper behind a floating panel. Requirement 4.4.4 names desktop backgrounds and browser windows specifically. While you are there, check that no image is only your logo on a colour - that is refused under the same requirement.

6. Compare every pair

Lay the six out together and look for two that carry the same thing. Requirement 4.4.5 asks that each image be unique and that screenshots show different features, views or states. If two are the same screen from a different scroll position, replace one or drop it. Three good screenshots beat six repetitive ones, and three is the minimum.

7. Read every word out loud

Typos survive design review because everybody has read the line forty times. Reading it aloud breaks that. Check that the words on the images match the words in the app: a headline that calls it a workflow while the app calls it a rule is one product with two names.

8. Look at the row at thumbnail size

Scale the whole row down until each image is about the size of a postage stamp, or better, open the staged listing on your phone and hold it at arm's length. You are checking two things: that the six are distinguishable from each other, and that the first one's headline is still readable.

9. Check the icon small

Put the icon at the size of a favicon beside the icons of three apps that rank for your keyword. If it disappears in that row, it is too detailed. That is a design fault, and it is the cheapest one on this list to fix.

10. Then submit

Nine passes, each looking for one thing. The reason to separate them is that a single look at each image will not find all of it - the eye that is checking the type size is not the eye that spots a browser window.

Everything on this list is a rule or a measurement, which means it is somebody's job rather than somebody's opinion. Do it once properly and the listing goes through on the first submission.