ASO June 27, 2026 · 4 min read

Your Mid-Year ASO Audit: 6 Things to Fix Before Back-to-School Season

June is the App Store’s quiet season — and the best time to fix screenshots, keywords, localized metadata, and pricing before the back-to-school lift. A six-point ASO checklist for mid-2026.

By the AppsOps news desk · June 27, 2026

June is the App Store’s quiet season — download volumes ease, editorial spotlight shifts to summer games, and most app teams take a breath. That makes it the best possible time to fix the metadata, screenshots, and pricing that have been silently dragging down your rankings. The back-to-school window opens in late August, Q4 kicks off in October, and Apple’s editorial review pipeline has lead time. The audit you skip in June is the opportunity you miss in September.

Why This Particular Audit Matters in Mid-2026

Two forces have converged this year to make a mid-year sweep especially worthwhile. First, iOS 26 was announced at WWDC with a visual overhaul — Liquid Glass — that Apple’s editorial team is already foregrounding in featuring curation. Apps whose screenshots still show iOS 15-era UI chrome are increasingly out of step with Apple’s own aesthetic framing in the App Store. Second, the AI keyword wave has reshuffled search intent across dozens of app categories. Terms that performed well in 2024 may be lower-competition dead weight today, while AI-adjacent terms in your category may be genuinely underutilised.

The Six-Point Audit

1. Screenshots: Liquid Glass Compatibility

Apple’s editorial team picks featured apps partly based on whether they look at home in the new iOS 26 design language. That’s consistent with how Apple handled previous major UI shifts — iOS 7 flat design in 2013, iOS 14 widget redesign in 2020. If your primary screenshots use pre-iOS 26 chrome, update at least your first two frames before the back-to-school push. The same logic applies to localized screenshot sets: updating US English but not your top five revenue territories captures maybe a third of the compounding benefit. For more on how Liquid Glass specifically changes the product page conversion calculus, see our earlier coverage of iOS 26 Liquid Glass and ASO impact.

2. Keywords: Remove Waste, Add AI-Era Terms

The 100-character keyword field decays passively over time. Common issues to purge before the fall season:

Plurals and prepositions (Apple’s indexer handles morphological variants automatically — adding them wastes characters)
Competitor brand names (still an App Review rejection trigger if you don’t own the trademark)
Terms already used verbatim in your app name or subtitle (Apple already indexes those; repetition does not increase weight)

What to add: AI-adjacent modifiers in your category have grown meaningfully in search volume. If your app does anything users now describe as “AI” — smart scheduling, auto-transcription, writing assistance, on-device summarisation — those terms belong explicitly in your keyword field. Apple’s search indexer matches keywords; it does not infer intent from feature lists. The AppsOps keyword strategy primer walks through field-level optimisation and per-locale variation in more detail.

3. Subtitle: Your Underused Click-Driver

The 30-character subtitle appears in search results directly beneath the app name. It is indexed for keywords but, more importantly, it affects tap-through rate before anyone reaches your product page. A subtitle that reads as a bland category descriptor (“Habit Tracker App”) is doing almost nothing. A subtitle that names the user outcome (“Build habits that actually stick”) earns the tap. Check whether yours is optimised for keyword indexing, conversion, or both — and whether it varies by locale. App Store Connect allows per-locale subtitles with no additional review friction.

4. Localized Metadata: The Multi-Territory Gap

Reports consistently suggest the majority of apps do not localise metadata past a handful of European languages. That leaves keyword indexing gaps in Japan, Brazil, South Korea, Indonesia, and other high-volume storefronts where localised titles and subtitles are the baseline expectation from competing apps. The conversion impact compounds: a localised screenshot set without localised metadata (or vice versa) captures only half the benefit of either.

If localisation cost is the blocker, the AppsOps localisation cost calculator lets you model the break-even point by territory. For most apps with meaningful organic installs, the threshold is lower than teams expect — particularly in Brazil, Japan, and German-speaking markets where conversion lift on localised metadata is well-documented by third-party ASO research. The top-markets localisation guide on the blog covers priority ordering by category.

5. Custom Product Pages: Audit and Refresh

Custom Product Pages set up for a campaign six months ago often go stale. Useful questions to work through now:

Which CPPs still have active Apple Search Ads traffic, and which are orphaned pages with no inbound links?
Do your active CPPs reflect post-iOS 26 screenshot assets, or are they showing old UI?
Have you created a CPP for back-to-school specifically? Productivity and focus framing converts strongly in August–September even for apps that are not primarily aimed at students.

CPPs support A/B testing of creative at the campaign level independently of your main product page. That means you can test back-to-school creative without touching organic rankings — a significant advantage heading into Q3.

6. Subscription Pricing: PPP and Price Architecture

If you have not reviewed your global pricing relative to purchasing-power-adjusted tiers in the past 12 months, you are almost certainly underpriced in some markets and overpriced in others. App Store Connect’s automated PPP suggestions are a reasonable starting point; they are not a complete answer. The more precise method is to export install distribution versus revenue by territory from ASC and look for markets where installs significantly outpace revenue — that gap is usually a pricing signal, not a product quality signal.

Revenue per user in markets like Brazil, India, and Southeast Asia responds meaningfully to PPP-adjusted pricing — but only when pricing reflects local income levels rather than a simple currency conversion of a US price point.

The AppsOps PPP pricing tool shows territory-level purchasing power benchmarks alongside your existing price tiers. Reviewing it before a price change lands is easier than unwinding grandfathered subscribers after the fact.