Custom Product Pages in 2026: The Complete Indie-Dev Guide to 70 Pages, Organic Keywords, and CPP Analytics

TL;DR: Apple doubled the iOS Custom Product Page limit from 35 to 70 on October 29, 2025, and on July 30, 2025 made CPPs organically discoverable by letting developers assign keywords to specific pages. A CPP changes screenshots, app previews, promotional text, and now keywords — not title, subtitle, icon, or description. Apple reports a 156% conversion-rate lift when users are referred to a CPP instead of the default page. This guide covers setup, analytics, use cases, and how to generate constraint-compliant CPP metadata.

Last updated: April 17, 2026

Custom Product Pages are one of the most powerful and most underused features in the App Store. Launched with iOS 15 in December 2021, they let you create up to 70 alternate versions of your App Store listing — each with different screenshots, app previews, promotional text, and (since July 2025) organic keyword assignments.

For indie developers running Apple Search Ads campaigns, testing audience segments, or targeting multiple keyword themes, CPPs are the closest thing the App Store offers to landing pages. Yet most small teams either ignore them or stop at one or two. If you need a refresher on ASO fundamentals, start there.

This guide covers everything that changed in 2025, the eight canonical use cases, a step-by-step setup walkthrough, CVR benchmark data from five sources, and how to generate CPP metadata that passes Apple's constraints.

What is a Custom Product Page on the App Store?

A Custom Product Page (CPP) is a persistent, audience-specific version of your App Store listing, reachable by a unique ppid URL. Each CPP can display different screenshots (up to 10), app previews (up to 3), promotional text (170 characters), and — since July 30, 2025 — different keyword assignments from your existing keyword field.

CPPs are distinct from Product Page Optimization (PPO), which is Apple's built-in A/B testing tool. PPO runs up to 3 treatments against your default page for a maximum of 90 days, with the goal of picking a winner to apply site-wide. A CPP is permanent — it exists as a standalone page you can link to from paid campaigns, organic search, or deep links.

Apple's documentation at developer.apple.com covers the full specification. CPPs require iOS 15 or later, and deep links require iOS 18+.

How many custom product pages can an iOS app have?

You can publish up to 70 custom product pages per app. Apple doubled the previous limit of 35 on October 29, 2025 (Apple Developer; MobileAction). Each page supports up to 10 screenshots, 3 app preview videos, 170 characters of promotional text, and assignable keywords from your existing keyword field (since July 30, 2025).

Each CPP also supports up to three localized versions, which count as a single CPP toward the 70-page limit. This means a single CPP targeting three markets uses one slot, not three.

What changed with Custom Product Pages in 2025?

Three major updates reshaped CPPs in 2025. If you set up CPPs before these changes, your playbook is outdated.

CPPs can now appear in organic App Store search (July 30, 2025)

This is the biggest shift. Previously, CPPs were only reachable through direct links — paid campaigns, QR codes, web referrals. Now, you can assign keywords from your existing keyword field to a specific CPP in App Store Connect. When your app ranks for that keyword, Apple serves the assigned CPP instead of the default product page in organic search results.

Important caveats: this does not expand your keyword index. You still have 100 characters in the keyword field. It only changes which page is shown for a given keyword. Apple's rule is strict: "Each keyword combination is unique to a single product page" (developer.apple.com). If two pages share the same keyword assignment, you create keyword cannibalization — avoid this.

70-page limit (October 29, 2025)

The limit doubled from 35 to 70 pages per app. The practical implication: you can now create one CPP per persona, per campaign, per season — without hitting the ceiling. Most indie developers will never need all 70, but teams running localized Apple Search Ads across multiple countries now have room.

100+ new metrics in App Store Connect (Q4 2025)

Apple added granular analytics for CPPs, including source-type filtering: organic, Apple Ads, referral, app referrer, and web referrer. Metrics include impressions, product page views, conversion rate, first-time downloads, redownloads, in-app purchase proceeds, sessions, and retention.

MobileAction observed that this level of analytics "almost eliminates the need for an MMP for indie developers and SMBs" — you can now attribute CPP performance by source directly in App Store Connect, without paying for a third-party mobile measurement partner.

What can I customize on a Custom Product Page?

Not everything on a CPP is customizable. Here is the exact breakdown:

Element	Customizable per CPP?	Details
Screenshots	Yes	Up to 10 per page
App Previews (video)	Yes	Up to 3 per page
Promotional Text	Yes	170 characters, no App Review required
Keyword Assignment	Yes (since July 2025)	From existing keyword field only
Deep Link	Yes (iOS 18+)	Opens specific in-app content
App Name	No	Same across all pages
Subtitle	No	Same across all pages
Icon	No	Same across all pages
Description	No	Same across all pages
Price / Rating / Category	No	Same across all pages

The key takeaway: title, subtitle, icon, and description — the fields that define your app's identity — cannot vary per CPP. Screenshots, videos, and promotional text are the primary levers. Keyword assignment is new and powerful, but it works within your existing 100-character keyword field, not in addition to it.

What is the difference between a Custom Product Page and Product Page Optimization?

Product Page Optimization (PPO) is Apple's native A/B testing tool. You create up to 3 treatment variations of your default product page and run a test for up to 90 days. Apple splits traffic and reports conversion rates. When the test ends, you pick a winner and apply it to your default page.

A Custom Product Page is permanent and audience-specific. It lives at its own ppid URL, is usable across paid campaigns and organic search, and does not replace your default page. The recommended workflow: use PPO to find a winning creative variant, then deploy it as a CPP targeted at the specific audience that responded best.

What are the canonical use cases for Custom Product Pages?

Eight use cases cover the majority of CPP deployments. Each one maps to a specific audience, channel, or intent:

1. Paid UA landing pages

Match your ad creative to the App Store experience. If your TikTok ad shows a "meal planning" workflow, the CPP should feature meal planning screenshots — not your generic hero image. SoundCloud partnered with AppTweak and saw a 39% reduction in cost per install and a 58% increase in conversions by aligning CPP creative with ad campaigns.

2. Apple Ads ad variations

Apple Search Ads lets you assign a CPP as an "ad variation" for Search Results ads. SplitMetrics reported a 13.4% increase in tap-through rate when using CPP-based ad variations versus the default page. For Today Tab ads, a CPP is required — you cannot use the default page.

3. Feature highlighting

Create a CPP for each major feature of your app. A fitness app might have one CPP highlighting its workout library, another for meal tracking, and a third for sleep analysis. Each page shows screenshots specific to that feature.

4. Seasonal and event campaigns

Holiday themes, sports events, back-to-school promotions — seasonal CPPs let you match App Store creative to current user intent without permanently changing your default listing. Create the CPP before the event, link it from your campaigns, and retire it after.

5. Audience segmentation

FunPlus created audience-targeted CPPs for their RPG game and saw a 33% increase in conversion rate and a 14% decrease in cost per install (Apple Tech Talks). Khan Academy uses separate CPPs for parents, teachers, and students — same app, three different value propositions.

6. Competitor-intercept pages

Build a CPP that addresses common complaints from competitor reviews. If users complain that a rival app lacks offline mode and yours supports it, create a CPP highlighting offline capability and assign keywords related to that competitor's category.

7. Organic-search keyword matching (new in 2025)

Assign specific keywords from your keyword field to a CPP so that users searching for those terms see a page tailored to their intent. A keyword research strategy that includes keyword-to-CPP mapping is now a competitive advantage.

8. Deep-linked re-engagement (iOS 18+)

With iOS 18, CPPs can include a deep link that opens specific in-app content when a user taps "Open." This enables re-engagement campaigns where lapsed users see a CPP promoting new features and are taken directly to those features in the app.

How do I set up a Custom Product Page in App Store Connect?

Setting up a CPP requires these 8 steps:

1. Verify your role. You need Account Holder, Admin, App Manager, or Marketing permissions in App Store Connect.
2. Navigate to your app in App Store Connect → App Store → Custom Product Pages → Create Custom Product Page.
3. Set a reference name. This is internal only — used in analytics to identify the page. Use a descriptive name like "Q2-2026-Fitness-Keywords" or "TikTok-Meal-Planning."
4. Start from scratch or copy. You can start with a blank page or copy your default product page as a starting point.
5. Upload localized assets. Add screenshots, app preview videos, and promotional text (170 chars) for each localization you want to support. Each CPP supports up to 3 localizations.
6. Assign keywords (optional). Since July 2025, you can assign keywords from your existing keyword field to this specific CPP. Remember Apple's rule: each keyword combination must be unique to a single page.
7. Set a deep link (optional, iOS 18+). If your app supports Universal Links, you can configure a deep link that opens specific in-app content.
8. Submit for App Review. Each CPP is reviewed independently of the app binary. Typical review time: 24–48 hours. Editing an approved CPP creates a new draft without changing its ppid URL, so campaign links survive updates.

This workflow is straightforward for 3–5 CPPs. If you plan to create more, the bottleneck is screenshot production — not the App Store Connect flow.

How do I generate CPP metadata that passes Apple's constraints?

Each CPP needs promotional text (170 characters) and a keyword assignment strategy that avoids overlap with other CPPs. Doing this manually for 10+ pages is tedious and error-prone — especially when you need to ensure each keyword combination is unique across all pages.

RespectASO's AI Niche Researcher generates constraint-compliant App Store metadata from a single seed keyword. It produces title, subtitle, keyword field, and description variants, then self-corrects for up to 7 rounds until all of Apple's metadata constraints pass — including character limits, duplicate word detection, and formatting rules.

For CPP workflows, the same approach extends to promotional text and keyword sub-assignments. Feed in your seed keyword and target audience, and the AI generates variants with constraint-compliance checks built in. The ASO Score Simulator can then validate that your keyword assignments don't overlap with other CPPs — catching the "unique keyword combination per page" rule before submission.

Everything runs locally on your Mac with your own API key (OpenAI, Anthropic, or Google Gemini). No data leaves your device. Download RespectASO free to start generating metadata.

How do I track CPP performance?

In App Store Connect, navigate to App Analytics → Acquisition. CPP data requires at least 5 first-time downloads before metrics become visible — Apple hides small-sample data for privacy.

Available dimensions:

• Source type: Organic, Apple Ads, Referral, App Referrer, Web Referrer
• Metrics: Impressions, product page views, conversion rate, first-time downloads, redownloads, in-app purchases, proceeds, sessions, retention

For deeper attribution, major MMPs support CPP tracking via the ppid parameter: Adjust uses redirect_ios, AppsFlyer uses af_ios_store_cpp, and Kochava, Branch, and Singular all support PPID-based routing.

But as MobileAction noted, the Q4 2025 analytics update makes native App Store Connect sufficient for most indie developers. You no longer need an MMP just to know which CPP drove which downloads.

How much CVR lift can a Custom Product Page actually deliver?

Conversion rate lift varies significantly by app category, creative quality, and audience targeting. Here are the benchmarks from five sources:

Source	Metric	Result
Apple	Average CVR lift	156% (1.6% default → ~4.1% with CPP)
MobileAction (2025)	Apple Ads CPP CVR	42.13% (2023) → 55.87% (2024), +32% YoY
AppTweak (2024)	CVR lift (apps / games)	6.6% apps, 8% games
FunPlus (Apple Tech Talks)	RPG-targeted CPP	+33% CVR, –14% CPI
SoundCloud × AppTweak	Campaign-aligned CPP	–39% CPI, +58% conversions

Baidu reported a 10% install rate increase using CPPs, and ODXClub saw a 56.3% CVR lift on a UGC-creator-imagery CPP (via RPLG). These are vendor-reported case studies with varying methodologies — treat them as directionally reliable, not as guaranteed benchmarks.

The pattern across all studies is consistent: when the App Store page matches what the user expected (from an ad, a search, or a referral), conversion improves. The lift is largest when the default page is generic and the CPP is highly targeted.

What is the indie-friendly CPP stack in 2026?

Enterprise tools exist for CPP management — AppTweak's CPP Explorer (from $79/month), SplitMetrics Acquire (enterprise pricing), and MobileAction's CPP A/B testing. For indie developers, those budgets rarely make sense.

The indie stack:

• Metadata generation: RespectASO's AI Niche Researcher for constraint-compliant promotional text and keyword assignments, using your own API key at pennies per task.
• Constraint validation: The ASO Score Simulator for pre-submission checks, ensuring keyword combinations are unique per page.
• Keyword research: The Country Opportunity Finder for identifying which markets justify a localized CPP.
• Analytics: App Store Connect's native CPP metrics (free).
• Screenshot production: Figma (free tier) or RocketSim for device frames.

For a full breakdown of ASO tool costs across the industry, see The True Cost of ASO Tools in 2026. You can also generate CPP metadata from inside Claude Desktop or Cursor using RespectASO's MCP integration.

When should I create a new CPP versus updating an existing one?

Use this decision framework:

• New CPP — when you are targeting a new audience, launching a new acquisition channel, or running a seasonal campaign with a clear end date.
• Update existing CPP — when you are iterating on creative for the same audience or campaign. Editing an approved CPP creates a new draft without changing the ppid URL, so campaign links survive.
• Retire a CPP — when a seasonal campaign ends. Remove the campaign links, but the CPP remains available if you want to reactivate it later.

Start with 3–5 high-intent CPPs before scaling. Each CPP requires screenshot production, which is the real bottleneck. Do not spread design capacity across 70 pages until you have proven which audience segments respond best.

The 70-CPP playbook for indie teams

Custom Product Pages are no longer optional for serious ASO. With 70 pages available, organic keyword assignment, and granular App Store Connect analytics, CPPs have become a core ranking and conversion lever — not just a paid-campaign nice-to-have.

The playbook: treat each CPP as a focused experiment matching one audience, one channel, or one keyword theme. Generate constraint-compliant metadata with RespectASO's AI Niche Researcher, validate keyword assignments with the ASO Score Simulator, and measure everything through App Store Connect's native analytics.

Start small. Pick your three highest-value audiences or keyword themes, create a CPP for each, and track the conversion lift for 30 days before expanding. Download RespectASO free and generate your first CPP metadata today.

Frequently asked questions

How many custom product pages can an iOS app have?

You can publish up to 70 custom product pages per app. Apple doubled the previous limit of 35 on October 29, 2025. Each page supports up to 10 screenshots, 3 app previews, 170 characters of promotional text, and assignable keywords from the app's existing keyword field. CPPs require iOS 15 or later.

Do custom product pages appear in organic App Store search?

Yes, since July 30, 2025. Developers can assign keywords from the app's keyword field to specific custom product pages in App Store Connect. When the app ranks for an assigned keyword, Apple serves the matching CPP instead of the default product page in organic search results. The feature launched in US English first.

What is the difference between a Custom Product Page and Product Page Optimization?

A Custom Product Page is a persistent audience-specific version of your App Store listing, reachable by a unique ppid URL and usable across paid campaigns and organic search. Product Page Optimization is Apple's built-in A/B testing tool — up to 3 treatments vs your default page, capped at 90 days, designed to pick a winner to apply site-wide.

Do custom product pages require App Review?

Yes. Each CPP must be submitted to App Review independently of the app binary, with approval typically taking 24–48 hours. Editing an approved CPP creates a new draft without changing the underlying ppid URL, so campaign links survive updates. Deep links in CPPs (iOS 18+) also require approval.

Can I localize a custom product page?

Yes. Each CPP supports up to three localized versions, which count as a single CPP toward your 70-page limit. Localized assets — screenshots, app previews, promotional text — are shown to users in their respective locales. This is the recommended pattern for testing market-specific creative without consuming additional CPP slots. For localization strategy, see our App Store localization guide.

How much does a custom product page lift conversion rate?

Apple reports a 156% CVR lift on average when users are referred to a CPP (2.5 percentage points over a 1.6% default baseline). MobileAction's 2025 Apple Ads Benchmark Report shows CPP conversion rates rose from 42.13% in 2023 to 55.87% in 2024, a 32% relative lift. Individual case studies range from +10% (Baidu) to +58% (SoundCloud). Results depend on creative quality and audience targeting.