# ASO workflows URL: https://storelift.net/guide/aso-workflows/ Language: en Updated: 2026-10-02 Choose the job you need to do. Each guide explains the observations to collect, an illustrative interpretation and the evidence for the next decision. These workflows serve app teams working on App Store and Google Play visibility. ## Pages in this section - [Failed ASO rank measurements: investigate missing data](https://storelift.net/guide/failed-rank-measurement/): A missing rank can mean that a measurement failed or that a completed search did not contain the app. - [App not found in tracked search results: interpret the limit](https://storelift.net/guide/app-outside-search-depth/): A completed rank check covers a finite result set. An app absent from that set has no observed position within the measured depth. That is useful evidence, but… - [Diagnose a sudden app keyword rank drop](https://storelift.net/guide/sudden-keyword-rank-drop/): A rank drop is an observation to explain, not a diagnosis by itself. - [Why your manual App Store rank differs from a tracker](https://storelift.net/guide/storefront-rank-mismatch/): Two rank checks can disagree because they are different observations. - [Keyword rank and category chart position: read both correctly](https://storelift.net/guide/keyword-rank-vs-category-chart/): A keyword rank describes one search phrase in one storefront. - [Measure ASO changes around an app release](https://storelift.net/guide/measure-aso-release-impact/): A release creates a useful marker in rank history, but several things may change around it: metadata, product behavior, reviews and acquisition campaigns. - [Prioritize an ASO keyword backlog with measured evidence](https://storelift.net/guide/prioritize-aso-keyword-backlog/): A long keyword list is an inventory, not a decision. Prioritization begins with whether the app actually satisfies the search intent, then considers the evidence… - [Separate brand and generic keywords in ASO reports](https://storelift.net/guide/brand-vs-generic-keyword-tracking/): People searching for your app by name already have a different intent from people searching for a task. - [Use fixed keyword cohorts for comparable ASO trends](https://storelift.net/guide/fixed-keyword-cohort-report/): A portfolio average changes when ranks move, but also when terms are added or removed. - [Track changes in the apps competing for your keywords](https://storelift.net/guide/search-competitor-turnover/): Your commercial competitors and your search competitors are overlapping sets, not necessarily identical ones. - [Monitor seasonal ASO keywords without confusing rank and demand](https://storelift.net/guide/seasonal-aso-keyword-monitoring/): Seasonal interest and search position are different variables. - [Build an ASO baseline before entering a new storefront](https://storelift.net/guide/new-storefront-aso-baseline/): Entering a new country requires a local baseline, even when the app already performs elsewhere. - [Keep an ASO metadata change log that explains results](https://storelift.net/guide/aso-metadata-change-log/): Rank history becomes more useful when the listing changes beside it are known. - [Plan an app subtitle change with a testable hypothesis](https://storelift.net/guide/app-subtitle-experiment-plan/): A subtitle has to explain the app while supporting relevant discovery. - [Write a screenshot test brief for an app store listing](https://storelift.net/guide/app-screenshot-test-brief/): A useful screenshot brief begins with a message hypothesis, not a request for a different color. - [Prioritize missing app store listing languages](https://storelift.net/guide/prioritize-app-listing-locales/): A missing language slot is a coverage gap, but the next language to work on should follow a product and market decision. - [Turn app review themes into better listing messages](https://storelift.net/guide/reviews-to-listing-messages/): Reviews can reveal how users describe an app's value and where the listing creates wrong expectations. - [Compare recent app reviews with the lifetime rating](https://storelift.net/guide/recent-reviews-vs-lifetime-rating/): A lifetime rating and a recent review sample summarize different populations. - [Review organic rank alongside Apple Ads performance](https://storelift.net/guide/organic-paid-aso-review/): Organic rank and paid acquisition can be viewed together without treating them as interchangeable metrics. - [Use paid search terms as ASO research candidates](https://storelift.net/guide/paid-search-terms-for-aso/): A paid search-term report can reveal the language people used before interacting with an ad. - [Diagnose an app store acquisition funnel change](https://storelift.net/guide/app-store-acquisition-funnel-diagnosis/): Impressions, product-page activity and downloads describe different parts of acquisition. - [Explain changes in your app's acquisition source mix](https://storelift.net/guide/acquisition-source-mix-report/): A source can gain a larger share of downloads because it grew or because other sources shrank. - [Compare app downloads and revenue without mixing scopes](https://storelift.net/guide/downloads-vs-revenue-scope/): Downloads and revenue can move differently because they describe different events and populations. - [Read subscription outcomes beside app acquisition](https://storelift.net/guide/subscription-cohort-reading/): Acquisition brings users into an app; subscription outcomes happen on their own timeline. - [A weekly ASO review template for app teams](https://storelift.net/guide/weekly-aso-review-template/): A weekly review should end with decisions, not a collection of screenshots. - [Build a client ASO report with traceable evidence](https://storelift.net/guide/client-aso-report-evidence/): A client report needs to distinguish completed work, observed results and the interpretation connecting them. - [Reconcile an ASO export with dashboard totals](https://storelift.net/guide/reconcile-aso-export-and-dashboard/): An export and a dashboard can disagree because they summarize different filters, dates or row populations. - [Review an ASO portfolio across several apps](https://storelift.net/guide/multi-app-aso-portfolio-review/): A portfolio summary should help decide where to investigate next without letting the largest tracking set dominate every conclusion. - [Triage keyword rank alerts before editing metadata](https://storelift.net/guide/keyword-rank-alert-triage/): An alert is a prompt to inspect an observation. It is not proof that a metadata change is needed. A consistent triage process checks data quality, scope and… - [Review data access before sharing an ASO report](https://storelift.net/guide/aso-report-access-review/): An ASO report can combine public store observations with private tracking choices and connected account data.