TL;DR. App Store Connect gives you three ways to release an approved version: automatic (live the instant App Review approves it), manual (held in “Pending Developer Release” until you click Release), and scheduled (held until a date/time you set, then automatic). All three affect your metadata the same way once live — your new keyword field, subtitle, description, and screenshots go into effect the moment the version releases, not the moment it’s approved. If you’re on manual or scheduled release and you’re checking rankings or conversion the day App Review approves your update, you’re measuring a version that isn’t live yet.

Indie developers who track keyword changes closely tend to watch one date: the day App Review approves the version. That’s the wrong date to watch unless your release option is set to automatic. Approval and release are two separate states in App Store Connect, and the gap between them can be minutes, days, or — if you forget a version sitting in Pending Developer Release — weeks.

When exactly do my new keywords and subtitle go live?

Your keyword field, subtitle, title, description, and screenshots all update at release, not at approval. For a version set to automatic release, those two events happen back to back, so the distinction rarely matters in practice. For manual or scheduled release, they don’t: the version can sit fully approved, with your new metadata already validated and ready, for as long as you leave it unreleased.

App Store Connect has three release options, chosen per version before submission:

  • Automatic release — the version goes live the moment App Review approves it. No extra step.
  • Manual release (“Release the app yourself”) — after approval, the version sits in Pending Developer Release status until you click Release This Version. Apple sends a reminder email if it’s been sitting there more than 30 days.
  • Scheduled release — Apple describes this as “automatically release this version after App Review, no earlier than” a date and time you set. The version releases on its own once that date arrives, but not before, even if approval comes through sooner.

All three require the Account Holder, Admin, or App Manager role to configure.

Why does this matter for a keyword or subtitle change specifically?

Because the failure mode is silent. If you submit a version with a reworked keyword field, watch App Review approve it, and then check search rankings or App Store Connect Analytics the next day expecting movement, you’ll see nothing — not because the keywords didn’t work, but because the version approved yesterday is still sitting in Pending Developer Release, waiting on you to click a button you forgot about. Nothing in the UI screams this at you; the version just quietly shows “Pending Developer Release” instead of “Ready for Sale,” and it’s easy to read that as “still processing” rather than “waiting on you.”

Scheduled release has a version of the same trap with a twist: developers sometimes set a “no earlier than” date for a coordinated marketing push, then forget that date is also gating their metadata change, not just their feature launch. If the date slips two weeks in planning and nobody updates the release date in App Store Connect, the keyword field rewrite you did to support that campaign sits dormant until the original date arrives.

Manual release also has a multi-platform gotcha: releasing is scoped per platform version. If you ship iOS and iPadOS versions together and both are sitting in Pending Developer Release, clicking Release on one doesn’t release the other — each platform needs its own manual trigger.

So which release option should I actually use?

Match the option to what you’re protecting:

  • Use automatic release for routine metadata-only or low-risk updates where you want the new keyword field and subtitle live as soon as possible — this is the right default for most ASO iteration, since it removes the “forgot to click Release” failure mode entirely.
  • Use manual release when you’re coordinating a metadata change with an external event — a press date, a paid campaign start, a feature announcement — and you need the product page to flip at a specific moment you control by hand. Put a calendar reminder on the approval date, not just the launch date, since approval can land days before you’re ready.
  • Use scheduled release when the launch moment is fixed and known in advance and you don’t want to depend on being online to click a button. Re-check the scheduled date any time the campaign timeline moves — App Store Connect won’t do that for you.

Either way, if you’re validating a keyword or subtitle change and want to know when it’s actually affecting new visitors, check the version’s status field for “Ready for Sale,” not the App Review approval notification. Approval is a review outcome. Ready for Sale is when your new metadata starts doing its job.

Before your next metadata-driven submission

  1. Check which release option is set on the version before you submit — don’t assume it’s automatic; it carries over from the last version you configured.
  2. If you’re on manual or scheduled release, put the actual release trigger on your calendar, separate from the submission date.
  3. When you check rankings or conversion after a keyword or subtitle change, confirm the version status says “Ready for Sale” first — an approved-but-unreleased version won’t move either metric.
  4. For multi-platform apps on manual release, release each platform version separately; approving or releasing one doesn’t touch the others.