An ASO checklist helps you check whether people can find your app, understand what it does, and choose to download it. This 30-step reference covers metadata, screenshots, localization, reviews, and measurement for the Apple App Store and Google Play.
Start with the fields that are inaccurate or incomplete, then use your store analytics to choose what to improve next. Neither completing a checklist nor updating on a fixed schedule guarantees higher rankings or more downloads.
Use this list at launch, after a major product change, or when a listing needs attention. Skip items that do not apply to your app and record anything that needs a follow-up. For background, see the guide to app store ranking factors.
Metadata Optimization (Steps 1-8)
Start with the words people see in search results and on the listing. They should describe the current app clearly and use relevant terms where they read naturally.
Step 1: Title Clearly Describes the App Within 30 Characters
Both stores limit the app name to 30 characters. Choose a recognizable name that describes your app accurately, and include a relevant search term where it reads naturally. See Apple's product page guidance and Google Play's field limits.
A title like "FitTrack: Calorie Counter" combines a brand with a clear function. Filling every character is not the goal: keep the title useful to readers and avoid irrelevant terms.
Step 2: Subtitle/Short Description Includes Secondary Keyword
The iOS subtitle allows 30 characters; the Google Play short description allows 80. Use that space to explain a benefit or function that complements the title. The two stores use different fields and ranking systems, so do not assume an identical ranking weight.
Good example: Title is "FitTrack. Calorie Counter" and subtitle is "Meal Planner & Weight Loss." That covers three keyword clusters without duplication.
Step 3: iOS Keyword Field Contains Relevant, Distinct Terms
Apple provides a 100-byte keyword field. Separate terms with commas and avoid repeating words from your title, subtitle, or category. Spaces can be used within keyword phrases. Use relevant terms that fit; padding the field to exactly 100 bytes is unnecessary. Apple explains how to choose keywords.
Use AppDrift's metadata generator to prepare a draft, then review the keywords for relevance and unnecessary overlap.
Step 4: Description Explains the App Clearly Within the Limit
Use the description to explain features, benefits, and any requirements users should know before downloading. Google Play allows up to 4,000 characters and advises against excessive length and repeated keywords in its store listing best practices. Repeat a term only when the sentence needs it.
Write enough to explain the app without padding it to a minimum length. Use short paragraphs and feature lists so readers can find the information they need.
Step 5: Description First Paragraph Hooks the Reader
Both platforms show only the first 1-3 lines of your description before the "Read More" fold. This opening paragraph needs to accomplish two things: communicate your core value proposition and compel the user to keep reading (or just install). Avoid vague statements like "The best app for productivity." Instead, be specific: "Track tasks, set reminders, and sync across your devices."
Step 6: No Prohibited Words Used
Check each store's rules for the field you are editing. Google Play's listing guidelines prohibit store-ranking and promotional claims in specified metadata, including app titles. Keep descriptions accurate about functionality and paid features, and avoid misleading references to competitors or affiliations.
Step 7: Promotional Text Is Current (iOS)
Apple's Promotional Text field (170 characters) sits above the description and can be updated without submitting a new app version. Use it for timely messaging: seasonal promotions, new feature announcements, limited-time offers. If your promotional text still says "New Year Special!" in April, it signals neglect to potential users.
Step 8: Release Notes Mention Latest Improvements
Use release notes to explain what changed for the people updating your app. Name the feature or fix, such as "Added dark mode and fixed a crash when opening saved workouts." Include performance numbers only when you have measured them. Do not treat release notes as an established keyword-ranking field.
Workflow tip: AppDrift can prepare metadata drafts and check field lengths. Read the finished copy for accuracy, relevance and natural wording before submission.
Visual Assets (Steps 9-14)
Screenshots, icons, and preview videos help people judge whether your app fits their needs. Show the actual experience clearly. Use store experiments when you have enough traffic to measure whether a visual change helps conversion.
Step 9: Screenshots Meet Each Store's Requirements
Apple allows up to 10 screenshots, while Google Play allows up to 8 per supported device type. Choose enough distinct screenshots to explain the experience; extra repetitive images are not automatically better. Check Apple's upload requirements and Google Play's preview asset requirements.
Use the device sizes required for your app's supported platforms and form factors. Requirements and scaling rules differ by store, so check the current specifications before exporting. A screenshot generator can help prepare those assets.
Step 10: First 3 Screenshots Show Key Value Proposition
Make the opening screenshots answer "What does this app do for me?" Show a useful feature in context and describe its benefit clearly. Claims about time saved or other outcomes need evidence from your app; do not add an invented number to make a caption more persuasive.
Step 11: Screenshot Captions Explain the Feature Shown
Use short, accurate captions that explain the experience shown. A workout screen could say "Review Your Weekly Workouts" if that is what the feature does. Check readability at the size people see in the store.
Do not assume screenshot text is a confirmed keyword-ranking field on both stores. Evaluate captions through user understanding and conversion experiments, rather than promising a ranking gain.
Step 12: App Icon Is Distinctive and Readable at Small Sizes
Test the icon at the small sizes and contexts where users see it. Keep its main shape recognizable and check it against nearby results. A particular color count is a design choice, not a store requirement.
Step 13: Preview Video Opens With the Core Task
Open a preview with a useful part of the actual app, and ensure it remains understandable without sound. The opening matters for communication, but a fixed three-second rule does not determine every viewer's decision.
Follow the current store duration and format requirements and use only the time needed to demonstrate the task. Test whether a video improves the listing rather than assuming shorter is always better.
Step 14: All Assets Follow Apple/Google Size Requirements
Rejected or incorrectly sized assets delay your launch and look unprofessional. Before submitting, verify every screenshot and video against current platform specifications. Apple requires specific dimensions per device class. Google Play has its own aspect ratio and resolution rules. Platform requirements change occasionally: check the latest guidelines with every submission, not just your first one.
Workflow tip: AppDrift supports manual Free-template screenshot exports with an account. Pro collections and AI usage have separate access and token requirements.
Localization (Steps 15-19)
Localization helps you explain your app to people in other markets. Choose those markets from audience needs, existing downloads, usage, and your ability to support the experience. Apple's localization guidance recommends evaluating market fit and territory-level analytics. A translation alone does not guarantee more downloads.
Step 15: Localization Prioritized for Relevant Markets
Start with markets where your app solves a clear problem and where your data or customer research shows interest. There is no universal minimum of ten languages. Test a manageable set of localizations and compare store performance by territory before expanding.
Your store listing should set accurate expectations about the languages supported inside the app. AI-powered translation tools can prepare drafts, but have a fluent reviewer check meaning, local terminology, screenshots, and any claims before publishing.
Step 16: Keywords Researched Per Locale (Not Just Translated)
Research how people describe the task in each target market. Direct translation can miss a local term or imply a different feature. Compare relevant store search results and ask a fluent reviewer whether your chosen phrases sound natural.
Step 17: Screenshots Localized With Translated Captions
Localize captions and the app interface shown where you support that language. Check the exported image for clipped text and mismatches between the caption and feature. Measure the result in the target market instead of assuming the translation will improve conversion.
Step 18: Cultural Adaptation Applied (Not Literal Translation)
Have a fluent reviewer check tone, terminology, imagery and feature emphasis for the intended audience. Country-level stereotypes do not predict which message will convert for your app.
Step 19: Right-to-Left Languages Handled Correctly
For right-to-left languages, validate reading order, caption alignment and the actual app UI with a fluent reviewer. Do not automatically mirror photographs, logos or directional controls whose meaning should stay fixed.
Ratings & Reviews (Steps 20-23)
Ratings and reviews give prospective users evidence about the experience. Apple lists them among its search factors and explains their role in its ratings and reviews guidance. Read the reasons behind your score rather than treating a particular rating as a guaranteed conversion or featuring threshold.
Step 20: Product Issues Behind Low Ratings Are Addressed
Group recent critical reviews by problem, such as crashes, billing confusion, or missing functionality. Prioritize fixes by severity and the number of people affected. Compare ratings by version and market where the console supports it, then check whether the same complaints continue after a fix.
Step 21: Recent Reviews Are Positive
A lifetime average can hide a recent problem. Monitor new reviews for recurring complaints and compare their timing with releases or incidents. Investigate a surge of negative feedback without assuming that every change in rating has the same cause.
Step 22: Critical Reviews Receive Useful Responses
Responding to negative reviews accomplishes three things: it shows potential users that you care about the product, it can prompt the reviewer to update their rating after you've fixed their issue, and it provides context that offsets the negative impression. Aim for responses within 48 hours. Address the specific problem, explain what you're doing about it, and invite them to reach out for direct support.
Step 23: In-App Review Prompts at Satisfaction Peaks
Timing is everything with review prompts. Trigger them after positive experiences, completing a task, reaching a milestone, unlocking an achievement, not during onboarding or after a crash. On iOS, use SKStoreReviewController (limited to 3 prompts per 365 days). On Android, use the Google Play In-App Review API. Never incentivize reviews: both platforms prohibit it and will penalize your app.
For prompt timing and review-policy details, see how to get more app reviews.
Technical & Tracking (Steps 24-30)
The first 23 steps handle what users see. Steps 24-30 handle what you measure, monitor, and iterate on. Use them to decide which changes deserve your time.
Step 24: Custom Product Pages Set Up for Key Intents
Apple supports up to 70 custom product pages, with keyword assignments from the approved app version where eligible. Use a dedicated page when a distinct audience benefits from different assets, and measure its performance. Apple CPP configuration.
Step 25: Keywords Tracked Across Target Countries
Track relevant keywords in the storefronts you serve and compare their positions over time. Investigate sustained changes alongside metadata updates, competitors, and store analytics. Our rank-movement study shows why an isolated daily movement is not enough to judge a listing change. AppDrift keyword tracking includes five keywords with daily updates on the Free plan.
Step 26: Competitors Monitored for Metadata Changes
Your competitors are not standing still. Choose a manageable set of relevant competitors for your primary keywords and monitor their title changes, screenshot updates, description edits, and rating trends. When a competitor updates their metadata, it can shift your rankings even if you haven't changed anything. Automated competitor monitoring catches these shifts early so you can respond before your rankings erode.
Step 27: Listing-Check Findings Are Reviewed
An ASO score is a tool's diagnostic based on its own checks, not a score issued by Apple or Google or a prediction of downloads. Use the findings from AppDrift's ASO Score to spot listing issues, then decide which changes matter for your app and measure their results.
Step 28: A/B Tests Have a Clear Hypothesis and Enough Data
Use Apple's Product Page Optimization or Google Play's Store Listing Experiments when you have a specific question and enough traffic to evaluate it. Test one meaningful change at a time, using the assets supported by that store. Read the platform's confidence results and sample requirements before choosing a winner; seven days does not guarantee a conclusive result. See Apple's test analysis guidance and Google Play's experiment setup and results.
Step 29: Listing Reflects the Current App Version
Update screenshots, descriptions, and release notes when the product changes or you find an inaccuracy. Choose a release schedule from product quality and user needs. Apple describes multiple search factors; publishing every month is not a documented guarantee of maintaining or improving rank.
Step 30: Analytics Tracking App Store Impressions
Use App Store Connect Analytics and Google Play Console to monitor discovery, listing visits, downloads, and conversion. Keep each platform's metric definitions and traffic sources explicit: their denominators are not interchangeable. Compare consistent periods and record changes to the app, listing, or campaigns that could affect the result.
Use the ASO Audit tool to find listing details worth checking. Compare each finding with the actual store page; a missing collected field is not necessarily missing from the listing.
How to Use This Checklist: Monthly ASO Audit Process
Working through all 30 steps at launch is critical, but the real value of a checklist comes from revisiting it regularly. Here's a practical monthly review cadence:
Of 202 listings we monitored for at least two weeks, 141 — about 70% — never changed their title, subtitle or description. This describes the observed listings; it does not show that an edit would improve their performance. See the listing-update study for the method and limits.
Week 1: Keyword review. Compare relevant keywords in the same storefront over time. Investigate sustained changes alongside search demand and conversion data before replacing terms. A single rank drop may be normal volatility.
Week 3: Competitive scan. Search your primary keywords and note any new competitors in the top 10. Check if existing competitors changed their titles, screenshots, or descriptions. Update your competitive analysis tracking.
Week 4: Ratings and visual refresh. Read the last 30 days of reviews for recurring themes. Ensure all negative reviews have responses. Evaluate whether screenshots still accurately represent the current app UI. Plan any visual asset updates for next month.
Adjust this cadence to your release schedule, traffic, and available time. Teams managing several apps or locales can use AppDrift's launch checklist to keep track of the work and revisit unresolved items.
Tools That Accelerate Your ASO Checklist
A checklist tells you what to optimize. The right tools determine how fast you can execute. Here's what covers the most ground with the least overhead:
- Metadata generation and optimization: AppDrift's AI metadata generator prepares editable titles, subtitles, descriptions, and keyword fields for both platforms
- Screenshot creation: AppDrift's screenshot generator lays out store screenshots for each device size; manual Free-template exports require an account, and Pro collections remain paid.
- Localization: AI-powered translation prepares drafts in 60+ languages with local keyword research for review before publishing
- Keyword tracking: Daily rank tracking in 60+ storefronts with difficulty scores, popularity trends, and competitor comparison
- Listing checks: ASO Score is a tool-defined diagnostic with limited inputs, not a store-issued grade or a complete live audit.
Choose tools for the tasks you actually need to complete. A keyword tracker, a metadata or design tool, and the stores' own analytics may cover your current workflow. Add another tool when there is a specific missing capability; our comparison of the 22 best ASO tools lists what each one covers and its dated price.
Frequently Asked Questions
What is an ASO checklist and why do I need one?
An ASO checklist brings the main listing tasks into one place: metadata, visuals, localization, reviews, and measurement. It helps you spot omissions and keep the store page aligned with the app.
How often should I run through my ASO checklist?
Run a lightweight audit monthly covering keyword rankings, conversion rates, and recent reviews. Perform a comprehensive review quarterly that includes a full competitive re-scan, screenshot refresh evaluation, and metadata overhaul assessment. Additionally, revisit the full checklist whenever you ship a major update, enter a new market, or notice a significant drop in impressions or installs.
What are the most important items on an ASO checklist for a new app launch?
For a new app launch, prioritize an accurate title within the 30-character limit, relevant terms in the iOS keyword field, screenshots that show the core experience, a clear opening description, and localization for the markets your app can support. Choose languages from audience evidence and have the translated listing reviewed before publishing.
Do I need separate ASO checklists for iOS and Google Play?
Use one checklist with platform-specific requirements. iOS has a subtitle and a dedicated keyword field, while Google Play has a short description and a full description. Screenshot limits, supported devices, and experiment options also differ. Check each store's current specifications rather than copying settings between platforms.
What is the biggest ASO mistake that a checklist can prevent?
A common mistake is leaving the listing out of step with the app. A recurring review helps you notice inaccurate screenshots, outdated descriptions, customer complaints, and changes in search performance. Review the evidence before making changes; a schedule alone does not prevent ranking losses or guarantee growth.
How do screenshot captions affect ASO in 2026?
Screenshot captions help people understand the feature shown and decide whether the app meets their needs. Keep them accurate, readable, and localized for the intended audience. Treat their effect on conversion as something to test; this checklist does not assume that caption text is a confirmed search-ranking field on both stores.
Can I automate parts of the ASO checklist?
Yes. Several checklist items can be partially or fully automated. AI-powered tools can generate keyword-optimized metadata, translate listings into 60+ languages, track keyword rankings daily, monitor competitor metadata changes, and calculate ASO scores. Automated screenshot generators can produce assets for multiple device sizes in minutes. However, strategic decisions like keyword selection, A/B test interpretation, and review response still require human judgment.
Key Takeaways
Use the checklist to keep track of practical work:
- Keep metadata accurate: Stay within field limits, use relevant terms, and remove duplication rather than padding the text.
- Show the actual experience: Use clear screenshots and captions that follow the store's specifications. Test a proposed change when you can collect enough data.
- Choose relevant markets: Research local terminology, review translations, and support the experience promised by your listing.
- Act on customer feedback: Fix recurring product issues and respond helpfully to reviews.
- Measure before changing direction: Compare ranks, impressions, and downloads over time. A rank alone does not prove a change caused more installs.
- Review regularly: Keep your listing aligned with the product; no fixed audit or release schedule guarantees growth.
Start with the checklist items where your listing is inaccurate or your data shows a problem. Record each change and its date, then review the relevant store metrics once enough data has accumulated.
