Download your lesson workbook · Open the assignment tool →
Your ASO learning objective
Compare two proposals without losing the original, and document what changed and why.
- Step 1Freeze a dated control
- Step 2Inspect text and visual differences
- Step 3Explain each change and its purpose
Preserve a meaningful control
Version A should represent a known starting point, not a moving target. Record its date, locale and purpose before copying it into version B. If you change A during review, note that explicitly. A comparison only helps the team when everyone knows which proposal is being evaluated against which baseline.
Review the complete listing for message consistency. A journal-focused screenshot sequence paired with a title that suggests route navigation sends conflicting signals. Use Listing Studio for the visual comparison and Metadata Comparator for the exact field values. Both tools share the same project so the review does not depend on outdated pasted copies.
Read the diff as evidence of edits, not performance
The comparator identifies exact field changes and unique words added or removed, ignoring case and punctuation for the term lists. Reordering words can change meaning without adding a new term, so inspect the full before-and-after text. A changed count is a editing aid; it says nothing about keyword demand or ranking impact.
Check limits and empty fields, then read the proposed text aloud. Confirm that each retained keyword and claim still fits the current product and locale. If the two versions use different languages, word differences are descriptive only. Translation accuracy and cultural fit require appropriate review rather than a larger list of changed terms.
Separate a creative package from an isolated experiment
A complete redesign may change metadata, order and screenshots together for a launch. An experiment intended to investigate one screenshot decision needs a tighter treatment. Label the project purpose. If you want to test only the opening message, hold other relevant assets and metadata constant and document the exact difference. Do not attribute an outcome to one element after changing several without a design that supports that inference.
Worked example: Trail Notes
This fictional hiking-journal app is the teaching project. Treat the example as a reasoning exercise you can adapt to your own evidence.
- Original draftA and B differ in subtitle, opening headline and screenshot order, but the brief calls this a headline test.
- Revised proposalKeep the full redesign as a proposal. For the isolated test, copy the control and change only the opening creative treatment.
- Why it changesVersioning preserves both useful artifacts while making the experiment's scope honest. A term diff cannot establish which simultaneous change caused a result.
Your ASO assignment
- Compare versions A and B in Metadata Comparator and inspect all changed fields, including those with no added or removed terms.
- Record important inclusions, exclusions and the reason for each metadata change.
- Export the metadata report and identify whether this is a launch package or an isolated experiment proposal.
Your handover and assessment criteria
Your work is ready for review when each deliverable below can be understood without a verbal explanation. Include the source or product reference, the decision owner and any unresolved evidence gap. If a reviewer cannot verify a claim, record the missing evidence before treating the proposal as approved.
- Deliverable 1Dated control and proposed metadata
- Deliverable 2Change report with decision rationale
- Deliverable 3Explicit experiment or launch scope
Check your understanding
The added-terms list is empty. Does that mean the subtitle is unchanged?
Read the interpretation
No. Order, punctuation or letter case may have changed. The exact-field comparison and full text determine whether the field changed; the term lists answer a narrower question.
Record your progress
Mark this lesson complete after checking your assignment against the handover criteria. Progress stays in this browser, separately from your tool project.
Sources and further reading
Platform references checked 30 September 2026.