Choose the scope before ticking anything.
Review one app, store and priority market at a time. A check completed for an English iOS listing does not prove that a translated Android listing is ready. Add the target context to your own work notes so another person can understand what was reviewed.
The interactive list saves its checked items in this browser when storage is available. Export the status before starting a different review. It does not upload your progress or connect to your store accounts.
Start with product accuracy and audience fit.
Confirm that the listing describes features available in the actual product. Identify the intended user and the main reason to install. Look for claims that need evidence, unclear subscription expectations and creative that implies an experience the app does not provide.
These are foundations. A field can fit its character limit and still fail to communicate anything useful. The ASO fundamentals guide explains why discovery and choice belong together.
Treat research as a documented decision.
Record the language your audience uses, group terms by intent and explain why the priority group belongs. Keep estimated tool metrics separate from observed account data. Note which ideas depend on assumptions or native-language input.
The research workflow shows how to move from candidate terms to a usable map. A downloaded spreadsheet alone does not complete this part of the review.
Review creative at realistic viewing size.
Read the opening message without zooming. Check whether the visible product screen supports it. Give each frame a different role and verify that translated captions fit. Ask someone unfamiliar with the app what they think it does after seeing the opening sequence.
A comprehension check can expose confusion, but it is not a conversion experiment. Use the screenshot guide to develop a more deliberate narrative.
Make the release and evaluation concrete.
Name the publishing owner, approver and target version. Save the previous listing and record the changes. Agree which report and audience will be used for evaluation, including its limitations. Note campaigns or product changes that could complicate interpretation.
When an item is not applicable, record the reason in your project notes rather than treating it as completed work. If several important items remain unclear, an ASO audit can help prioritise the next steps.
