App store optimization moved out of its "keyword stuffing and icon color" phase a few years ago. What is working in 2026 is more specific and more connected to actual install and retention metrics than the old playbook suggested. This post covers the levers that move installs, the ones that used to matter but no longer do, and the measurement approach that lets you tell the difference.
What actually moves install volume in 2026?
The short list of levers that are producing measurable results this year, in rough order of impact:
1. Conversion rate optimization on the product page
Install rate from browse and from search has diverged significantly. From browse (featuring, category charts, related apps), the product page is doing heavy lifting - the first two screenshots, the icon, and the short description are the only things most users evaluate before the install button. From search, the query-to-install path is shorter and keyword relevance matters more. Treating these as one optimization problem produces mediocre results on both.
The practical implication: run separate A/B tests for browse and search traffic. Apple's Product Page Optimization lets you run up to three treatment variants against the default. Use browse sessions to test screenshot narrative and icon variants. Use custom product pages (CPPs) for search-driven campaigns where you can tighten the message to the specific query.
2. Rating velocity and recency, not rating aggregate
Both Apple and Google have shifted their ranking signals toward recent ratings over all-time averages. An app with a 3.8 star average over five years will rank below an app with a 4.2 average over the past ninety days, all else being equal. The store algorithms are measuring momentum, not history.
The practical implication: implement in-app review prompts at high-satisfaction moments rather than at arbitrary intervals. Session length and feature completion are better triggers than time-since-install. For iOS, SKStoreReviewRequest after a user completes a workflow or reaches a positive milestone produces significantly higher ratings than prompting after a fixed number of sessions.
3. Metadata optimization with search intent alignment
Keyword stuffing is still prevalent and still produces the same result it always did - you rank for terms nobody is searching and miss the terms that convert. The shift in 2025-2026 is toward explicit intent modeling: what is the user trying to accomplish when they search this term, and does the app deliver that outcome.
For App Store, the title field (30 characters) and subtitle (30 characters) carry the most ranking weight. The keywords field (100 characters) is secondary. Google Play metadata works differently - the long description is indexed, so keyword density in the full description matters more than on iOS.
The practical implication: use Sensor Tower or data.ai to identify the terms that drive installs (not just impressions) for competitors in your category, and build your title and subtitle around the two or three terms that have the highest install intent. Rotate the keywords field quarterly based on trending terms in your category.
4. Feature graphic and first screenshot
On Google Play, the feature graphic (the banner at the top of the store listing) is the primary visual asset for browse and search results. Most developers treat it as an afterthought. On iOS, the first screenshot or app preview video is what appears in search results before a user taps into the product page. Both are the highest-leverage single creative assets in the ASO stack.
The practical implication: test the feature graphic and first screenshot with the same rigor you would apply to a paid creative. A 10 percent improvement in browse-to-page CTR compounds across every traffic source that reaches the listing.
5. In-app events and LiveActivities
Apple's in-app events surface in App Store search, the Today tab, and on the product page for installed users. For apps with recurring engagement loops - fitness, gaming, productivity, events - in-app event cards are a re-engagement tool that most competitors are not using, which means the impression share for well-crafted event cards is disproportionately high right now.
The practical implication: run in-app events around major feature launches, seasonal campaigns, and any content-driven engagement moment. The setup cost is low (an event card, a short description, a start and end date) and the visibility gain is material for apps in the sub-100K download range where organic visibility is otherwise hard to capture.
What used to work but does not anymore
- Keyword stuffing the app name. Both stores penalize keyword-heavy names in ranking and in featured placement consideration. "Fitness Tracker - Workout Log App" is a worse name than "StrongLog" from a brand standpoint and from a ranking standpoint in 2026.
- Review-gating. Showing a satisfaction prompt first and only directing satisfied users to the store is an explicit violation of both Apple and Google policies, and enforcement has increased significantly since 2024.
- All-time rating average optimization. As noted above, the algorithms care about recent ratings. Chasing the all-time average by resetting it (changing bundle ID) or by soliciting reviews without intent context is expensive and produces diminishing returns.
How do you measure ASO correctly?
The measurement failure I see most often is conflating organic browse installs with organic search installs. These have different optimization levers and different conversion characteristics. Mixing them produces averages that do not tell you which intervention produced which result.
The measurement setup I recommend:
| Signal | What it tells you | Where to find it |
|---|---|---|
| Impressions by source (browse vs search) | Which traffic source is growing or declining | App Store Connect Analytics / Play Console |
| Conversion rate by source | Where the product page is converting well or poorly | App Store Connect / Play Console |
| Keyword ranking (organic) | Which terms drive impressions and installs | Sensor Tower, data.ai, AppFollow |
| Rating velocity (30-day) | Momentum signal for store algorithms | AppFollow, direct store reporting |
| D1/D7/D30 retention | Whether installs are converting to retained users | Amplitude, Mixpanel, built-in app analytics |
The last metric - retention - is the one ASO practitioners most often skip. An install that churns in 24 hours is a negative signal for both Apple and Google's ranking algorithms. Retention is an ASO metric, not just a product metric, and improving D1 retention (through better onboarding, faster time-to-value, or more accurate pre-install messaging) improves organic ranking.
Common questions
How long does ASO take to show results?
Metadata changes surface in search results within 24-48 hours on both stores. Rating improvements take 30-90 days to shift ranking signals materially. Creative test results (screenshots, icons) in Apple's Product Page Optimization run a minimum of 90 days for statistical significance on most apps with under 50K monthly impressions.
Does paid UA affect organic rankings?
Yes, indirectly. Install velocity is a ranking signal, and paid campaigns that drive installs (and low churn) improve organic position. The effect is more pronounced for newer apps or apps in competitive categories where organic install velocity is otherwise low. The key is that paid installs need to produce retained users - installs that churn quickly generate a negative signal that can offset the volume benefit.
What is the minimum viable ASO investment?
For an app with under 10,000 monthly active users: metadata optimization, a review prompt implementation, and one screenshot test per quarter is the minimum viable set. For apps above that threshold, adding Sensor Tower or data.ai competitor monitoring and a quarterly in-app event cadence produces material returns relative to cost.
