# Keep an ASO metadata change log that explains results

URL: https://storelift.net/guide/aso-metadata-change-log/
Language: en
Updated: 2026-10-02

Rank history becomes more useful when the listing changes beside it are known. A change log records the exact old and new text, the storefront and the reason for the edit. A note saying 'ASO updated' is too broad to support a later investigation.

## Investigation steps

1. Save the app identifier, platform, locale, field, previous value and proposed value. Record the intended search task and the terms expected to gain or lose coverage.
2. Separate draft approval, submission and observed publication dates. Keep the reviewer and release identifier with the entry so the published version can be traced.
3. Add the first comparable post-publication observations. Preserve the original hypothesis even if the result is disappointing; rewriting it afterward makes the record less useful.

## Worked interpretation

Illustrative entry: a subtitle replaced a broad benefit phrase with a specific supported task. The log retains both strings, the target locale, publication date and tracked terms. A later decline can then be investigated against the actual edit.

## Decision and next check

Use the record to choose between retaining, revising or reverting a change. A rollback should also become a new dated entry. Keep campaign and product changes nearby as context rather than attributing every movement to text alone.

## Related Storelift feature

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