翻訳待ち：Show HN: 2026 ASO Complete Guide (With 2025 OCR/AI Tags Update)

AI サービスが一時的に利用できないため、復旧後に翻訳を補完します。

App Store Optimization 2026: The Complete Indie Guide — LaunchShots App Store Optimization 2026: The Complete Indie Guide 15 min read 258 views Summarize this with AI Open this article in your favorite AI assistant and get a quick summary in seconds. App Store Optimization is the closest thing indie developers have to a permanent unfair advantage. 65% of all mobile app downloads begin with a search, the top three results capture 60–75% of taps, and the gap between rank 3 and rank 45 produces 10–20x more organic installs per month. Done well, ASO compounds for years — a single 30-character title change can lift your install rate by 30% and keep producing that lift in perpetuity. Done poorly, ASO is a quiet ceiling on every other growth lever you'll ever pull. This is the complete operator-level guide to App Store Optimization in 2026 for indie developers — every ranking factor, every metadata field, the iOS-vs-Google-Play differences that change everything, and the playbook that lifts apps from page 8 obscurity to top-3 visibility within 90 days. Each section links out to the deep dive on that specific topic; this is the master map for the full ASO surface in 2026. What ASO actually is in 2026 ASO has three jobs that compound on each other: Visibility (traffic): Getting your app to appear in search results for relevant queries. Driven by metadata — title, subtitle, keyword field, description (Google Play only), and screenshot caption text (iOS only). Conversion (downloads): Getting users who see your listing to actually install. Driven by visuals — icon, screenshots, preview video, rating, and listing copy. Retention (ranking signal): Keeping the users you acquire so the algorithm rewards your listing with more impressions. Both stores now monitor uninstalls, session frequency, and crash rates as ranking inputs. The big shift in 2026: conversion rate is itself a ranking signal. Apps with high tap-to-install rates rise in rankings; apps with low conversion get demoted regardless of how many keywords they target. This creates a compounding flywheel — better visuals → higher CVR → higher ranking → more impressions → more downloads → more reviews → better ranking. The flywheel works in reverse too. Skip the fundamentals and your rankings slowly bleed out. The ranking factor hierarchy App Store ranking factors in 2026, ordered by impact: For Apple App Store: App title (30 chars): Strongest ranking signal. Include your primary keyword. Subtitle (30 chars): Second-strongest. Secondary keywords or value prop. Keyword field (100 chars): Hidden field, indexed for ranking. Critical for long-tail visibility. Screenshot caption text: NEW in 2025 — Apple's OCR now indexes screenshot text. This is a fourth metadata surface. Download velocity: First-week and first-day install spikes lift long-term rankings. Star rating: Below 4.0 stars suppresses visibility on competitive keywords. 4.5+ ranks dramatically better. Conversion rate: Tap-to-install rate. Apps that get tapped often rise; apps that get scrolled past fall. Retention/uninstalls: Day 1 and Day 7 retention. High uninstall rates suppress rankings. Technical performance: Crash rates, ANR rates, hangs. Buggy apps get demoted. For Google Play: App title (30 chars): Highest weight signal. Short description (80 chars): Indexed for search. The Google Play equivalent of an iOS subtitle. Full description (4,000 chars): Fully indexed via full-text search. Major difference from iOS. Reviews: Fully indexed — keywords in user reviews create additional ranking entry points. Download velocity: Same as iOS. Star rating: Same as iOS. Conversion rate: Same as iOS. Android Vitals: Crash rate, ANR rate, battery usage — directly suppress rankings for unstable apps. Retention: Same role as iOS. The biggest difference: Apple gives you a hidden 100-character keyword field; Google indexes the full description. Same content goal, very different mechanics for getting there. The 4 iOS ASO fields and how they work Apple's iOS App Store gives you four metadata surfaces. Each one has a specific job — and a deep dive guide: App Name (30 characters): Highest-weight ranking signal. Pair your brand with your primary keyword. "Streak — Habit Tracker" outperforms "Streak" alone for users who don't know your brand. For the deep dive on the title/subtitle pair, see our title vs subtitle guide. Subtitle (30 characters): Second-strongest signal. Secondary keyword + value clarification. Cover an angle the title doesn't. Keyword Field (100 characters, hidden): The most under-optimized iOS field for indie developers. Comma-separated, no spaces between words, no repetitions from title/subtitle. For the rules that govern every character — including the SDK-decoder rule that confuses most indies — see our 100-character keyword guide. Description (4,000 characters, NOT indexed): Counter-intuitive but critical: Apple's description does NOT affect search ranking. It's pure conversion copy. Write for the user, not the algorithm. For the structure that converts visitors to installs, see our 4,000-character description guide. Bonus: Promotional Text (170 characters, NOT indexed, editable anytime): Dynamic conversion lever. Updatable without a new release. For seasonal pushes, new feature highlights, time-limited offers. For the patterns that drive conversion, see our promotional text guide. The 2025 OCR change: screenshot captions are now keyword surfaces The single biggest ASO change in the past 18 months: Apple's algorithm now uses OCR to extract text from your screenshot captions and indexes it for keyword ranking. This was rolled out in mid-2025 and is fully active in 2026. What this means: Screenshot captions are a fourth metadata surface. Whatever text appears in your screenshot designs gets indexed alongside your title, subtitle, and keyword field. Caption text should reinforce your primary keywords. Unlike the keyword field (where repetition wastes space), screenshot captions amplify existing metadata signals. Generic captions waste a ranking opportunity. "Easy to use" and "Beautiful design" rank you for nothing. "Build habits in 21 days" ranks you for "build," "habits," "21 days" simultaneously. Contrast and font size matter for OCR. If Apple's OCR can't read your text, it doesn't index. Use bold, high-contrast captions. The OCR change reframes the screenshot question entirely. Apps now optimize captions for both human conversion AND algorithmic indexing. This is one of the few new ASO levers in years where indies who act early can capture lasting advantage. For the screenshot design patterns that hit both conversion and OCR ranking, see our screenshots that convert guide. Google Play ASO: different field structure, same goals Google Play ASO follows the same Visibility → Conversion → Retention logic, but the metadata structure is different: App title (30 characters): Highest weight, same role as Apple's. Include primary keyword. Short description (80 characters): Equivalent to Apple's subtitle but FULLY INDEXED. Pack your most important secondary keyword here in a natural sentence. Full description (4,000 characters): The big difference. Google indexes the entire description for keyword ranking via full-text search and NLP. Write naturally with keywords woven throughout — but don't keyword-stuff. Google's spam filters are aggressive. Reviews: Fully indexed. User reviews containing relevant keywords create additional entry points your title can't. Custom Store Listings (CSLs): Google's equivalent of Apple's Custom Product Pages. Different listings for different acquisition sources or countries. The mental model swap when going from iOS to Google Play: Apple wants you to compress keywords into three discrete fields; Google wants you to weave keywords through one long readable description. The first approach is structured; the second is contextual. Same goal, different mechanics. For the cross-platform launch process including both stores' submission flows, see our App Store Connect setup guide and Google Play Console setup guide. Visual ASO: the 7-second decision window Once a user lands on your product page, they make a decision in 5–10 seconds. The visuals determine which way they go: App icon (1024×1024): First impression. Recognizable at tiny sizes. Bold colors, simple shapes, distinct silhouette. Test at actual display size — if it looks like a smudge, simplify. First screenshot: Carries 80% of the conversion. Lead with a benefit headline, not a UI dump. Social proof elements (media logos, user counts) lift conversion up to 90%. Screenshots 2–3: Reinforce the primary benefit, show the differentiator. Together with screenshot 1, these three are above the fold in search. Preview video (optional): Boosts conversion when high quality. Hurts conversion when low quality. If you can't produce something polished, skip it entirely. Feature graphic (Google Play, 1024×500): Required for Play Store. No iOS equivalent. Banner-style image displayed prominently on your store page. The key insight: visuals are now ranking signals, not just conversion levers. Conversion rate factors into search ranking, screenshot text feeds OCR indexing, and visual quality compounds across both axes. Indie developers who treat visuals as "design polish I'll do later" cede the strongest 2026 ASO lever to better-organized competitors. For the comprehensive visual checklist covering icon, screenshots, feature graphic, and preview video across both stores, see our visual assets checklist. Ratings: the multiplier on everything else Star ratings are the single highest-leverage ASO input most indies leave to chance. The data is brutal: 4.5+ stars install at 1.7–3x the rate of sub-4.0 apps. 4.5 stars convert nearly 2x of 4.0 stars. Below 3.5 stars, apps lose visibility on 3x more competitive keywords. Featured placement on both stores is gated almost entirely by rating. The path to 4.5+ isn't tricks. It's disciplined prompting (at milestones, never at frustration points), strict segmentation (never after crashes or paywalls), sentiment gating (route unhappy users to private feedback before public reviews), and active response to every 1-3 star review. Apps following this playbook lift from 3.7–4.0 to 4.4–4.7 within 90 days. For the full rating optimization playbook including prompt timing, sentiment gating, and the 70% review revision opportunity, see our rating optimization guide. For early-stage apps with zero reviews, see our first 10 reviews guide. The 4-week ASO sprint that consistently works The cadence that lifts indie apps from buried to discoverable in 90 days: Week 1: Research and audit. Build a master list of 50+ candidate keywords. Use Apple's Search Ads suggestions, App Store autocomplete, and competitor analysis. Rate each by search volume, relevance, and competition. Select your top 20 to target. Week 2: Refresh metadata. Update your title, subtitle, keyword field (iOS) or short/long description (Google Play). Submit the new build. iOS metadata changes require a new release; Google Play allows metadata-only updates. Week 3: Refresh visuals. Redesign screenshots with keyword-aware captions (for iOS OCR indexing). Update icon if it's old or unclear. Test at actual display sizes. Week 4: Reviews and analytics. Audit your last 50 reviews for issue patterns. Fix the top 2. Respond to every 1-3 star review with specific acknowledgment. Set up rating prompt segmentation if you haven't. Weeks 5–12: Iterate. Monitor ranking changes weekly. Most ranking shifts become visible within 7–14 days of metadata updates. Meaningful organic traffic growth takes 60–90 days of consistent optimization. The sprint compounds: better metadata → better impressions → better conversion (visuals + ratings) → better ranking → more impressions. Each input reinforces the others. Custom Product Pages and Custo [truncated for AI cost control]