What a Full ASO Refresh Looks Like After a Major Version Update

Most teams treat a major version update as a development milestone. Ship the new features, bump the version number, submit for review. Done.

That's a missed opportunity. A major update is the single best leverage point in app store optimization you'll encounter all year. The stores treat significant updates as fresh signals. Users have a reason to re-engage. Press has a hook. And the ratings slate can—if you move deliberately—reset in your favor.

What follows is the exact sequence we run for apps going through a major version release. Not a general checklist. A specific, ordered operation.

Why Major Version Updates Hit Different in the Stores

Minor updates (1.x patches) rarely move the ranking needle much. The stores have seen your app. They know what it does. A bug fix doesn't change that calculus.

A major update—going from 1.x to 2.0, or a substantial feature overhaul—creates a different signal environment:

Apple App Store weights recent ratings more heavily than historical ones when a new version ships. If your 2-star legacy reviews were dragging you down, a reset request after a major update is your cleanest path forward.
Google Play refreshes its editorial consideration window. Apps that have stagnated in search rankings sometimes see movement within a few weeks of a significant update, particularly when the metadata also changes.
Category ranking algorithms pick up engagement signals from the update surge—press coverage, re-installs from lapsed users, and an install spike from the App Store's own editorial team if they choose to feature you.

None of this is automatic. You have to position the update correctly, and you have to do it before the binary goes live—not after.

Step 1: Metadata Audit Before You Submit

The worst time to realize your keyword strategy is stale is after the binary is already in review. Lock down your metadata before submission.

What to audit:

Title field — Your primary keyword belongs here. On iOS, the title + subtitle combination gives you roughly 30 characters each. On Google Play, the title is 30 characters. Don't waste them on the app name alone if you can work in a descriptor.
Keyword field (iOS only) — 100 characters, no spaces between keywords, commas as separators. Pull your current list and run it against your keyword research. Remove any terms you're already ranking for in the title or subtitle (the algorithm doesn't double-count). Add mid-volume, low-competition terms you've been ignoring.
Short description (Google Play) — 80 characters, indexed. Treat it like a meta description with keyword intent, not a tagline.
Long description (Google Play) — 4,000 characters. Actually indexed. Use natural keyword density in the first 167 characters (the fold), then expand into feature detail and use cases.
Subtitle (iOS) — The most underused field in ASO. It indexes separately from the title and should carry your second-priority keyword cluster.

Run this audit in a spreadsheet. Column A: current value. Column B: proposed value. Column C: rationale. That discipline forces you to make deliberate choices rather than reflex edits.

Step 2: Visual Asset Refresh

The app stores are visual search engines. Your screenshots and preview video are your conversion rate. Getting ranked matters nothing if the store page doesn't convert.

A major update gives you a legitimate reason to refresh your entire visual set—and you should.

Screenshot priorities:

Asset	iOS Requirement	Google Play Requirement	What to Change
Primary screenshot	6.9" (iPhone 16 Pro Max) required	Phone screenshots required	Lead with the #1 new feature
Landscape screenshots	Optional but indexed	Required for tablet	Update to reflect new UI
App preview video	Up to 30 seconds, autoplays muted	Up to 30 seconds	Rebuild around the new core flow
Feature graphic	N/A	1024×500 required	Refresh with new version branding
iPad screenshots	Required if iPad-compatible	N/A	Often forgotten—don't skip

What we've seen work: Lead with the value outcome in your first screenshot, not a UI frame. "Track every delivery in real time" with a map in the background converts better than a raw screen capture with no context text. The caption overlay is doing most of the conversion work.

If your design team is rebuilding the UI for v2, the screenshot set should be part of that sprint—not an afterthought the week before submission.

Step 3: Ratings Strategy Around the Update

This is the highest-leverage and most frequently botched part of a major update.

On iOS: You can call SKStoreReviewRequestAPI to prompt a rating. Apple allows up to three prompts per 365-day period per user. If you've already used your prompts, a major version update resets the user's 365-day window. Trigger your prompt 2–3 sessions after the update installs, once the user has experienced the new features.

On Google Play: The In-App Review API has no annual limit but throttles based on user behavior signals. The same principle applies—wait until the user has had a genuine positive interaction with the new feature, not the moment the update downloads.

What to avoid: Prompting on first launch of the new version. Users are still orienting. They haven't formed an opinion yet, and a premature prompt generates neutral or negative responses.

What to consider: If your pre-update ratings were poor (below 4.0), you can request a ratings reset from Apple via App Store Connect before you submit the major version. This is a one-time action per app. Use it deliberately. Going from 3.6 to a clean slate is worth more than the short-term social proof of existing volume.

Step 4: Release Notes as a Keyword Surface

Most teams write release notes in 30 seconds. "Bug fixes and performance improvements." That's a waste of indexed real estate.

On Google Play, release notes are indexed and surfaced in search. On iOS, they're visible on the App Store page and influence user decision-making at the install moment.

Write release notes that:

Lead with the user benefit, not the engineering change. "Deliveries now update every 30 seconds" instead of "Improved real-time tracking polling interval."
Include 2–3 natural keyword mentions relevant to your category. Don't stuff. Write for the user first, but be intentional.
Use scannable formatting. Bullet points. Short sentences. Users read these on mobile in the install decision window.
Acknowledge the version. "Version 2.0 brings…" signals to both users and the algorithm that this is a meaningful update, not a patch.

Release notes for a major version should run 150–250 words. That's enough to be substantive without being ignored.

Step 5: The Submission Timing Window

Don't submit the major update on a Monday. Apple's review team—and more importantly, the editorial team—operates on a cycle. Apps submitted mid-week, particularly Tuesday through Thursday, have historically had better editorial consideration windows in our engagements. There's no official confirmation of this, but the pattern holds.

On Google Play, the staged rollout feature matters here. Don't push a major update to 100% of users immediately. Roll out to 10%, watch your crash rate and rating signals for 48–72 hours, then expand. A crash spike in a major update that reaches your full user base before you catch it is a ratings disaster that takes months to recover from.

Coordinate with your UA campaigns. If you're running paid install campaigns, pause or reduce spend during the first 48 hours of rollout. You want organic engagement signals—especially from existing users updating—to dominate the early window. Adding cold-traffic installs before your crash rate is confirmed is a risk that rarely pays off.

If you're running paid campaigns and want a framework for how paid and organic ASO signals interact, our deep linking and strategic marketing guide is worth reading alongside this checklist.

Running a major app update and want a second opinion on your ASO strategy? Our mobile app marketing team handles full ASO audits, metadata rewrites, and visual asset production for apps across iOS and Android.

Step 6: Post-Launch Monitoring (First 30 Days)

The refresh doesn't end at submission. The first 30 days after a major update ship are when the algorithm is most responsive to signals.

Monitor weekly:

Keyword rank movement — Use a tool (AppFollow, AppTweak, Sensor Tower, or MobileAction). Expect volatility in weeks 1–2 as the stores re-index. Don't panic and change metadata mid-cycle.
Conversion rate on the store page — App Store Connect and Google Play Console both report impression-to-install rates. If impressions rise but conversion drops, your new screenshots aren't working.
Rating velocity — How many ratings per day, and at what star distribution. This tells you whether your in-app prompt timing is correct.
Review content — Read the actual text. Users will tell you exactly what they like and don't like about the new version. That's free product research.

At day 30, run a full keyword rank report against your pre-update baseline. That delta is your ASO lift attribution for the update cycle.

FAQ

How long does it take to see ranking changes after a major update?

Typically 2–4 weeks for keyword rank movements to stabilize on both platforms. The stores re-index your metadata relatively quickly, but ranking reflects engagement signals that accumulate over time. Don't make metadata changes during this window unless you have a clear reason—let the signals settle first.

Should I change my app name during a major version update?

Only if the old name has no brand equity worth preserving. Name changes can temporarily disrupt rankings because the algorithm has to re-associate your keyword relevance. If you're rebranding entirely, a major version update is the right moment to do it—but treat it as a net-new ASO launch, not an optimization.

Can I reset my ratings on both iOS and Google Play?

Apple allows a ratings reset via App Store Connect—you can request it before submitting a major version. Google Play does not offer a formal ratings reset option. Your best lever on Play is increasing rating volume post-update to dilute historical low ratings through the in-app review prompt.

Does updating the app preview video actually impact conversion?

In our engagements, yes—particularly on iOS, where the preview video autoplays in search results. A video that leads with the new UI and core value prop in the first 5 seconds typically outperforms a static screenshot set for conversion in competitive categories. The caveat: a poorly produced video underperforms no video. Don't ship something half-finished.

How is this different from a routine ASO audit?

A routine ASO audit is reactive—you're reviewing what's working and making incremental adjustments. A major version refresh is a proactive, coordinated operation timed to the update window when the algorithm is most receptive to new signals. The metadata changes, visual refresh, ratings strategy, and release notes all have to move together. Any one element done in isolation loses leverage.

What if my app has been live for years with very few rating signals?

A major update is the best catalyst you'll get to generate fresh ratings velocity. Combine the in-app prompt (timed correctly, as described above) with an email or push notification to your engaged user base announcing the new version. "We rebuilt X—let us know what you think" is a legitimate reason to ask for a review. The apps we've seen recover best from thin rating histories almost always pair the update with a deliberate re-engagement push.

A major version update that ships without a coordinated ASO refresh is a missed window you won't get back until the next major cycle. If you're planning a significant release in the next quarter and want to pressure-test your approach before you submit, book a call or review what our mobile app marketing team covers in a full ASO engagement.