highapple

Custom Product Page Expansion

Also known as: CPP Limit Increase, Custom Pages Expansion 2026, 35 to 70 Pages, Product Page Variants

Keywords & Metadata

Definition

Apple doubled the maximum number of Custom Product Pages (CPP) developers can create from 35 to 70 active pages effective April 2026. Each custom product page can have its own custom title, subtitle, preview images, app icon, and crucially, manually assigned keywords. When users search for a custom product page's keywords, the custom page appears in search results instead of the default product page. This expansion enables developers to target 70 different keyword sets, user segments, and use cases with distinct messaging and creative—effectively running parallel A/B tests and multi-variant ASO strategies within a single app listing. Custom product pages with manually assigned keywords are now a primary ASO mechanism for targeting long-tail, intent-based queries.

How It Works

Apple App Store

Custom Product Page Mechanics:

  1. Page Creation — Developer creates custom product page from App Store Connect:

- Custom title and subtitle (up to original character limits)

- Custom app icon

- Custom preview screenshots/videos

- Custom description and metadata

- Maximum 70 active pages

  1. Keyword Assignment — Each custom page assigned:

- Up to 30 custom keywords manually entered

- Keywords can overlap across multiple pages (unlike main keyword field, which has single instance)

- Pages triggered when user searches for assigned keywords

- Default product page still serves as fallback for unassigned searches

  1. Page Selection Logic — When user searches on App Store:

- If search matches custom page's keywords → Show custom page

- If search doesn't match any custom page → Show default product page

- Custom pages rank independently in search results for their keywords

  1. CTR and Conversion Tracking — App Store Connect tracks:

- Impressions per custom page

- Clicks per custom page

- Conversion rate per page

- Keywords triggering each page

Constraints:

  • Each page can have different visual assets but same app binary/functionality
  • Custom pages must comply with App Store Guidelines (no misleading messaging)
  • Keywords must be relevant to app functionality
  • Review required; misleading pages can be rejected or suspended

Formulas & Metrics

Custom Page Optimization Metric:

Custom_Page_Performance = (Page_Installs / Page_Impressions) × 100

Optimal CTR by Page Type:

  • Brand/Direct: 8–15% CTR
  • Problem-Solution: 5–12% CTR
  • Feature-Specific: 4–10% CTR
  • Niche/Long-tail: 2–8% CTR

Multi-page Strategy Benchmarking:

  • 10–20 custom pages: Typical for moderately aggressive ASO
  • 20–40 custom pages: Aggressive, competitive categories
  • 40–70 custom pages: Enterprise-level, 10+ use cases or segments

Keyword Coverage:

Total_Keywords_Covered = Sum(Keywords_per_Page) × Uniqueness_Factor

  • Fully unique keywords across pages: 100% efficiency
  • 30% overlap: 70% keyword coverage efficiency

Best Practices

  1. Segment by Use Case or User Problem — Create custom pages for distinct problems:

- Page 1: "Quick Budget Tracking" (keywords: quick budgeting, fast expense tracking)

- Page 2: "Investment Tracking" (keywords: stock portfolio tracking, investment app)

- Page 3: "Business Expense Management" (keywords: business expense tracker, team budget)

Each page optimized for specific keyword set and messaging.

  1. Create Long-tail Keyword Pages — Target low-competition, high-intent long-tail:

- Main page: "Budget App"

- Custom page: "AI-powered Expense Tracking with Receipt Scanning"

- Custom page: "Family Budget Shared Across Multiple Members"

- Custom page: "Subscription Cancellation Tracker and Reminder"

Long-tail pages face less competition, higher conversion rates.

  1. A/B Test Creative and Messaging — Use multiple pages to test:

- Icon variations

- Title/subtitle messaging (problem-solving vs. feature-focused)

- Preview images (showing specific use cases)

- Color schemes

Track CTR and conversion per page; double down on winners.

  1. Prioritize by Search Volume and CPC — Focus custom pages on:

- High-volume keywords (e.g., "budget app" parent keywords)

- Long-tail, conversational keywords (e.g., "how do I stop overspending")

- High-intent keywords (problem-solving language)

- Emerging keywords (new trend opportunities)

  1. Monitor Keyword Overlap and Conflicts — Review custom page keywords quarterly:

- Identify keywords assigned to multiple pages (may cause inconsistent ranking)

- Reassign overlapping keywords to highest-performing page

- Remove redundant pages that don't differentiate

  1. Align Page Messaging with Keyword Relevance — For each custom page:

- Title/subtitle must clearly address keyword intent

- Preview images should show keyword-relevant use case

- Description elaborates on keyword promise

  1. Leverage Custom Pages for Regional Variants — Create region-specific pages:

- US page: Feature "Dollar" currency support

- EU page: Feature "GDPR compliance" and euro support

- India page: Feature "INR support" and local payment methods

Different keywords and messaging per region.

Examples

Example 1: Photo Editor App with 35→70 Page Strategy

Old strategy (35 pages max):

  • Page 1: "Photo Editor" (general keywords)
  • Page 2: "Background Removal" (background removal keywords)
  • Page 3: "Photo Collage" (collage keywords)
  • Pages 4–35: Other features

New strategy (70 pages):

  • Pages 1–10: Feature-specific (remove bg, collage, filters, effects, retouch, blur, etc.)
  • Pages 11–30: Problem-solving (fix blurry photos, enhance dim photos, enlarge photos, etc.)
  • Pages 31–50: Use-case specific (profile pictures, Instagram content, headshots, product photos)
  • Pages 51–70: Long-tail conversational (how to remove wrinkles from photos, AI photo enhancement, etc.)

Result: 70 targeted keyword sets reach 7x more search queries vs. 10-page baseline.

Example 2: Conversion Rate Comparison

  • Default page: "Budget App" — 3% conversion rate, 50K impressions = 1,500 installs
  • Custom page 1: "AI Budget Coach" — 8% conversion rate, 10K impressions = 800 installs
  • Custom page 2: "Family Budget Sharing" — 6% conversion rate, 8K impressions = 480 installs
  • Custom page 3: "Investment Tracker" — 5% conversion rate, 5K impressions = 250 installs

Total: 68K impressions, 3,030 installs (4.5% blended), vs. 1,500 on default page alone = 2x install lift

Example 3: Keyword Assignment per Page

Budget App custom pages (sample):

PageTitleKeywordsCTRConversion
DefaultBudget App(system keywords)3%3%
Custom 1AI Budget Coachai budget, expense tracking ai, smart budgeting8%8%
Custom 2Family Budget Sharedfamily budget app, shared budgeting app, group expense tracker6%6%
Custom 3Investment Portfolioinvestment tracker, stock portfolio app, dividend tracker5%5%

Dependencies

Influences

Depends On

Platform Comparison

AspectApple App StoreGoogle Play Store
**Custom Pages**Custom Product Pages up to 70 (April 2026)Custom store listing (limited; not equivalent to CPP)
**Keyword Assignment**Manual keywords per custom pageDefault metadata only
**Independent Ranking**Each CPP ranks independently for its keywordsN/A
**Use Case**Multi-variant keyword targeting, A/B testingN/A
**Strategic Advantage**Can rank for 70+ keyword sets simultaneouslySingle listing visibility

Related Terms

Product Page Optimization (PPO), Keyword Research, Keyword Ranking, Conversion Rate, Metadata Optimization, Visual Assets & Creative, A-B Testing|A/B Testing, App Store Optimization (ASO), Search Visibility

Sources & Further Reading

📰 Recent News Impact (20)

Apr 11, 2026
How to Build an App Studio by Buying Apps [The Wall Street Playbook]App Masters YouTube
Apr 3, 2026
Q&A: How Plane Finder set itself up for the long haulApple Developer News
Apr 1, 2026
Get your Wear OS apps ready for the 64-bit requirementAndroid Developers Blog
Mar 26, 2026
Update on regulated medical device apps in the European Economic Area, United Kingdom, and United StatesApple Developer News
Mar 18, 2026
Apple guidelines explained: remote testing your iOS app (without getting your account banned)RevenueCat Blog
Mar 6, 2026
Exit Offers in RevenueCat PaywallsRevenueCat Blog
Feb 24, 2026
Age requirements for apps distributed in Brazil, Australia, Singapore, Utah, and LouisianaApple Developer News
Feb 24, 2026
Cross-platform subscription state: sharing entitlements between Android and iOSRevenueCat Blog
Feb 10, 2026
Running custom built paywalls alongside RevenueCat PaywallsRevenueCat Blog
Feb 9, 2026
RevenueCat React Native SDK adds React Native Web supportRevenueCat Blog
Feb 6, 2026
Updated App Review Guidelines now availableApple Developer News
Dec 29, 2025
ASO News Digest for December 2025Asodesk Blog (RU)
Dec 24, 2025
Update on age requirements for apps distributed in TexasApple Developer News
Dec 8, 2025
New Requirements for Social Media Apps in AustraliaApple Developer News
Nov 26, 2025
Bolt Accelerates Market Growth Using Keyword Expansion Strategies in SplitMetrics AcquireSplitMetrics Blog
Nov 25, 2025
October product updates: Paywall videos, smarter support, and a big step onto the webRevenueCat Blog
Nov 14, 2025
Flex + RevenueCat: Accept HSA/FSA payments for in-app subscriptionsRevenueCat Blog
Nov 4, 2025
Next steps for apps distributed in TexasApple Developer News
Oct 18, 2025
App Growth Week: The largest digital AI event for app marketersSplitMetrics Blog
Oct 8, 2025
New requirements for apps available in TexasApple Developer News

Referenced by (1)

#aso#glossary#apple-app-store#product-pages#keywords#2026
Custom Product Page Expansion — ASO Wiki | ASOtext