Aso

---
name: aso
description: >
  Use this skill for App Store Optimization on iOS App Store and Google Play. Trigger phrases: "ASO," "app store optimization," "app store keywords," "app title optimization," "app screenshots," "Google Play listing," "iOS App Store ranking," "app store A/B test," "app ratings strategy," "review strategy," "app store competitor analysis," "app store keyword research."
---

# App Store Optimization: iOS and Google Play

## Mandatory Content Standards

- Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.
- Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.
- Use short sentences. One idea per sentence. One focus per paragraph.
- Use active voice. Never passive constructions.
- Address the reader directly using "you" and "your."
- Use bullet points only when they genuinely improve readability.
- Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.
- End every sentence with a period.
- No hashtags, emojis, or asterisks.
- No introductory or closing filler phrases such as "in conclusion," "in summary," or "in a world where."
- No warnings, notes, or disclaimers. Stick to requested output.
- No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."
- No excessive adjectives or adverbs. Let specifics do the work.
- No broad generalizations. Every claim tied to specific context.
- Use specific examples, data, and scenarios.
- Pose at least one thought-provoking question per skill.
- Mobile-friendly: short paragraphs, clear headers, scannable.
- Practical and actionable. Every section connects to a next step.

---

## What This Skill Covers

App Store Optimization (ASO) is the process of improving your app's visibility in the App Store and Google Play search results and increasing the percentage of store visitors who install your app. This skill covers keyword research specific to app stores, metadata optimization (title, subtitle, description, keyword field), visual asset strategy (screenshots and preview videos), rating and review strategy, A/B testing on store listings, and competitive listing analysis.

---

## Why ASO Is Not the Same as SEO

Developers and marketers who apply web SEO logic directly to ASO typically get worse results than those who learn the distinct rules of app store search.

App stores are closed ecosystems. Google Play and the Apple App Store control what they index, how they weight metadata, and what signals they use to rank apps. They do not follow the same rules as Google web search.

Several specific differences matter:

In web SEO, links from authoritative sites are the dominant ranking signal. In ASO, there are no external links. The store's algorithm weights keyword relevance in metadata, install velocity, ratings, engagement, and revenue signals.

In web SEO, content length and depth can be optimized continuously. In ASO, every character is constrained. Your app title has 30 characters on the App Store and 50 on Google Play. Your keyword field on iOS has 100 characters. Every character choice is a strategic trade-off.

In web SEO, you optimize individual pages for individual queries. In ASO, a single listing competes across hundreds or thousands of keywords simultaneously.

Here is the question that should orient your ASO strategy: which specific keyword does your ideal user type when they are looking for an app that does what yours does, and does your listing currently rank in the top 10 results for that keyword?

---

## How App Store Search Works

Both the App Store and Google Play use a combination of relevance signals and behavioral signals to rank apps.

Relevance signals come from your metadata: the title, subtitle or short description, keyword field (iOS only), description, and developer name. The store's algorithm checks whether your metadata contains keywords that match a user's search.

Behavioral signals come from installs, ratings, reviews, engagement, retention, and revenue. An app that converts a high percentage of listing visitors into installs, earns strong ratings, and retains users sends signals that indicate quality.

The relationship between these two signal types is important. You need sufficient keyword relevance to appear in search results. But relevance alone does not rank you at the top. Behavioral signals determine who wins among apps with similar relevance.

This means two strategies must work together. You optimize metadata to capture keyword relevance across a targeted keyword set. And you optimize your listing's conversion rate (install rate) and your in-app experience (to drive ratings and retention) to build the behavioral signals that move you up.

---

## Keyword Research for App Stores

App store keyword research differs from web keyword research in its tools and logic.

### Sources for App Store Keywords

Your users' language: what words do your current users use when describing your app to others? Survey your users or read your reviews. The language users choose naturally is often more aligned with search behavior than internal product terminology.

Competitor listings: read your top competitors' titles, subtitles, and descriptions. Competitors who have optimized their listings have already validated which keywords to target.

App store autocomplete: type a partial query into the App Store or Google Play search bar. The autocomplete suggestions show real search queries users perform. These are high-value keyword signals.

Keyword tools: AppFollow, AppTweak, Sensor Tower, MobileAction, and data.ai (formerly App Annie) all provide keyword volume estimates, difficulty scores, and keyword suggestions specific to app stores. These tools are the most important investment for serious ASO.

Review mining: read your reviews and your competitors' reviews. Users describe what they were looking for and what they found. Reviews surface vocabulary that maps to search intent.

### Keyword Evaluation Criteria

Volume: how many searches does this keyword receive? Higher volume means more potential traffic if you rank.

Difficulty: how strong are the apps currently ranking for this keyword? A keyword where the top 5 results are all well-established apps with millions of reviews is much harder to rank for than a keyword where the top results are smaller apps.

Relevance: will users who searched for this keyword actually want your app? Traffic from irrelevant keywords generates installs from users who immediately uninstall, which damages your behavioral signals.

Your current ranking: if you already rank in position 6 for a keyword, investing further in that keyword might move you to position 1 or 2 with meaningful impact. If you rank at position 85, the gap to page 1 is much larger.

The best keywords to prioritize are those with sufficient volume, moderate difficulty (where you have a realistic path to page 1), and strong relevance. Very high difficulty keywords are a longer-term play after you have built strong behavioral signals.

---

## Metadata Optimization: iOS App Store

### Title (30 characters)

The title is the most important metadata field for iOS keyword indexing. The App Store's algorithm gives the highest weight to keywords in the title.

Your title should include your brand name and your most important primary keyword. The format "Brand Name: Primary Keyword" is the most common approach. For example: "Notion: Notes, Docs, Tasks" or "Headspace: Mindful Meditation."

You have 30 characters. Count precisely. "Invoicing for Freelancers" is 25 characters and leaves 5 for your brand name abbreviation. Plan your character allocation before writing.

Do not repeat in your title keywords that are already covered by your subtitle or keyword field. The App Store indexes each keyword across metadata fields. Repetition wastes valuable character space.

### Subtitle (30 characters)

The subtitle appears below the app name in search results and on the listing page. It is the second most important field for keyword indexing on iOS.

Use the subtitle to include your second and third priority keywords. These should be keywords that did not fit in your title or that are secondary to your primary search intent.

The subtitle also serves as a short value proposition for users scanning search results. It should contain keywords that are also readable as a short benefit statement. "Track expenses, save time" covers two keywords while being readable as a benefit.

### Keyword Field (100 characters)

The iOS keyword field is invisible to users but indexed by the App Store. Use it to target keywords that do not appear naturally in your title, subtitle, or description.

Rules for the keyword field:

Use commas to separate keywords. Do not add spaces after commas. This saves characters.
Do not include words already in your title or subtitle. The algorithm ignores repetition.
Do not include your app name, category name, or competitor app names.
Include singular forms only. The App Store indexes both singular and plural automatically.
Include common misspellings of your primary keywords if they are genuinely common.
Use all 100 characters. Every unused character is a missed opportunity.

An example keyword field for an invoicing app: invoice,billing,estimate,quote,time tracking,expense,receipt,freelancer,consultant,small business,payment,client

That is 100 characters. Each keyword is distinct from the title and subtitle.

### Description

The description on iOS is not the primary indexing signal. The App Store search algorithm does not heavily weight description text for keyword ranking. However, the description influences two things: conversion rate (users who scroll and read it before deciding to install) and Google Play indexing (on Play, the description is the primary indexing source).

Write an iOS description that converts. Lead with the most compelling benefits in the first three lines, which are visible before the "more" prompt. Describe specific features in plain language. Include social proof: user count, notable customers, press mentions, or award recognitions.

### What Not to Do

Do not keyword stuff. Descriptions that read like "the best invoicing app for invoicing invoices invoice software" hurt conversion and signal low quality.

Do not include misleading claims. Both stores review listings and will reject apps that make false claims about functionality.

Do not copy competitor descriptions. Apple will reject duplicate content.

---

## Metadata Optimization: Google Play

Google Play indexes keywords differently from iOS. The short description (80 characters) and long description (4,000 characters) are both indexed by Google Play's search algorithm, and the description content carries more weight than on iOS.

### Title (50 characters)

Google Play allows 50 characters in the title. Use the additional characters beyond iOS to include more keyword detail. A typical format: "Brand Name - Primary Keyword and Secondary Use Case."

### Short Description (80 characters)

The short description appears in search results below the app title. It is indexed for keywords and serves as a conversion copywriting element. Treat it similarly to the iOS subtitle but with 80 characters to work with.

Write the short description as a compelling benefit statement that also contains your primary keywords. "Track invoices and get paid faster" covers invoicing keywords while being benefit-oriented and readable.

### Long Description (4,000 characters)

Unlike iOS, the Google Play long description is a significant indexing source. Include your target keywords naturally throughout the description. Repeat primary keywords three to five times. Include secondary keywords throughout.

Structure the description with headers or clear paragraph breaks. Google Play renders basic formatting. Use short paragraphs. Lead with the highest-value benefits.

Research the descriptions of your top-ranked competitors for your primary keywords. Note which keywords appear consistently and how they are distributed through the text.

Do not pad the description to 4,000 characters with low-quality text. Quality content that reads naturally and is relevant will convert better and perform better algorithmically.

### Developer Name

The developer name is indexed by both stores. If your company name contains relevant keywords, this is a marginal but real benefit. A developer named "Freelance Tools Inc" will have a small advantage over "XYZ Corp" for freelance-related keywords.

---

## Screenshot and Preview Video Strategy

Screenshots are the highest-impact conversion element on your store listing. Users make install decisions partly based on screenshots before reading a word of your description.

Most users view only the first two to three screenshots in search results before deciding to tap through or install. Those first screenshots carry the most weight.

### Screenshot Composition Principles

Show the product. Screenshots should show actual app screens, not abstract marketing imagery. Users want to see what the app looks like before they install.

Lead with the primary benefit. Your first screenshot should communicate the single most important thing your app does. Not your logo. Not an abstract value statement. The key feature or outcome, shown in the app interface.

Add captions. Both stores allow caption text on screenshots. Use captions to call out the feature or benefit shown in each screenshot. Keep captions short (three to six words). Place captions at the top or bottom consistently.

Maintain a visual hierarchy. Screenshots 1 through 3 should cover your three most important features or benefits in order of importance. Screenshots 4 through 8 (or however many you use) can cover secondary features, social proof, or specific use cases.

Design for portrait vs. landscape. For portrait apps, use portrait screenshots. For landscape apps (games, certain utilities), use landscape. The App Store requires at least one portrait screenshot for portrait apps.

### Preview Videos

Preview videos (iOS) and promotional videos (Google Play) autoplay in search results on supported devices. A well-executed preview video can significantly increase conversion rate.

The first three to five seconds are critical. The video autoplays without sound on iOS by default. Your video must communicate value visually before a user opts to enable sound.

Show the app in action. Demonstrate the primary feature set. Focus on the experience, not an abstract brand message.

Keep iOS preview videos to 15 to 30 seconds. Keep Google Play promo videos to 30 to 120 seconds, with 30 to 60 seconds being the practical effective range.

Avoid videos that focus entirely on brand imagery without showing the actual app. Users watching a preview video want to see whether the app is right for them. Give them that information.

---

## Rating and Review Strategy

Ratings are one of the most influential signals in app store search ranking and one of the most powerful conversion drivers on your listing. An app with a 4.7 star average and 10,000 ratings outperforms an app with a 3.9 star average on both dimensions.

### When to Ask for Ratings

Both stores have in-app review prompt APIs (SKStoreReviewRequest on iOS, ReviewManager on Android). Use these APIs rather than building custom prompts. The native prompt is optimized for conversion and compliant with store guidelines.

The timing of the prompt significantly affects the rating you receive. Ask for a rating after a positive user event, not after a frustrating one.

Positive trigger moments:

- After a user completes a task successfully for the third time
- After a user shares or exports something they created
- After a session where the user achieved their primary goal
- After a user has been using the app for 7 days and has returned at least 3 times

Avoid asking for ratings immediately after a user encounters an error, after a failed payment, or during their first session before they have experienced any value.

### Responding to Reviews

Both stores allow you to respond to user reviews. Responding to negative reviews has two benefits: it sometimes converts a negative reviewer into a more positive one, and it signals to potential installers that your team is responsive and cares.

Keep responses professional, specific, and non-defensive. Acknowledge the issue. Explain what you have done or are doing about it. Invite the user to contact support for direct resolution.

Responding to positive reviews is also worthwhile, especially for detailed positive reviews. A short, genuine thank-you builds community and encourages other users to leave reviews.

### Rating Gating

Do not filter users to only show the rating prompt to those who indicate they are satisfied. Both Apple and Google prohibit this practice in their guidelines. The prompt must be shown without prescreening for user sentiment.

---

## A/B Testing on Store Listings

Both the App Store and Google Play offer built-in tools for A/B testing your listing.

### App Store Product Page Optimization (PPO)

Apple's Product Page Optimization lets you test up to three variants of your screenshots, app icon, and preview video against your control page. The test runs automatically and shows split traffic between your control and variants.

After you collect sufficient data (Apple recommends at least 90 days or until Apple declares a winner with 95% confidence), apply the winning variant as your permanent listing.

Test one element at a time when possible. Testing a different icon versus different screenshots versus a different video simultaneously makes it impossible to attribute the performance difference to a specific change.

The most impactful elements to test are those with the highest conversion influence: the app icon (visible in search results before a user taps your listing) and the first two screenshots (visible in the search result card for some query types).

### Google Play Store Listing Experiments

Google Play Console offers Store Listing Experiments for testing icon, screenshots, short description, and long description. You can set the traffic split (typically 50/50) and run tests until statistical significance is reached.

Google Play also offers a "pre-launch report" through Firebase App Distribution, which can test your listing with a small group before a broad launch.

Run at least two to three experiments per year on your store listing. Treat your listing as a product that can always be improved rather than a one-time creative decision.

---

## Competitor Listing Analysis

Understanding your competitors' ASO approach helps you identify keyword gaps and conversion differentiators.

### What to Analyze

Competitor keywords: use AppTweak, Sensor Tower, or AppFollow to see which keywords your competitors rank for that you do not. These are your keyword opportunities.

Competitor title and subtitle structure: how do competitors format their title? What keywords do they include? Are there keyword choices your competitors are making that you should evaluate for your own listing?

Competitor screenshot design: what features do competitors highlight in their first three screenshots? What captions do they use? Are there conversion patterns you can learn from or differentiate against?

Competitor ratings profile: what is the distribution of ratings? What are the most common themes in negative reviews? Those negative review themes are opportunities to differentiate your listing by specifically addressing the concern your competitor does not.

Competitor review response behavior: do your top competitors respond to reviews? If not, this is an opportunity to demonstrate responsiveness that they do not offer.

### Building a Competitive Map

Create a simple spreadsheet tracking your top five to eight competitors across these dimensions:

- App Store rating and review count
- Primary keywords in title and subtitle
- First screenshot theme
- Notable claims or social proof in listing

Review and update this map quarterly. ASO is not static. Competitors update their listings, launch A/B tests, and respond to algorithm changes. Staying current on competitor moves helps you identify when the competitive landscape has shifted.

---

## Getting Started

If you are starting ASO from scratch or auditing an existing app, work through these steps in order.

Step one: conduct keyword research. Use AppTweak or a similar tool to identify 50 to 100 candidate keywords. Evaluate each on volume, difficulty, and relevance. Select 20 to 30 target keywords.

Step two: audit your current metadata against your keyword targets. How many of your target keywords appear in your title, subtitle, keyword field, or description? Which priority keywords are missing from your metadata?

Step three: update your metadata. Prioritize highest-volume, most relevant keywords in your title. Fill your subtitle and keyword field with the next tier. Ensure your description covers all targets naturally.

Step four: analyze your screenshots. Compare them against your top competitors. Identify whether your first screenshot communicates your primary value proposition clearly. If not, redesign.

Step five: implement a rating prompt at the right moment in your app flow. Verify that the native store prompt is triggering correctly.

Step six: set up your first store listing experiment. Test your most impactful visual asset (icon or first screenshot) against an alternative.

Step seven: track your keyword rankings weekly using your ASO tool. Monitor ranking changes after metadata updates. Adjust your keyword strategy based on ranking movement and install volume.

ASO is an ongoing program, not a one-time project. The stores change their algorithms. Competitors update their listings. Your product evolves and offers new value propositions. A quarterly review and update cadence keeps your listing competitive.