Custom Product Pages for Indie Developers: How to Use Apple's Free Conversion Tool After the 2025 Update

Custom Product Pages have been available since December 2021. For most of their existence, they required running Apple Search Ads or sharing direct URLs to be useful. In July 2025, Apple changed this by letting CPPs appear in organic search results. This makes them relevant for every developer, including those who spend nothing on ads.

Here is what CPPs are, what changed, and how to use them with limited time and resources.

What are Custom Product Pages

Custom Product Pages let you create up to 70 alternative versions of your App Store product page. Each version can have different screenshots, preview videos, and promotional text.

What you can customize per CPP:

• Screenshots (up to 10)
• App preview videos
• Promotional text
• Keywords (since July 2025)
• Deep links to specific in-app content (iOS 18+)

What stays the same across all CPPs: app name, icon, subtitle, and long description. These are global elements tied to your default product page. You cannot vary them.

Each CPP gets its own unique URL and can be localized independently per market.

What changed at WWDC 2025

The timeline matters for understanding why CPPs are now worth attention:

Before July 2025, a CPP only appeared when you sent someone a direct link or ran a paid ad pointing to it. Users browsing or searching the App Store organically would never see your CPPs.

Now, you can assign keywords to each CPP, and when a user searches for that keyword, Apple may show your CPP instead of your default product page. This happens in organic search results, not just ads.

How keyword-based CPPs actually work

This is where precision matters. There are several important constraints that are easy to miss.

Keywords come from your keyword field only. You can assign keywords to a CPP, but only keywords that already exist in the keyword field of your latest approved app version. Title and subtitle keywords are not eligible for CPP assignment.

You select from Apple's suggestions. You cannot type arbitrary keywords. Apple suggests keywords based on your existing keyword field for each localization, and you choose from those suggestions.

Each keyword must map to exactly one CPP. You cannot assign the same keyword to multiple CPPs. This forces strategic allocation.

CPPs do not expand your keyword index. This is the most critical point. Assigning a keyword to a CPP does not help you rank for new terms. It only changes which product page version is displayed when your app already ranks for that term.

Apple Search Ads take priority. If the same keyword is targeted by both a paid ad and a CPP, the ad version wins.

What Apple has not disclosed

Apple has not documented how it decides whether to show a CPP versus the default page for a given search. The community hypothesis is that Apple may run initial testing between the CPP and the default page, then favor whichever converts better. This is speculation, not confirmed.

It is also unknown whether CPP keywords generate long-tail keyword combinations the way main listing keywords do, or whether cross-locale indexing applies to CPP keyword assignments.

Setting up a CPP: step by step

1. In App Store Connect, go to your app and click Custom Product Pages
2. Click the "+" button. You can start from your default page (recommended to save time)
3. Give it a descriptive internal name (users do not see this)
4. Upload screenshots and preview videos tailored to the keyword theme
5. Write promotional text relevant to the keyword
6. In the Keywords section, select from Apple's suggestions
7. Localize per market as needed
8. Submit for review (independent of app updates, typically 24-48 hours)
9. After approval, toggle visibility on

Key limits

• 70 CPPs maximum per app
• Each CPP is reviewed independently of app updates
• Analytics become available after 5 first-time downloads per CPP
• Deep links require iOS 18+
• iPhone and iPad only (no Mac App Store)

CPPs are not A/B tests

This is a common confusion worth addressing directly.

They are complementary. Use PPO to find the best version of your default page. Use CPPs to create targeted variants for specific keywords or campaigns. Do not expect CPPs to give you statistically valid A/B test results, because each CPP serves a different audience with different intent.

Strategic use cases for indie developers

Before keyword-based CPPs, this feature was primarily for companies running paid ads at scale. Now that CPPs appear in organic search, every developer can benefit for free.

Feature-specific pages

If your app does multiple things, create a CPP for each major feature. A personal finance app could have:

• Default page: general overview of the app
• CPP 1: assigned to "budget tracker" keyword, screenshots showing the budgeting interface
• CPP 2: assigned to "expense report" keyword, screenshots showing expense categorization
• CPP 3: assigned to "savings goals" keyword, screenshots showing the savings feature

When someone searches "budget tracker," they see screenshots specifically about budgeting. When they search "savings goals," they see the savings feature first. Same app, different first impression tailored to intent.

Problem-solution alignment

Match the user's search intent to screenshots that directly address their problem. If someone searches "sleep tracker," show your sleep tracking feature first, not your general wellness dashboard. The first 2-3 screenshots drive 50-60% of download decisions.

Seasonal content

Create CPPs for seasonal peaks. A recipe app could have holiday-themed screenshots during December, then a "meal prep" CPP for January health resolutions.

Competitive positioning

Some apps create CPPs targeting competitor keywords with comparative messaging. Opera created CPPs for users searching "Microsoft Edge" and "Mozilla Firefox." An indie developer could position their app as a simpler or more affordable alternative.

The indie advantage: start small

You do not need to fill all 70 slots. Indie developers actually have an advantage here: agility. While large companies need approval workflows across marketing, design, and legal teams, a solo developer can:

1. Identify 3-5 most important keywords from the keyword field
2. Group them by user intent
3. Create one CPP per intent group with matching screenshots
4. Monitor conversion in App Store Connect
5. Iterate based on data

3-5 well-crafted CPPs will outperform 30 mediocre ones.

What the data shows

Apple's official case studies

• CBS Sports: highlighted seasonal sports content, saw a +20% conversion rate
• State of Survival: aligned RPG features with marketing creative, saw +33% conversion rate and -14% cost per install

Industry benchmarks

From AppTweak's ASO Benchmark Report:

• Apps using CPPs saw a +5.9% conversion rate lift on average
• Games saw +3.5%
• Generic keyword campaigns with CPPs: up to +8.6% conversion rate lift

From MobileAction's 2025 Apple Ads Benchmark Report:

• Conversion rates improved by 32% (from 42.13% to 55.87%)
• Cost per acquisition decreased from $4.83 to $4.58
• Taps decreased while installs increased, indicating higher-quality traffic

SoundCloud reported a +58% conversion rate boost and -39% cost per install.

Apple's own data shows CPPs average around 4.1% conversion versus 1.6% for default pages. That is roughly a 2.5 percentage point improvement.

Important context: most of this data comes from Apple Search Ads campaigns, not organic search. The organic search impact of keyword-based CPPs is too new (July 2025) for comprehensive benchmark data. However, the conversion logic is the same: showing users screenshots that match their intent converts better than showing a generic page.

The adoption gap

According to a 2024 study, 69% of the top 1,000 apps and 74% of the top 1,000 games in the U.S. App Store were not using CPPs in their Apple Ads campaigns. Most apps still do not use CPPs at all. This is your opportunity as an indie developer: low competition for a proven conversion tool.

How CPPs fit into your ASO strategy

Since 2025, Apple's ASO landscape has three interconnected systems:

Traditional metadata (title, subtitle, keywords) determines what you rank for. This is still the foundation.

Screenshot text (since June 2025) reinforces your keyword signals. Apple uses AI to read caption text and factor it into their discovery system.

Keyword-based CPPs (since July 2025) optimize conversion for specific keywords. They do not help you rank, but they help you convert once you do rank.

The practical workflow:

1. Keyword research: identify your most valuable keywords
2. Metadata optimization: place highest-priority keywords in title and subtitle, remaining in keyword field
3. Screenshot design: include keyword-rich captions that align with your metadata
4. CPP creation: for keywords where a different visual narrative would improve conversion, create dedicated CPPs
5. Monitor: track conversion rates per CPP versus default page in App Store Connect

8 common mistakes to avoid

1. Creating too many CPPs. Do not try to fill all 70 slots. Each needs unique, high-quality screenshots. Start with 3-5.

2. Not matching intent to visuals. The entire point is that the first screenshot addresses the user's specific search intent. If someone searches "budget tracker" and your CPP shows social features, you have missed the point.

3. Expecting CPPs to improve rankings. CPPs do not help you rank for new keywords. They only change which page appears for keywords you already rank for.

4. Confusing CPPs with A/B tests. CPPs serve different audiences with different intent. They do not give you statistically valid comparisons. Use Product Page Optimization for A/B testing.

5. Duplicating keywords across CPPs. Each keyword must map to exactly one CPP. Keep keyword sets unique per page.

6. Ignoring CPP analytics. App Store Connect provides per-page impressions, downloads, conversion rates, and retention. Check these. Metrics appear after 5 first-time downloads.

7. Forgetting localization. Each CPP should be localized per market, not just translated. Cultural context matters in screenshot design.

8. Neglecting the first screenshot. 50-60% of users decide based on the first 2-3 screenshots. The first screenshot of your CPP must include a clear value proposition relevant to the assigned keyword.

What about Google Play?

Google Play does not have an equivalent to keyword-based Custom Product Pages. Google does offer Custom Store Listings, which let you create different page versions per country, pre-registration status, or Google Ads campaign. But there is no mechanism to associate a Custom Store Listing with specific organic search keywords the way Apple now allows.

For Google Play, your conversion optimization strategy relies on your default listing plus Custom Store Listings for ads and per-country customization.

Summary

Custom Product Pages are no longer just for companies running paid ad campaigns. The July 2025 keyword-based update makes them a free organic conversion tool that any developer can use.

The key points: CPPs do not help you rank for new keywords, they improve conversion for keywords you already rank for. Start with 3-5 well-targeted CPPs based on your most important keyword themes. Match the visual narrative to the user's search intent. Monitor per-page analytics and iterate.

Most apps still do not use CPPs effectively. 69% of top apps do not use them at all. This adoption gap is your opportunity. The data consistently shows conversion improvements of 5-33%, and the effort to create a few targeted CPPs is modest relative to the potential return.

Keep reading

• Screenshot Caption Keywords — Apple now reads screenshot text for ranking. Your CPP screenshots carry keyword signals too.
• App Store Localization Strategy — Each CPP should be localized per market. This guide covers how.
• In-App Events and Ranking — Another WWDC 2025 search lever. Combine events with CPPs for maximum visibility.
• How to A/B Test App Store Screenshots — Use PPO for testing, CPPs for targeting. Different tools, complementary strategies.
• App Store Screenshot Best Practices — Each CPP needs its own screenshots. Start with the fundamentals.

StoreLit tools

• Screenshot Studio — Create CPP-specific screenshot sets with different messaging per keyword theme
• Keyword Packer — Optimize your keyword field, the source of all CPP keyword assignments
• ASO Audit — Identify which keywords to target with dedicated CPPs