Back to Details

app-store-optimization

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

App Store Optimization (ASO)

App Store优化（ASO）

Search visibility and conversion optimization for App Store product pages. This skill covers strategic metadata decisions -- which keywords to target, how to structure descriptions for conversion, and how to use Custom Product Pages and in-app events for discoverability. For metadata compliance rules (character limits, screenshot device requirements, rejection triggers), see the 
app-store-review
skill.
针对App Store产品页面的搜索曝光度与转化率优化。本技能涵盖元数据策略决策——选择目标关键词、如何构建高转化描述，以及如何利用Custom Product Pages和应用内活动提升曝光度。有关元数据合规规则（字符限制、截图设备要求、拒审触发因素），请查看
app-store-review
技能。

Contents

目录

Overview

概述

ASO has two pillars:
  1. Search visibility -- ranking for relevant queries so users find the app.
  2. Conversion rate -- convincing users who land on the product page to download.
Apply this skill when a developer asks about improving discoverability, keyword strategy, download conversion, or any product page element that affects either pillar.
For metadata format rules and compliance guardrails, see the 
app-store-review
skill. This skill assumes the developer is working within those constraints and focuses on strategy.
ASO有两大核心支柱：
  1. 搜索曝光度——在相关搜索查询中获得高排名，让用户找到应用。
  2. 转化率——说服进入产品页面的用户下载应用。
当开发者询问提升曝光度、关键词策略、下载转化率，或任何影响上述两大支柱的产品页面元素相关问题时，可应用本技能。
有关元数据格式规则与合规准则，请查看
app-store-review
技能。本技能假设开发者已在这些约束下开展工作，重点聚焦策略层面。

Title and Subtitle Strategy

标题与副标题策略

Apple indexes the app name and subtitle for search. Together they provide 60 characters (30 + 30) of indexed, high-visibility keyword real estate.
苹果会对应用名称和副标题进行搜索索引。两者合计提供60字符（30+30）的高曝光关键词空间。

Positioning framework

定位框架

PatternWhen to useExample
Brand -- KeywordEstablished brand with recognition
Notion -- Notes & Docs
Keyword -- BrandNew app competing on category terms
Budget Tracker -- Pennywise
Brand + Keyword blendBrand name contains a keyword naturally
Headspace: Sleep & Meditation
模式使用场景示例
品牌——关键词具有知名度的成熟品牌
Notion -- Notes & Docs
关键词——品牌竞争品类通用术语的新应用
Budget Tracker -- Pennywise
品牌+关键词融合品牌名称自然包含关键词
Headspace: Sleep & Meditation

Rules

规则

  • Do not repeat words between the name and subtitle -- Apple indexes both, so duplicates waste characters.
  • Front-load the highest-value keyword in whichever field has more room.
  • Avoid generic filler words ("the", "best", "app") -- they consume space without search value.
  • The subtitle should communicate the primary value proposition, not a tagline.
  • 不要在名称和副标题之间重复用词——苹果会对两者都进行索引，重复会浪费字符。
  • 在剩余空间更多的字段中前置高价值关键词。
  • 避免使用通用填充词（"the"、"best"、"app"）——它们会占用空间但无搜索价值。
  • 副标题应传达核心价值主张，而非标语。

Keyword Field Strategy

关键词字段策略

The keyword field is 100 characters, comma-separated, no spaces after commas. See the 
app-store-review
skill for the full format rules. This section focuses on which keywords to choose and how to prioritize them.
关键词字段共100字符，采用逗号分隔，逗号后无空格。有关完整格式规则，请查看
app-store-review
技能。本节重点聚焦关键词选择与优先级排序。

Research process

研究流程

  1. Competitor audit -- identify the top 5-10 competitors in the category and note which keywords appear in their titles, subtitles, and descriptions.
  2. Category analysis -- identify terms users associate with the app's category that competitors may be missing.
  3. Search Ads signals -- run Apple Search Ads discovery campaigns to surface high-intent queries with actual impression and tap data.
  4. Iterate each release -- update keywords based on Search Ads performance, App Analytics impressions, and conversion data.
  1. 竞品审计——识别品类内Top5-10竞品，记录其标题、副标题和描述中出现的关键词。
  2. 品类分析——识别用户关联到该应用品类但竞品可能遗漏的术语。
  3. 搜索广告信号——运行Apple Search Ads发现型广告系列，获取具有真实曝光和点击数据的高意向查询词。
  4. 每次迭代更新——根据搜索广告表现、App Analytics曝光数据和转化数据更新关键词。

Prioritization

优先级排序

Rank candidate keywords by three factors:
FactorWeightSignal
RelevanceHighestDoes the keyword describe what the app actually does?
Search volumeMediumAre users actually searching for this term?
CompetitionLowerHow many apps target this keyword?
Relevance always wins. A high-volume keyword that does not describe the app will get impressions but not conversions.
根据三大因素对候选关键词进行排名：
因素权重信号
相关性最高关键词是否准确描述应用的实际功能？
搜索量中等用户是否真的在搜索该术语？
竞争度较低有多少应用以该关键词为目标？
相关性始终是第一位的。与应用不匹配的高搜索量关键词只会带来曝光，无法转化。

Tactical rules

战术规则

  • Deduplicate against title and subtitle -- Apple already indexes those words.
  • Use singular forms only -- Apple matches both singular and plural from singular.
  • Omit the category name -- Apple adds the app's primary category to search automatically.
  • Omit spaces after commas -- they count against the 100-character limit.
  • Consider abbreviations and common misspellings if they are genuine search terms.
  • Place highest-value keywords first -- there is some evidence that position affects ranking weight.
See: references/keyword-research-methodology.md for the full research process, scoring framework, and indexing details.
  • 排除标题和副标题中的重复词——苹果已对这些词进行索引。
  • 仅使用单数形式——苹果会从单数形式匹配单数和复数。
  • 省略品类名称——苹果会自动将应用的主品类添加到搜索索引中。
  • 逗号后不要加空格——它们会占用100字符的限额。
  • 如果是真实搜索词，可考虑缩写和常见拼写错误。
  • 将高价值关键词放在前面——有证据表明位置会影响排名权重。
参考： references/keyword-research-methodology.md 获取完整研究流程、评分框架和索引细节。

Description Structure

描述结构

The App Store description does not affect search ranking -- Apple does not index it for keyword matching. It does affect conversion: users who expand the description are evaluating whether to download.
App Store描述不影响搜索排名——苹果不会将其用于关键词匹配。但它会影响转化率：展开描述的用户正在评估是否下载应用。

Four-part structure

四部分结构

  1. Hook (first 1-3 lines) -- the only text visible before the "more" fold. Lead with the strongest benefit or differentiator. This is the most important copy on the page.
  2. Feature highlights -- 4-6 short feature descriptions. Use Unicode bullet characters (•) since the App Store does not render markdown. Focus on outcomes, not technical details.
  3. Social proof -- awards, press quotes, user count milestones, or notable ratings. One or two lines.
  4. Call to action -- a closing line encouraging the download. Keep it short and benefit-focused.
  1. 钩子（Hook）（前1-3行）——“查看更多”折叠前唯一可见的文本。以最强的利益点或差异化优势开头。这是页面上最重要的文案。
  2. 功能亮点——4-6条简短的功能描述。使用Unicode项目符号（•），因为App Store不渲染markdown。聚焦用户收益，而非技术细节。
  3. 社交证明——奖项、媒体报道、用户数量里程碑或显著评分。1-2行即可。
  4. 行动号召（CTA）——鼓励下载的收尾语句。简短且聚焦利益点。

Formatting notes

格式说明

  • The App Store does not render markdown, HTML, or rich text. Use plain text with Unicode characters for structure.
  • Short paragraphs with line breaks between them. Walls of text kill conversion.
  • Write per locale -- translate the structure, not the words. See Localized Metadata Optimization.
  • App Store不渲染markdown、HTML或富文本。使用纯文本搭配Unicode字符构建结构。
  • 短段落，段落间换行。大段文字会降低转化率。
  • 按地区撰写——适配结构，而非直接翻译文字。请查看本地化元数据优化。

Promotional Text

宣传文案

Promotional text is the only metadata field changeable without submitting a new binary. It appears above the description and is limited to 170 characters.
宣传文案是无需提交新二进制包即可修改的唯一元数字段。它显示在描述上方，限制为170字符。

Rotation strategy

轮换策略

Update promotional text to match current context:
TriggerExample text
Feature launch
New: Collaborate in real time with shared workspaces
Seasonal event
Plan your holiday travel -- route sharing now available
Award or press
Winner of Apple Design Award 2025
Sale or promotion
Premium features free through January
In-app event
Join the Spring Challenge -- starts March 15
Do not leave promotional text static across releases. If there is nothing timely to promote, rotate between the app's strongest selling points.
根据当前场景更新宣传文案：
触发场景示例文案
功能上线
New: Collaborate in real time with shared workspaces
季节性活动
Plan your holiday travel -- route sharing now available
获奖或媒体报道
Winner of Apple Design Award 2025
促销活动
Premium features free through January
应用内活动
Join the Spring Challenge -- starts March 15
不要让宣传文案在多个版本中保持不变。如果没有时效性内容可推广，可轮换应用的核心卖点。

Screenshot and Preview Optimization

截图与预览优化

Most users never scroll past the first 3 visible screenshots. These slots determine whether a user engages with the full product page or moves on.
大多数用户不会滚动查看前3张可见截图之外的内容。这些位置决定了用户是继续浏览完整产品页面还是离开。

First 3 screenshots

前3张截图

  • Lead with the primary value proposition -- the screen that best demonstrates why someone should download.
  • Never place onboarding, splash, or loading screens in the first 3 slots.
  • Each screenshot should demonstrate a different benefit or feature.
  • 以核心价值主张开头——最能体现用户下载理由的界面。
  • 切勿将引导页、启动页或加载页放在前3个位置。
  • 每张截图应展示不同的利益点或功能。

Caption writing

说明撰写

  • Write benefit-oriented captions, not feature labels. "Never miss a deadline" converts better than "Calendar View".
  • Keep captions to 2-5 words above the screenshot and one short line below.
  • Use action verbs: "Track", "Share", "Discover", "Build".
  • 撰写聚焦利益点的说明，而非功能标签。“永不错过截止日期”比“日历视图”转化率更高。
  • 截图上方的说明控制在2-5个词，下方配一行简短文字。
  • 使用动作动词：“Track”、“Share”、“Discover”、“Build”。

Ordering strategy

排序策略

SlotPurpose
1Primary value proposition -- the single best reason to download
2Core differentiator -- what sets this app apart from competitors
3Secondary feature -- the next strongest selling point
4+Supporting features, social proof, or edge cases
位置目的
1核心价值主张——下载应用的最佳理由
2核心差异化优势——与竞品的区别
3次要功能——下一个核心卖点
4+辅助功能、社交证明或边缘场景

App preview video

应用预览视频

If a preview video is present, it occupies the first slot. The first frame becomes the poster image when autoplay is disabled -- choose a frame that works as a standalone screenshot.
For screenshot device requirements and compliance rules, see the 
app-store-review
skill.
如果有预览视频，它会占据第一个位置。当自动播放关闭时，第一帧会成为海报图——选择可作为独立截图的帧。
有关截图设备要求和合规规则，请查看
app-store-review
技能。

In-App Review Prompts

应用内评分提示

StoreKit provides two APIs for requesting ratings:
SwiftUI -- use 
RequestReviewAction
via the environment:
swift
@Environment(\.requestReview) private var requestReview

func onTaskCompleted() {
    requestReview()
}
UIKit -- use 
AppStore.requestReview(in:)
:
swift
if let scene = view.window?.windowScene {
    AppStore.requestReview(in: scene)
}
StoreKit提供两个请求评分的API：
SwiftUI——通过环境使用
RequestReviewAction
：
swift
@Environment(\.requestReview) private var requestReview

func onTaskCompleted() {
    requestReview()
}
UIKit——使用
AppStore.requestReview(in:)
：
swift
if let scene = view.window?.windowScene {
    AppStore.requestReview(in: scene)
}

System behavior

系统行为

  • The system enforces a maximum of 3 prompts per 365-day period per device for users who have not yet rated the app.
  • The API is a request, not a guarantee -- StoreKit decides whether to show the prompt.
  • During development, the prompt always appears. In TestFlight, it never appears.
  • 系统对未评分用户的设备强制执行每年最多3次提示的限制。
  • API是请求而非保证——StoreKit决定是否显示提示。
  • 开发期间，提示始终显示。在TestFlight中，提示从不显示。

Prompt timing

提示时机

Good triggersBad triggers
After completing a meaningful taskOn first launch
After achieving a milestone or streakImmediately after an error or crash
After a positive in-app momentDuring onboarding
After the user has been active for several sessionsIn response to a button tap
Do not gate the prompt behind a "Rate this app?" dialog -- Apple discourages intercepting the system prompt and may reject apps that pre-screen.
合适触发时机错误触发时机
完成有意义的任务后首次启动时
达成里程碑或连续使用后错误或崩溃后立即触发
应用内积极体验后引导流程中
用户活跃多个会话后响应用户按钮点击时
不要在“是否评分？”弹窗后再触发系统提示——苹果不鼓励拦截系统提示，此类应用可能被拒审。

Persistent review link

持久评分链接

For a settings screen or "Rate us" option, link directly to the App Store review page using the URL format:
https://apps.apple.com/app/id{APP_ID}?action=write-review
This opens the review writing screen directly and is not subject to the 3x/year system limit.
For the full StoreKit API surface, see the 
storekit
skill.
对于设置页面或“给我们评分”选项，直接链接到App Store评分页面，格式如下：
https://apps.apple.com/app/id{APP_ID}?action=write-review
这会直接打开评分撰写页面，不受每年3次的系统限制。
有关完整StoreKit API，请查看
storekit
技能。

Custom Product Pages

Custom Product Pages

Custom Product Pages allow up to 35 variant product pages per app. Each variant can have different screenshots, app preview videos, and promotional text -- tailored to a specific audience or acquisition channel.
Custom Product Pages允许每个应用最多创建35个变体产品页面。每个变体可拥有不同的截图、应用预览视频和宣传文案——针对特定受众或获客渠道定制。

Use cases

使用场景

AudienceCustomization
Paid search adsScreenshots matching the search intent of the ad group keywords
Social media campaignScreenshots and captions tailored to the campaign creative
Feature-specific landingLead screenshot showing the specific feature being promoted
Seasonal campaignSeasonal screenshots and promotional text
受众定制方向
付费搜索广告截图匹配广告组关键词的搜索意图
社交媒体营销活动截图和说明适配活动创意
特定功能落地页首屏截图展示推广的特定功能
季节性活动季节性截图和宣传文案

Setup

设置步骤

  • Each Custom Product Page gets a unique App Store URL usable in ad campaigns, deep links, and web pages.
  • Pages can be localized independently.
  • Create pages in App Store Connect under the Custom Product Pages tab.
  • Name pages descriptively for internal tracking (e.g., "Search-FitnessTracking", "Social-HolidayCampaign").
See: references/product-page-variants.md for setup details, URL structure, and campaign mapping strategy.
  • 每个Custom Product Page会获得唯一的App Store URL，可用于广告活动、深度链接和网页。
  • 页面可独立本地化。
  • 在App Store Connect的Custom Product Pages标签下创建页面。
  • 为页面起描述性名称以便内部追踪（如"Search-FitnessTracking"、"Social-HolidayCampaign"）。
参考： references/product-page-variants.md 获取设置细节、URL结构和活动映射策略。

In-App Events

应用内活动

In-app events surface in App Store search results, on the Today tab, and in personalized recommendations. They increase visibility during the event window and can re-engage lapsed users.
应用内活动会在App Store搜索结果、Today标签页和个性化推荐中展示。它们在活动窗口内提升曝光度，还能召回流失用户。

Event types

活动类型

BadgeWhen to use
ChallengeTime-limited goals users can work toward
CompetitionHead-to-head or leaderboard contests
Live EventReal-time experiences (concerts, sports, streams)
Major UpdateSignificant new features or redesigns
New SeasonSeasonal content refreshes
PremiereFirst-time content availability
Special EventLimited-time promotions or celebrations
标识使用场景
Challenge用户可参与的限时目标
Competition一对一或排行榜竞赛
Live Event实时体验（音乐会、体育赛事、直播）
Major Update重大新功能或重新设计
New Season季节性内容更新
Premiere首次上线的内容
Special Event限时促销或庆祝活动

Metadata limits

元数据限制

FieldLimit
Event name30 characters
Short description50 characters
Long description120 characters
Event card imageRequired (1920x1080 or similar 16:9)
字段限制
活动名称30字符
短描述50字符
长描述120字符
活动卡片图片必填（1920x1080或类似16:9比例）

Strategy

策略

  • Schedule events around feature releases, seasonal moments, or content drops.
  • Use the event name and short description as additional keyword surfaces -- Apple indexes event metadata for search.
  • Events appear on the product page and in search results, giving the app a visual badge that increases tap-through rate.
  • Overlap events strategically: end the current event as the next one begins to maintain continuous search visibility.
See: references/product-page-variants.md for event scheduling templates.
  • 围绕功能上线、季节性节点或内容更新安排活动。
  • 将活动名称和短描述作为额外关键词载体——苹果会对活动元数据进行搜索索引。
  • 活动会显示在产品页面和搜索结果中，为应用增加视觉标识，提升点击率。
  • 策略性地重叠活动：当前活动结束时启动下一个活动，维持持续的搜索曝光度。
参考： references/product-page-variants.md 获取活动排期模板。

Product Page Optimization

产品页面优化

App Store Connect provides native A/B testing for product page elements.
App Store Connect提供产品页面元素的原生A/B测试功能。

What can be tested

可测试内容

  • App icon (alternate icons)
  • Screenshots (order, content, captions)
  • App preview video
Only one treatment can be tested at a time. The default product page serves as the control.
  • 应用图标（替代图标）
  • 截图（排序、内容、说明）
  • 应用预览视频
每次只能测试一个变体。默认产品页面作为对照组。

Test design

测试设计

  • Run tests for a minimum of 7 days to account for day-of-week variation.
  • Ensure sufficient traffic for statistical significance -- low-traffic apps may need longer test durations.
  • Test one variable at a time (e.g., screenshot order OR caption copy, not both simultaneously).
  • Changes to the default locale only affect that locale.
  • 测试至少运行7天，以覆盖周度波动。
  • 确保流量足够以获得统计显著性——低流量应用可能需要更长测试时长。
  • 每次只测试一个变量（如截图排序或说明文案，而非同时测试两者）。
  • 默认地区的更改仅影响该地区。

Interpreting results

结果解读

  • Focus on conversion rate lift (impressions-to-downloads), not absolute download numbers.
  • App Store Connect shows confidence intervals -- do not apply a winning treatment until the test reaches statistical significance.
  • After applying a winner, wait before starting the next test to establish a clean baseline.
  • 聚焦转化率提升（曝光到下载的转化），而非绝对下载量。
  • App Store Connect会显示置信区间——测试达到统计显著性前不要应用获胜变体。
  • 应用获胜变体后，等待一段时间再启动下一次测试，以建立清晰的基准。

Ratings and Review Management

评分与评论管理

Average rating affects both conversion and search ranking. The threshold effects are significant: apps below 4.0 stars see measurably lower conversion, and apps above 4.5 stars convert noticeably better.
平均评分会影响转化率和搜索排名。阈值效应显著：评分低于4.0星的应用转化率明显更低，评分高于4.5星的应用转化率则显著提升。

Review response strategy

评论回复策略

  • Respond to negative reviews in App Store Connect -- a professional response improves perceived quality even without changing the rating number.
  • Acknowledge the issue, state what is being done (or has been fixed), and keep the tone neutral.
  • Turn negative reviews into keyword signals -- users describe problems using search-relevant language.
  • 在App Store Connect中回复负面评论——专业的回复即使不改变评分，也能提升感知质量。
  • 承认问题，说明正在采取的措施（或已修复的内容），保持语气中立。
  • 将负面评论转化为关键词信号——用户会用与搜索相关的语言描述问题。

Rating reset

评分重置

When submitting a new version, you can choose to reset the displayed rating. Use this strategically:
SituationRecommendation
Current rating is significantly below the app's quality after major improvementsReset
Current rating is strong (4.5+)Do not reset
Bug fix release with no quality improvementDo not reset
Major redesign with mixed early feedback expectedWait for stabilization, then reset on a subsequent update
提交新版本时，可选择重置显示的评分。策略性使用该功能：
场景建议
当前评分远低于重大改进后的应用质量重置
当前评分良好（4.5+）不重置
仅修复Bug，无质量提升不重置
重大重新设计，预计早期反馈褒贬不一等待反馈稳定后，在后续更新中重置

Localized Metadata Optimization

本地化元数据优化

Localizing ASO is not the same as translating the app UI. Keyword strategy, descriptions, and screenshot captions must be researched and written per market, not machine-translated from the primary locale.
ASO本地化不同于应用UI翻译。关键词策略、描述和截图说明必须针对每个市场进行研究和撰写，而非从主地区机器翻译。

Key principles

核心原则

  • Research keywords per market. The most-searched term for "photo editor" in Japanese is not a direct translation of "photo editor."
  • Rewrite descriptions per locale. Adapt the hook-features-proof-CTA structure to local conventions and selling points.
  • Some markets index English keywords. Japan, South Korea, and several other markets index both the local language and English keyword fields. Use this to capture additional search terms.
  • Localize screenshot captions. Captions in the user's language convert better than untranslated English.
For in-app string localization (String Catalogs, FormatStyle, right-to-left layout), see the 
ios-localization
skill.
  • 按市场研究关键词——日语中“照片编辑器”的最高搜索词并非“photo editor”的直接翻译。
  • 按地区重写描述——将钩子-功能-证明-CTA结构适应当地惯例和卖点。
  • 部分地区会索引英文关键词——日本、韩国等多个地区会同时索引本地语言和英文关键词字段。利用这一点获取额外搜索词。
  • 本地化截图说明——用户母语的说明比未翻译的英文转化率更高。
有关应用内字符串本地化（String Catalogs、FormatStyle、从右到左布局），请查看
ios-localization
技能。

Common Mistakes

常见误区

  1. Duplicating title words in the keyword field. Apple indexes the title and subtitle automatically -- repeating those words in the keyword field wastes characters.
  2. Writing feature-descriptive screenshot captions instead of benefit-oriented ones. "Calendar View" converts worse than "Never miss a deadline" -- lead with the user outcome.
  3. Translating keywords instead of researching per-market terms. Direct translation misses local search behavior and high-volume terms specific to each market.
  4. Prompting for reviews after a negative experience. Calling 
    requestReview()
    after an error, a failed transaction, or during onboarding generates low ratings.
  5. Ignoring the first three screenshot slots. Most users never scroll -- placing an onboarding or splash screen first wastes the highest-impact real estate.
  6. Never rotating promotional text. Promotional text is the only field changeable without a new build -- leaving it static misses conversion opportunities.
  7. Running A/B tests with insufficient duration. Product page optimization tests need at least 7 days and meaningful traffic to reach statistical significance.
  8. Adding spaces after commas in the keyword field. Spaces count against the 100-character limit -- use 
    keyword1,keyword2
    not 
    keyword1, keyword2
    .
  9. Using identical screenshots for every Custom Product Page. Custom Product Pages exist to tailor messaging per audience segment -- reusing identical assets defeats the purpose.
  10. Not responding to negative App Store reviews. Unanswered negative reviews signal abandonment to prospective users and miss an opportunity to demonstrate responsiveness.
  1. 在关键词字段中重复标题用词——苹果会自动对标题和副标题进行索引，在关键词字段重复会浪费字符。
  2. 撰写聚焦功能的截图说明而非利益点导向——“日历视图”比“永不错过截止日期”转化率低——要以用户收益为核心。
  3. 翻译关键词而非按市场研究术语——直接翻译会忽略本地搜索行为和特定市场的高搜索量术语。
  4. 在负面体验后请求评分——在错误、交易失败或引导流程中调用
    requestReview()
    会产生低评分。
  5. 忽视前3张截图位置——大多数用户不会滚动——将引导页或启动页放在首位会浪费最高价值的展示空间。
  6. 从不轮换宣传文案——宣传文案是无需新构建包即可修改的唯一字段——保持静态会错失转化机会。
  7. 运行时长不足的A/B测试——产品页面优化测试至少需要7天和足够流量才能达到统计显著性。
  8. 在关键词字段的逗号后加空格——空格会占用100字符限额——使用
    keyword1,keyword2
    而非
    keyword1, keyword2
    。
  9. 为所有Custom Product Page使用相同截图——Custom Product Page的存在是为了针对受众细分定制信息——重复使用相同素材会失去其意义。
  10. 不回复App Store负面评论——未回复的负面评论会向潜在用户传递被遗弃的信号，也错失了展示响应性的机会。

Review Checklist

审核清单

  • Title uses high-value keyword alongside brand name; no words repeated in subtitle
  • Subtitle communicates primary value proposition within 30 characters
  • Keyword field uses all 100 characters; no spaces after commas; no duplicates of title/subtitle words; singular forms only
  • Description follows hook-features-proof-CTA structure; first 3 lines compelling before the fold
  • Promotional text is current and relevant to the latest release or event
  • First 3 screenshots show highest-value screens with benefit-oriented captions
  • App preview video (if present) leads with the core feature in the first 5 seconds
  • requestReview()
    is placed after a positive user moment, not on first launch or after errors
  • Custom Product Pages created for distinct acquisition channels with tailored screenshots
  • In-app events configured for upcoming launches, seasons, or feature releases
  • Metadata localized with per-market keyword research for all supported locales
  • Compliance cross-check: all metadata passes the 
    app-store-review
    skill checklist before submission
  • 标题搭配品牌名称使用高价值关键词；副标题无重复用词
  • 副标题在30字符内传达核心价值主张
  • 关键词字段用完100字符；逗号后无空格；无标题/副标题重复词；仅使用单数形式
  • 描述遵循钩子-功能-证明-CTA结构；折叠前的前3行具有吸引力
  • 宣传文案符合当前版本或活动的时效性
  • 前3张截图展示高价值界面，搭配利益点导向的说明
  • 应用预览视频（如有）前5秒展示核心功能
  • requestReview()
    设置在用户积极体验后，而非首次启动或错误发生后
  • 为不同获客渠道创建Custom Product Page，搭配定制截图
  • 为即将到来的上线、季节或功能更新配置应用内活动
  • 元数据本地化，针对所有支持地区进行市场关键词研究
  • 合规交叉检查：提交前所有元数据通过
    app-store-review
    技能清单审核

References

参考资料

  • Keyword research methodology: references/keyword-research-methodology.md
  • Custom Product Pages, A/B testing, and in-app events: references/product-page-variants.md
  • 关键词研究方法论：references/keyword-research-methodology.md
  • Custom Product Pages、A/B测试和应用内活动：references/product-page-variants.md