App Store rankings are moving again. Here's what you control.

For about a year, new apps barely ranked on the App Store. If you shipped something in that window and watched it land nowhere, you were not imagining it.

This past week, around WWDC 2026, a lot of developers started saying the opposite. Keywords moving again. Brand-new apps showing up for terms they had no business reaching a month ago. I have seen enough of it in my own feeds to notice the pattern, though I want to be honest up front: this is developer-reported, the sample is small, and nobody outside Apple can tell you whether it lasts or why it happened.

Here is the part I am sure about. You cannot control the App Store ranking algorithm. It froze, it thawed, and it will move again on a schedule you do not set. What you can control are the inputs that feed it. The most underused one is your price, because both stores rank on conversion, and conversion depends on whether your price reads as fair in the user's wallet. This post is the argument for spending your energy there instead of on the algorithm you cannot see. If you want the deeper mechanics, I put them in how App Store pricing affects your ASO rankings.

Price is the input you control here, and it is worth getting right end to end. For the full picture, see the pillar on app pricing localization.

What actually happened to App Store rankings

Rewind to the last year. The common experience, across a lot of indie developers I talk to, was that new apps simply stopped gaining traction in search. You could do the metadata work, write the keywords, ship the screenshots, and still land nowhere. The going theory was that a flood of low-effort apps, a lot of them quickly assembled, pushed Apple to be more conservative about surfacing anything new. Whether that theory is right, I cannot prove. Apple does not narrate its ranking decisions.

What is documented is how concentrated downloads are. The top 1% of app publishers generate roughly 80% of all new installs (Sensor Tower), and indie developers feel that concentration harder than anyone. The old playbook, build an app around a popular keyword and let search do the rest, stopped being something you could lean on. So the response was predictable: developers moved spend to paid ads and web-to-app funnels to buy the installs that search used to hand out for free.

Then, around WWDC 2026, the mood shifted. Reports of rankings moving again, including for fresh apps. It is tempting to draw a straight line from the conference to the movement, and I would caution against it. Correlation around a date is not causation. The most I will say is that the timing is interesting, and that App Store ranking shifts seem to cluster, which means whatever changed may stick around for a while rather than churn weekly. If you are sitting on an app that went quiet last year, it is worth checking your numbers this week.

Why you cannot optimize for an algorithm you cannot see

Here is the trap. When rankings move, the instinct is to reverse-engineer the change. What did Apple do, and how do I game it? You can lose months there.

The honest reason it is a dead end is that Apple keeps shifting the basis of discovery, and it said as much at WWDC 2026. The read from people who watch this full-time is that discovery is moving from exact keyword matching toward semantic interpretation, where Apple reads your metadata, creative, and reviews together as connected signals rather than matching exact phrases. The same recap notes that the new Personalized Collections can reach users based on app usage and downloads before they have searched for anything (AppTweak's WWDC 2026 recap). Others describe those collections as AI-driven, on-device recommendations that surface apps from a user's interests and behavior, each with a short note on why it was picked (M+C Saatchi Performance). Increasingly, who sees your app depends on signals like usage and downloads, not just the keywords that led to it.

Notice what that means. Apple has never published the exact weights, and now they lean on signals you influence only indirectly, like whether the people who find your app actually download and use it. You cannot type your way to the top of that. You can only feed it healthier inputs. Chasing the algorithm is chasing a target that moves every June. Improving the inputs is the same work no matter which way the algorithm leans, which is why I would rather spend the time there. It compounds instead of resetting.

The inputs you do control

Strip away the parts you cannot touch and a short list remains. Your metadata and creative, which most ASO guides cover well. Your retention and the quality of the product, which decide whether post-install signals help or hurt you. And your price, which almost no ASO guide treats as a ranking input at all.

That last omission is the expensive one. Both Apple and Google reward listings that convert. Apple's own App Analytics surfaces conversion rate as a primary listing health metric, and the working consensus among ASO teams like AppTweak and Phiture is that listings which convert better tend to rank better, while ranking better brings a more qualified pool of visitors, which lifts conversion again. It is a loop.

Price sits right in the middle of that loop, and it is fully yours to set. Apple exposes roughly 900 price points per currency across 175 storefronts. Google lets you set a specific price per country. The price lever is as granular as the metadata lever. The difference is that nobody hands you a default keyword set, but the stores will happily fill the price field for you with a raw currency conversion the moment you leave it alone. That default is not a pricing decision. It is a unit conversion, and in most of the world it quietly suppresses the exact conversion signal you are trying to raise.

Why price does not care where the install came from

This is the point I keep coming back to, and it is the reason price beats the algorithm as a place to spend effort.

Every install converts against your price. It does not matter whether the person arrived from organic search, a paid ad, an influencer, or a web-to-app funnel. The last screen before they pay shows a number, and that number either fits their wallet or it does not. If you fled to paid ads during the frozen year, this matters even more, because you are now paying for each visitor. A price that reads as unaffordable in their market wastes the click you just bought.

Here is the gap in plain numbers. A flat $9.99 subscription is around 0.2 percent of median monthly income in the United States. Auto-converted into rupees or reais, that same $9.99 lands at roughly 3 percent or more of the local median, more than ten times the share it takes from a US paycheck. Same listing, same number in the console, wildly different affordability. The US developer sets the price feeling like a rounding error and never feels the version that hits a user in Mumbai or São Paulo. The stores see all of it in the conversion data, even when your dashboard only shows you the blended rate.

Localized pricing closes that gap. It means setting a price that reflects local purchasing power instead of the exchange rate, so $9.99 in San Francisco feels the way its local equivalent feels in Istanbul or Jakarta. That is the layer PricePush handles for me: PPP-aligned prices for 190+ countries, pushed to App Store Connect and Google Play in one step. Whatever the ranking algorithm is doing this quarter, the price underneath every install already fits the market it landed in.

What I would actually do this week

If rankings are moving for you, do not spend the week guessing at the algorithm. Spend it on the inputs.

First, pull your country-level conversion rate from App Store Connect and Google Play Console and sort by country. The markets where your conversion is far below your home market are your candidates. In my own apps, India, Brazil, Turkey, Indonesia, and Nigeria sat at the bottom until I fixed the price side.

Second, map each of those markets to a PPP-adjusted price rather than the auto-converted one, and watch the currencies that move, because the price that felt fair in Turkey last quarter may be off today. That ongoing drift is the part the stores' converter will never solve for you. For the full execution walkthrough, including baselines and per-market rounding, the complete guide to localized pricing for mobile apps covers the mechanics step by step.

Doing that on a cadence, rather than once, is a PPP rebalance: the recurring fix for prices that drift as currencies move.

Third, if you are also digesting everything Apple shipped this month, the discovery and selling changes are worth knowing, but they do not change the price each new model inherits. I wrote a neutral rundown of everything Apple changed at WWDC 2026 if you want the reference.

The takeaway

App Store rankings will do what Apple decides. They froze for a year, they are moving again, and they will shift once more next June, on a timeline none of us control. Your price will not. It is the one input that stays yours through every algorithm change, and it is the one the stores quietly grade you on in every country your app is visible.

So while everyone refreshes their rankings this week, go check your country-level conversion instead. If you want the execution handled, PricePush calculates PPP-adjusted prices for 190+ countries and pushes them to both stores in one tap. You can try it free on one app without a credit card and see the per-country gap on your own listing, and plans plus the founding lifetime offer are on the pricing page.