# Does Anything From 'Unreleased' Status Carry Forward Once You Launch?

> An app sitting in unreleased status, visible only through a direct link, feels like a quiet staging ground. Here's what actually follows your app once it finally goes public.


**Key points:**
- Unreleased status keeps your app reachable only through a direct link, not through normal search or browsing.
- Real feedback and use from that stage are genuinely useful, but they aren't the same as production ranking signal.
- Your real ranking clock starts once the app is truly public and findable through normal search and browse, not before.
- Staying unreleased longer than needed mainly costs you time, since that's time your real ranking signal isn't building yet.

A quiet, link-only stage before launch feels like a safe place to build something up before the real thing starts. What actually carries forward is smaller than it might seem.

## What unreleased status actually is

While your app sits unreleased, you can only reach it through a direct link, not through normal search or category browsing. That's a real, fair tool for sharing a build with a chosen group, stakeholders, early testers, a small invite list, without showing it to the public yet. It's also a genuinely different setting from your real listing later, not a soft, partial version of the same thing.

| | Unreleased status | After public launch |
|---|---|---|
| Found through normal search? | No, link only | Yes |
| Does activity here build real ranking signal? | Not the same real signal | Yes, from this point on |

## What carries forward and what doesn't

Real feedback from people who used the app during this stage has real value. Bugs caught. Confusing steps spotted. Feature ideas gathered. All of that counts, no matter when it happened. What doesn't carry forward the same way is ranking signal itself. The kind that actually builds your standing, real public search behavior, organic installs from real discovery, review activity from a wide, unprompted group, only starts once your app is truly public and reachable the normal way. A small, link-only group's activity before that isn't the same thing, even if it's useful on its own.

> **Real-world scenario:** A team kept their app in unreleased status for a long stretch, gathering feedback from an invited group and polishing the app based on what they learned. They assumed that stretch was quietly building momentum that would carry into launch. Once they finally went public, their rank started from about where any fresh public launch starts, since the real signal the store ranks on had never had a chance to build during the link-only stage. The feedback and polishing had genuinely made the app better. It just hadn't built the kind of signal they'd assumed it was.

## What this means for how long to stay unreleased

The real cost of staying unreleased longer than needed isn't that anything breaks. It's that the clock on your real ranking signal hasn't started yet. Every extra week spent gathering feedback in that stage is a week your real ranking signal isn't building, since that only starts once the app is truly public. Using the stage for real, needed feedback and fixes is worth it. Treating it as a place where ranking quietly builds in the background is the part that doesn't hold up.

## What to actually do about it

1. **Use unreleased status for real feedback and fixes, not a quiet ranking head start.** The signal you'd hope to build doesn't actually build there.
2. **Treat going public as your real starting line.** That's when the signal that actually matters for rank begins.
3. **Don't stretch this stage past what your feedback actually needs.** Extra time here is time your real ranking clock hasn't started yet.
4. **Carry the real insight forward, not an assumed head start.** The fixes and feedback are real value. The ranking boost isn't.

[AppRankr's Rank Tracker](/rank) tracks your real rank from the moment your app actually goes public, a clear way to see where your signal genuinely starts.

