# Build an ASO baseline before entering a new storefront

URL: https://storelift.net/guide/new-storefront-aso-baseline/
Language: en
Updated: 2026-10-03

Entering a new country requires a local baseline, even when the app already performs elsewhere. The initial record should describe availability, listing language, relevant search terms and the apps already appearing for them. It is the comparison point for later decisions.

## Investigation steps

1. Confirm that the app and its intended features are available in the target market. Save the current listing and the language shown for the chosen storefront.
2. Research locally relevant phrases and record their intended app tasks. Measure the local results instead of carrying over ranks or demand assumptions from the home market.
3. Record measurement dates, observed ranks, missing observations and the competing apps. Add source-level acquisition data if available and mark unavailable metrics as unknown.

## Worked interpretation

Illustrative case: the home-market term ranks 9, while a locally researched phrase is outside the measured range in the new country. The home-market position is not the new market's starting rank; the local observation is.

## Decision and next check

Keep the baseline with the launch date, first planned listing changes and a fixed review window. Compare later results against that record. Separate localization work from product availability and campaign changes so the launch report explains what actually happened.

## Related Storelift feature

Read ASO localization for the available product data and its scope. Keep the app, storefront, period and measurement status with the observations used in your report.

## Worked example and blank template

The values below are synthetic, not customer or product results. Open the example, replace its scope with your own data and keep the source export alongside it.

- Printable worksheet and short walkthrough
- Worked CSV example
- Blank CSV template