ASO articles

App SEO is not a trick for indexing screens inside a binary. It is a web demand, content, technical-routing, store-conversion and measurement system that turns qualified searches into installs or app opens.

Someone on your team wants to know whether shaving megabytes off the build will move installs, and every number they can find online is a vendor blog quoting another vendor blog. Google does document the relationship, in plain language, on pages that disagree with each other about the actual limit. Here is what the primary sources say, what they do not say, and which Play Console metrics tell you whether size is costing you anything.

You changed the title, the screenshots and the description, and three weeks later nothing has obviously happened. Part of that is real: the stores publish two timing anchors worth planning around, a 28-day quality window on Google Play and a 90-day test length on the App Store. The rest of the timeline is undocumented, and most of the confident week-by-week figures circulating about ASO are invented.

Your ad platform claims one install number, Play Console shows another, and App Analytics shows a third. None of them are lying. Each store counts a different event, at a different moment, for a different population of users, and once you know which event each report is actually counting the three numbers stop contradicting each other.

Your app is live, the listing looks fine, and it appears nowhere. "Not ranking" is not one problem — it is at least six, and they fail in a fixed order. Work the fault tree from indexing upward and most teams find the answer two branches before they reach keyword strategy.

Someone in Jakarta sees your listing in Indonesian and you never wrote a word of Indonesian. That is Google Play doing two different things under one word, and knowing which one is running on your listing decides whether you have a localisation problem or not. The text is the easy part; the screenshots, the in-app strings and the support inbox are where the money leaks.

Most teams find custom store listings after they have already built a workaround for the problem custom listings solve. The feature lets you show a different name, icon, description and screenshots to a targeted slice of Play traffic, and Google documents both the ceiling and the constraints. The constraints are where the plans usually break.

Localisation is sold as one decision and priced as one invoice, but the stores treat the listing and the binary as two entirely separate systems with two separate fallbacks. Google Play will now translate your app strings at no cost while charging for listing translation; Apple charges for neither and supplies neither. Knowing which half of the work each store does for you is what decides where the money goes.

Your rating fell further than the new reviews should allow, and you cannot work out why. Google Play does not show users a lifetime average — it shows a figure weighted toward recent ratings, which is why a bad fortnight moves it so hard. The same mechanism is why recovery is faster than the arithmetic suggests, and there is a documented way to accelerate it.

Installs fell off a cliff, the app is still live, nothing was released, and nobody changed a campaign. There are seven documented causes, two of which restrict your distribution without removing your app, and one of which quietly makes you unavailable on newer devices. Here they are in the order that costs you the least time to check.

Most ASO tool roundups are written by people who have never had to justify the invoice. This one is written by an agency that pays for these tools, checked every price against the vendor's own page in August 2026, and will tell you plainly when the answer is to buy nothing at all.

Localisation is the only ASO change that creates new demand instead of fighting harder for demand you already compete in. This is how to choose locales from your own install data, rebuild a keyword set in a language rather than translating one, and decide which assets are worth localising — including the Indian-language opportunity almost every Western ASO guide ignores.

Play Console gives you a free A/B testing engine for your store listing, and most teams misread its rules before they run a single test. This is the mechanics guide: what the console will and will not let you test, how the traffic split and the target metric actually behave, and how to read a result that comes back as a draw.

Every ASO framework assumes you already have rankings, conversion rates and A/B test results to optimise against. A brand-new app has none of them. This guide covers only the data-free stage: how to build a keyword set, model the right competitors, and make the listing decisions iOS gives you no way to test yet — plus what Play does let you experiment on before launch, and how long you will wait for the rest.

Your app name is the shortest, most permanent and most contested piece of metadata you will ever write. Thirty characters on each store, a trademark exposure you cannot undo cheaply, and no way to A/B test it once you are live. Here is how to choose one properly.

Your screenshot set is the largest surface on the product page and the one place you get to argue for the install rather than describe it. This is how we design sets that survive the two-second scan: what the first panel must do, how to sequence the rest, which caption styles work, and the size, format and content rules on both stores — including the Play restrictions that quietly make an iOS set non-compliant on Android.

Every ASO guide tells you review velocity is a ranking factor. Almost none tells you how to earn reviews without doing something both stores prohibit — starting with the tactic most apps are quietly using right now.

Most teams conflate two completely different jobs: testing your store listing (icon, screenshots) and testing what happens inside the app (features, flows, paywalls). They need different tools. Here is a vendor-neutral map of which tool to reach for, what is free, and the iOS-versus-Android gap that changes everything.

The app growth tooling landscape is overwhelming until you organise it by funnel stage. This is the vendor-neutral, free-first map of every layer — ASO, user acquisition, attribution, analytics, engagement and monetisation — with a starter stack you can run for almost nothing and a clear signal for when each layer is worth paying to upgrade.

Most paid ASO suites repackage data the stores already give you for free. Here are the three free first-party tools that actually move rankings — Apple Search Ads keyword popularity, Play Console experiments and the App Store Connect search-term report — plus a complete ASO stack for under $30 a month.

Google Play still drives the volume, but the Galaxy Store, Indus Appstore, Xiaomi GetApps and Huawei AppGallery each open reach and billing economics Play cannot. Here is a 2026 decision framework for which alternative app stores actually earn their place — and which to ignore.

PhonePe's Indus Appstore is the most India-native Android store yet — 100M+ devices, Tier-3 reach, vernacular and voice search, and zero commission on in-app purchases. Here is how it works, how to publish, and where it actually pays off.

The Galaxy Store is preloaded on roughly a billion active Samsung devices, and since May 2025 it pays developers 80/20 on apps and games. Here is how to submit, what drives ranking, and where it actually pays off versus Google Play.

Xiaomi's GetApps ships preinstalled on millions of MIUI devices across India — and unlike Google Play, it gives you a dedicated keyword field to index. Here is how to submit, which metadata fields actually rank, and when the effort pays off.

Huawei AppGallery reaches a large Google-less audience, but it carries a stale myth and low India relevance. We debunk the dead '100% revenue' promo, explain HMS Core publishing, map the ASO fields that rank, and say plainly where it pays off.

Apple and Google rank apps on fundamentally different signals — Apple indexes a hidden 100-character keyword field and ignores your description, while Google full-text-indexes a 4,000-character long description. Here is exactly how the two algorithms differ, with the primary-sourced data, and why one ASO playbook cannot serve both stores.

Traditional ASO tooling was replaced by a Claude skill stack in 2026. This guide covers the seven layers of automated ASO — keyword research, metadata generation, screenshot copy, localisation, competitor intel, review mining, and rejection prevention — and the five skill repos driving the shift.

Apple doubled the Custom Product Page limit to 70 in October 2025 and opened CPPs to organic search results in July 2025. This playbook covers how to structure all 70 pages, assign keywords without cannibalisation, connect them to Apple Search Ads, and measure results with SKAN 4 — the same system our portfolio uses to achieve Apple's published 156% CVR uplift benchmark.

Your store listing is the last gate between a search result and an install. This guide covers every lever that moves App Store CVR — benchmarks by category, screenshot design, icon A/B testing, App Preview video lift, ratings influence, feature graphic on Google Play, Apple PPO vs. Store Listing Experiments, and seasonal updating.

Category ranking is a different game from keyword ranking. This is the playbook we use to push apps into the top 10 of their category and hold the position.

Basic ASO gets you to page one. Advanced ASO keeps you there — and pushes you to position one. This is the full 2026 playbook: semantic clustering, AI-era discovery signals, competitor keyword poaching, localisation as a multiplier, and review velocity engineering.

No one outside Google knows the exact Play Store algorithm — but five years of experiments across our portfolio give a clear-enough picture of what moves rankings.

The iOS App Store algorithm rewards different signals than Play Store. Here is what we know about iOS ranking in 2026 — based on our experiment portfolio and Apple's published documentation.

ASO A/B testing sounds simple — it is full of statistical traps that produce false winners. Here is the framework we use to test smarter and lift conversion 30%+ reliably.

Apple and Google editorial teams pick apps to feature on Today tab and Editor's Choice. Get picked once and you can see 50K-500K incremental installs. Here is how.

Our annual look at the Indian mobile marketing landscape — install trends, CPI movements, channel shifts, category dynamics, and what we expect next.

ASO in 2026 is not a checklist—it is an ongoing growth discipline spanning keyword research, creative testing, and platform-specific tools that Apple and Google keep shipping. This guide covers every lever, treated separately for iOS and Android, with conversion benchmarks drawn from our portfolio of 300+ apps.

ASO in 2026 looks fundamentally different from 12 months ago. Apple Intelligence has replaced keyword stuffing with semantic relevance, CPPs have doubled to 70 pages and now influence organic search, and Google Play's Gemini-powered recommendations weight retention over raw download count. Here is what changed and exactly what to do about it.

Google Play has its own algorithmic quirks that savvy ASO practitioners use to rank higher and convert more. This guide covers the best Android-specific ASO hacks — from AI recommendation signals and long description keyword density to Store Listing Experiments and pre-registration — that are producing measurable ranking lifts in 2026.

Every ASO ranking factor, ranked by impact — from building a keyword universe to Custom Product Pages, off-metadata signals, and the measurement framework that separates compounding programmes from one-off tweaks. Built from first-hand results across 300+ apps.

App Store Optimisation is the highest-ROI channel for sustainable app growth. This step-by-step guide walks you through every ASO lever — from audit and keyword research to A/B testing, ratings, and measuring results — so you can rank higher and convert more visitors into installs.