Renaming an app can change keyword relevance, recognition, and brand search, so treat it as a managed migration. Benchmark first, update metadata and creative together, communicate with users, and monitor visibility, conversion, and reviews afterward.
Decide whether to rename
Reasons include trademark issues, product pivots, or market expansion. If the current name works but feels dated, the risk may outweigh the benefit. List expected gains and losses before deciding.
Consider whether a subtitle or visual refresh achieves the goal.
Benchmark before changing
Record rankings, brand search volume, conversion, and ratings so you can compare after. Identify the keywords currently carried by the old name and plan to cover them elsewhere.
Align the change with a release and annotate it.
Update everything together
Update the name, subtitle, icon, screenshots, website, and support materials so the story is consistent. Mixed branding confuses visitors and users.
Check trademark and domain availability beforehand.
Communicate and monitor
Tell existing users what is changing and why through in-app messages and release notes. Watch brand search, ratings, and support after launch and adjust.
Expect a transition period and plan resources.
Common mistakes with app rebrand ASO
Renaming without a benchmark makes it impossible to judge results. Changing only the name and leaving old branding in screenshots and the website confuses users. Dropping keywords the old name carried silently erodes visibility.
Failing to communicate with existing users generates confused support requests.
App rebrand ASO: a worked example
A company renames its app after a trademark conflict. It records rankings and brand search, moves the dropped keywords into the subtitle, updates the icon and screenshots in the same release, and announces the change in-app.
It monitors brand search and ratings for two months and adjusts messaging where confusion appears.
How to do it, step by step
- Write the case for renamingList the reasons and expected gains.
- BenchmarkRecord rankings, brand search, conversion, and ratings.
- Map keywords carried by the old nameDecide where each moves.
- Update all assets togetherChange name, icon, screenshots, website, and support.
- Communicate and monitorAnnounce in-app and track brand search for two months.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Old name had budget; new name is Penny
Move budget into the subtitle
Why it works: Visibility is preserved.
No notice
An in-app message: We are now Penny. Same app, same account.
Why it works: It reduces confusion.
Name changed, old logo everywhere
A coordinated update across the stores and website
Why it works: Consistent branding aids recognition.
Action plan
- List expected gains and losses
- Benchmark rankings and brand search
- Cover old name keywords elsewhere
- Update all assets together
- Check trademark and domains
- Communicate and monitor
Metrics to monitor
- Brand search volume
- Keyword visibility
- Conversion
- Rating and support trends
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
Will renaming hurt rankings?
It can if keywords were carried by the old name, so plan coverage.
Do reviews stay?
Reviews remain with the app, but context may confuse users.
How long does recovery take?
It varies; monitor and adjust.
Keep reading
More in Metadata Craft
Browse all 10 Metadata Craft guides
