Key points:
- Your app’s package name is a permanent ID, not an editable setting like your title or description.
- Publishing under a new package name creates a whole new listing, with none of your old history attached.
- Ratings, reviews, rankings, and install counts all stay with the original package name, not the new one.
- A real migration path exists for teams that truly need to change this, but it’s a step you take on purpose, not something that happens by itself.
A setting buried deep in your app’s setup turns out to be one of the few things you genuinely can’t just edit later.
Why this one is different from everything else
Most of what makes up your listing, title, description, screenshots, price, can be edited any time on a live app. Your package name isn’t in that group. It’s the fixed ID the store uses to track your app’s whole history. Every rating. Every review. Every install. Every rank signal. All of it tied to that one ID for the life of the listing. Change it, and you’re not editing your old app. You’re making a new one.
| Can you change it on a live listing? | What it carries | |
|---|---|---|
| Title, description, screenshots | Yes, any time | No history tied to these |
| Package name | No | Your full rating, review, and install history |
Why this surprises teams
A rename or rebrand often touches everything else about an app. The title changes. The icon changes. The description changes. It’s easy to assume the package name should just follow along with that. It doesn’t work that way, for good reason. The package name is the anchor the whole system uses to know it’s looking at the same app over time. Everything else can shift freely around it. That anchor staying fixed is what lets your history mean anything at all.
Real-world scenario: A team rebranding their app published what they thought was simply an updated version, under a new package name as part of the wider refresh. The result wasn’t an update. It was a brand-new listing, starting at zero ratings, zero reviews, zero rank history. Their years of reviews and their established keyword rankings stayed behind on the old, now-abandoned package name. They later used the store’s real migration process to move users and merge the listings properly, a real path that exists for exactly this. They just found it only after losing real time running two separate listings instead of one.
The real path if you genuinely need to change it
Migration exists for exactly this case, teams with a real, fair reason to move to a new package name. It’s built to carry your existing presence forward in a controlled way, instead of leaving your history stranded on an ID you’re walking away from. The key difference from just publishing a new listing is that migration is something you set up on purpose, not something that happens as a side effect of changing a setting.
What to actually do about it
- Treat your package name as fixed from day one. Unlike almost everything else on your listing, this one isn’t meant to be touched later.
- Never let a rebrand quietly drag your package name along. Everything else about your listing can change freely without touching this ID at all.
- Use the real migration path if you genuinely need to change it. It exists specifically to stop your history from getting stranded on an ID you’re leaving behind.
- Check both listings’ standing if you ever end up with two. Catching a split early gives you more room to merge them before too much history piles up on the wrong side.
AppRankr’s Rank Tracker tracks your real rank history over time, a clear way to catch it fast if something like this ever splits your data in two.