# Plan an app subtitle change with a testable hypothesis

URL: https://storelift.net/guide/app-subtitle-experiment-plan/
Language: en
Updated: 2026-10-02

A subtitle has to explain the app while supporting relevant discovery. Before editing it, state the specific misunderstanding or search gap the new wording is meant to address. A sequential metadata change is an observational comparison, not automatically a randomized experiment.

## Investigation steps

1. Write the current and proposed subtitle beside the app name. Check that the combined message describes a supported capability and reads naturally to the intended audience.
2. Identify the target terms and any terms removed by the new wording. Save their baseline observations in the relevant storefront and record which other fields will remain unchanged.
3. Choose a review window and the evidence needed for the decision: publication confirmed, comparable rank observations and relevant acquisition metrics where available.

## Worked interpretation

Illustrative hypothesis: making the app's core task explicit will improve relevance for a small target group of searches. If those terms improve but acquisition falls after a campaign ends, the report must describe both events rather than declaring a simple win or loss.

## Decision and next check

Review readability and search evidence together. Preserve the previous subtitle for a documented rollback. Do not present the change as a supported product-page asset experiment unless the platform actually tests that field in the chosen experiment type.

## 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.