ASO Glossary

Discovery terms

Keyword: a word or phrase used to describe a search intent or product concept. Search intent: the task or outcome a person appears to be seeking with a query. Search results: the apps displayed for that query in a particular store, country, and moment.

Organic discovery: a shopper finding an app without a paid placement associated with that visit. Visibility is a broad term for the opportunity to be seen; it should not be confused with an install, because a visible listing can still be declined.

• Metadata: information supplied with a listing.
• Localization: adapting a listing and product for a market.
• Category: a store classification that helps browsing and context.

Listing and conversion terms

Product page or store listing: the page where a shopper evaluates an app. Creative assets: the icon, screenshots, preview media, and related visual material. Conversion is the movement from one step to another, such as from viewing a listing to installing; define the steps before using the term.

Value proposition: the concise explanation of why a particular audience should consider the app. Differentiator: a meaningful distinction from alternatives. Neither term should become a slogan detached from the product; both need evidence in the actual experience.

Measurement and experimentation terms

Search volume estimate: a third-party directional model of query activity, not a guaranteed count of installs. Keyword difficulty: a tool-specific estimate of competitive conditions, not a prediction of rank. Ranking: an app’s displayed position for a query under a particular context.

Hypothesis: a stated expectation that can be examined, such as whether clearer screenshots reduce confusion about a feature. Change log: a dated record of listing and product changes. These terms encourage teams to learn carefully rather than assign certainty to a single observation.

Product and audience terms

Feature: a specific capability available in the app. Use case: a concrete situation in which a person uses that capability. Audience: the people a listing is designed to help; it is more specific than everyone who could technically install the app.

Onboarding: the first-use experience that helps a new person reach value. Retention: continued use over time, which should be defined by the product team rather than assumed from an install. Review: customer feedback displayed through a store’s review system.

• Claim: a statement a listing asks shoppers to believe.
• Proof: visible product evidence that supports a claim.
• Friction: an obstacle that makes a task harder.
• Localization review: checking meaning and fit for a target market.

How to use the vocabulary

Use metric names with their scope. Instead of saying conversion improved, state the starting action, ending action, storefront, market, period, and whether other changes occurred. This makes a report understandable and less likely to overstate causation.

Use “estimate,” “observation,” and “hypothesis” precisely. An estimate is modeled; an observation is what was seen in a stated context; a hypothesis is an explanation or expectation to examine. None is a guarantee of future results.

Use evidence without overstating it

A store listing is one part of a wider product system. When reviewing its performance, begin by defining the question in plain language: what did a shopper see, what did they appear to be trying to do, and what changed in the app or listing at the same time? This framing is more useful than starting with a desired conclusion. It also helps separate an observation about a page from a judgment about the whole product.

Keep raw context with any report: the storefront, language, date range, release state, asset version, query or browsing path, and known campaign or seasonal activity. A number without this context is difficult to interpret later. Qualitative evidence matters too. Review excerpts, support themes, usability notes, and direct customer language can explain why a listing is clear or confusing in a way that an aggregate measure cannot.

Decide in advance what would make you revisit a choice. It might be recurring confusion about a feature, a localization concern, an outdated screenshot, or a product change that makes the present promise inaccurate. Then choose the smallest responsible next step: verify the product, review the live page, revise one message, or conduct further research. Small, documented decisions are easier to learn from than sweeping changes made under pressure.

Do not turn a correlation into a promise. Store presentation, search results, customer needs, and platform behavior can all change. The durable goal of ASO is a truthful, useful product page that helps the right person understand the app. That goal remains valuable even when the available signals are incomplete or ambiguous.

• State the question before opening a dashboard.
• Record market, timing, version, and related changes.
• Read customer language alongside quantitative signals.
• Identify uncertainty instead of filling gaps with assumptions.
• Choose a reversible, supportable next action.
• Review the live listing after publication.

Additional terms for clearer decisions

Impression: an opportunity for an item to be displayed, with the exact definition depending on the reporting surface. Install: acquisition of an app, which is not the same as active use. Attribution: the method used to associate an outcome with a source; its definitions and limits should be stated before comparison.

A/B test: a structured comparison of alternatives under defined conditions, not simply changing a listing and observing a later outcome. Baseline: the documented state used for comparison. Confounder: another change or condition that can make an apparent effect difficult to attribute to one listing element.

• Browse: discovery through store navigation rather than a typed query.
• Query: the text entered into search.
• Locale: a language and regional presentation context.
• Storefront: the country or region context of a store.
• Creative test: a comparison involving visual listing assets.
• Measurement window: the stated period used for observation.

Frequently asked questions

Further reading

• Apple: Product page metadata
• Google Play: Create and set up your app