App Store Optimisation in 2026: Launch Playbook
A launch-plus-90-days playbook for getting a new app found and installed on the App Store and Google Play, covering keyword research, metadata limits, visuals and reviews.
Key Takeaways
- Treat ASO as two jobs at once: getting found in search and turning product page visitors into installs.
- Apple gives 160 searchable characters in total, while Google Play reads the full description instead.
- The first screenshots, the icon and early reviews shape the install decision more than any single keyword.
- A 90-day routine of weekly measurement and one change at a time beats one big launch effort.
An app store optimisation playbook is a launch plan plus a 90-day routine that makes a new app easy to find in store search and easy to choose on its product page. It works by placing the search terms real users type into the small set of fields each store reads, then improving screenshots, ratings and reviews so more of the people who arrive install. This guide applies that playbook to both the Apple App Store and Google Play, because the two stores read different fields and reward different signals. It covers keyword research, metadata limits, visuals, reviews and a week-by-week plan for the first 90 days. It is written for founders and small teams shipping their first app, and for teams relaunching an app that never gained traction.
What Is App Store Optimisation?
App store optimisation is the practice of improving how an app appears in store search results and how many store visitors install it. It covers two jobs at once. The first job is visibility: appearing for the searches a future user types. The second job is conversion: convincing the person who opens the product page to install. Both jobs matter: a top ranking with weak screenshots still loses installs, and great screenshots on a page nobody finds still lose installs. The work does not end at launch, because rankings shift as rivals update listings and stores change rules.
According to Apple, App Store search results are based on text relevance, including matches in the app title, subtitle, keywords and primary category, and on user behaviour such as downloads, ratings and reviews. That statement frames the whole playbook: match the words users search for, then earn the behaviour signals that lift the app further. Google Play states a similar idea in different words, ranking apps on relevance, engagement and quality.
How Does the App Store Optimisation Playbook Work?
The app store optimisation playbook works as two connected loops. The search loop puts the right terms in the fields each store reads, so the app appears for more searches. The conversion loop improves the icon, screenshots, preview video, ratings and reviews, so more visitors install. Better conversion then feeds better rankings, because both stores watch what users do after they see an app. Measure each loop separately: impressions and keyword ranks for search, and the share of visitors who install for conversion.
| Field | Apple App Store | Google Play |
|---|---|---|
| Title | 30 characters, indexed | 30 characters, indexed |
| Subtitle or short description | Subtitle, 30 characters | Short description, 80 characters |
| Keyword field | 100 bytes, hidden | No keyword field |
| Long description | 4,000 characters, not indexed | 4,000 characters, indexed |
| Promotional text | 170 characters, editable anytime | Not applicable |
According to Google Play Console Help, a Google Play title is limited to 30 characters, the short description to 80 characters, and the full description to 4,000 characters. On Apple, the title and subtitle are each limited to 30 characters, the hidden keyword field holds 100 bytes, and the description runs to 4,000 characters but is not used for search. The contrast sets the strategy: Apple rewards a tight keyword plan across three small fields, while Google Play rewards clear, natural language in a long description the store actually reads.
Keyword research follows a simple sequence. First, list the words customers use when they describe the problem the app solves. Second, check the search suggestions each store shows when those words are typed, since those suggestions reflect real demand. Third, study the top five rival listings and note which terms they repeat. Fourth, sort the list by two tests: does the term match what the app really does, and can a new app rank for it. Fifth, place the strongest term in the title, supporting terms in the subtitle or short description, and the rest in the keyword field on Apple or the full description on Google Play.
Why Do Apple and Google Play Rank Apps Differently?
Apple and Google Play rank apps differently: Apple reads a hidden keyword field and ignores the long description for search, while Google Play has no keyword field and reads the full description instead. Apple therefore rewards a compact keyword plan, while Google Play rewards descriptive copy in natural sentences. One shared listing strategy across both stores wastes effort on both.
Apple allows up to 70 Custom Product Pages per app, and since July 2025 those pages can appear in App Store search results when keywords are assigned to them in App Store Connect, according to App Store Connect guidance. Google Play offers a similar tool, custom store listings, with up to 50 per app, targeted by search keyword, country or audience. Both tools let a team show a different product page to a different audience without changing the main listing.
Discovery is also moving beyond typed search. At Google I/O 2026, Google announced Ask Play, an AI overlay that recommends apps, plus discovery in the Gemini app and Play Shorts, a vertical video feed, according to Admiral Media's Google Play ASO guide. Since iOS 26, Apple also shows App Store tags, labels generated by Apple's AI from listing metadata and reviewed by people before they go live, according to Netguru. An AI summary or a short video still has to explain the app in seconds, so clear screenshots and a sharp first sentence gain value.
Quality signals matter on both stores. Google's Android vitals guidance sets its bad-behaviour threshold for the user-perceived crash rate at 1.09 percent of daily users, or 8 percent on a single device model, according to Google Play Console documentation cited by DEESU. Crossing those lines can lose discoverability, so stability work is part of ASO, not separate from it. Ratings and reviews carry weight on both stores, so replies to reviews and fixes for repeated complaints feed back into ranking.
What Should Your App Store Optimisation Playbook Cover in the First 90 Days?
The app store optimisation playbook for the first 90 days has three phases: launch week sets the listing, days 8 to 30 test and fix it, and days 31 to 90 expand it. Each phase has one clear job, so the team always knows what to change next.
Launch week is about shipping a complete listing, not a perfect one. The checklist: a title that pairs the brand name with the main search phrase, a subtitle or short description stating the core benefit, every keyword field filled with no repeated terms, an icon readable at small sizes, and five screenshots that show the outcome of using the app rather than a list of features. Teams building the app behind the listing can read about the mobile app development services from Skills Technology Solutions, which cover the build choices that shape store performance.
Days 8 to 30 are for measurement and the first fixes. Watch which search terms bring impressions, which screenshots hold attention, and what early reviews say. Run one product page test at a time, changing a single screenshot or the first line of the description, then wait two weeks to read the result. Apple limits its in-app review prompt to three displays per app in a 365-day period, according to Apple's review request documentation reported by Netguru, so the prompt should appear only after a user completes a meaningful task, never at launch.
Days 31 to 60 are for expansion. Localise the listing for the next language where traffic exists, since a translated listing can rank for searches the English listing never reaches. Build the first Custom Product Page or custom store listing for a second audience, and test it against the main page. Review the keyword list again and replace terms that bring impressions but no installs. This is also the point to check the technology choice behind the app, and the Flutter versus React Native comparison for 2026 explains how the two leading cross-platform options differ for a business shipping on both stores.
Days 61 to 90 are for consolidation. Keep the title stable, since frequent title changes can unsettle rankings, and put the effort into reviews, localisation and seasonal updates to screenshots and promotional text. By day 90 the team should have a baseline for every key number: impressions, keyword ranks, the install rate, the average rating and the crash rate. Those baselines turn ASO from a launch task into a monthly routine.
How to Turn Launch Week Into Lasting Visibility?
Launch week turns into lasting visibility when the listing, the launch page and the first reviews all tell the same story. A visitor who reads a launch announcement, opens the store page and sees the same benefit is more likely to install, and more likely to leave a review that mentions it. That consistency is what turns the first week of attention into rankings that hold.
Before launch, prepare the assets and the sequence: final screenshots, a short preview video, the first review replies drafted in advance, and a launch page that matches the store listing message. The guide to landing page systems for launch campaigns shows how a launch page can be ready in a day and keep its message aligned with the store listing. On launch day, share the page with the people most likely to try and review the app, then answer every review within a day. After launch, keep one change in test at all times, and record each result in a single log, so the team never repeats a failed experiment.
What Are the Common Mistakes in App Store Optimisation?
The most common mistakes in app store optimisation come from treating the two stores as one, or from changing too much at once.
- Repeating keywords across the title, subtitle and keyword field on Apple, which wastes the 100-byte allowance because Apple counts each term once.
- Stuffing keywords into the Google Play description as a list, which reads badly and can breach store policy.
- Copying the Apple listing onto Google Play unchanged, which ignores that Play reads the full description and has no keyword field.
- Changing the title every week, which unsettles rankings and hides which change caused a result.
- Ignoring reviews, which lets the same complaint appear again and again and drags down the rating and the install rate.
- Designing screenshots around features instead of outcomes, so a visitor sees what the app has, not what it does.
Frequently Asked Questions
How long does app store optimisation take to show results?
App store optimisation usually shows early movement within two to four weeks, with steadier gains across the first 90 days. Rankings respond first to metadata changes, while ratings and reviews build more slowly. Change one element at a time and wait at least two weeks before judging it, so each result traces back to a single cause.
What is the difference between ASO on the App Store and Google Play?
The App Store reads the title, subtitle and a hidden 100-byte keyword field, and it does not use the long description for search. Google Play has no keyword field and instead reads the title, short description and full description. Apple rewards a compact keyword plan, while Google Play rewards natural descriptive copy with key phrases used once or twice.
How many keywords should a new app target at launch?
A new app should target five to ten keywords, with one main phrase in the title and the rest spread across the subtitle, keyword field or description. A narrow set keeps the listing focused and shows which terms drive installs. Add new terms after the set has ranked for two weeks, and replace terms that bring impressions but no installs.
Do ratings and reviews affect app store rankings?
Ratings and reviews affect app store rankings on both stores, because Apple and Google both count user behaviour among their ranking signals. A higher average rating also lifts the install rate, since visitors trust the stars and written reviews. Reply to reviews, fix the problems reviewers repeat, and ask for a rating only after a user finishes a valued task.
How often should an app update its store listing?
An app should review its store listing monthly and update it when the data gives a reason, such as a keyword losing rank or a screenshot underperforming in a test. Most metadata changes on Apple need a new app version, while promotional text can change freely. Avoid changing the title every week, because frequent title changes can unsettle rankings.
The first 90 days set the pattern for everything that follows: a listing that matches real searches, visuals that show the outcome, and a routine that tests one change at a time. Skills Technology Solutions, a software agency based in Rahim Yar Khan, Pakistan, serving clients in Pakistan and the UK, can help you put this into practice. Contact our team to discuss your project.
Related Articles
Keep reading — more guides you may find useful.
Related Services
Services connected to this guide.
