Custom Product Pages have quietly become the most powerful ASO lever in the App Store. What started in 2021 as a way to show different screenshots in paid ad campaigns has evolved into something far more significant: a tool that lets you serve tailored store listings in organic search results based on what a user actually searched for.

If you've been treating your App Store listing as a single page that has to speak to everyone, you're leaving downloads on the table. In 2026, the apps winning the install are the ones matching their message to the user's intent — and Custom Product Pages are how they do it.

This guide covers everything you need to know about CPPs: what they are, how the 2025 organic search update changed the game, how to set them up step by step, and how to build a CPP strategy that turns keyword relevance into conversion lifts.

What Are Custom Product Pages?

Custom Product Pages (CPPs) are alternate versions of your App Store product page that you create inside App Store Connect. Each CPP can feature its own set of screenshots, app preview videos, and promotional text — all independent of your default listing.

Think of your default product page as a general-purpose storefront. It has to communicate your app's value to every possible user, which means it inevitably speaks to no one perfectly. Custom Product Pages solve this by letting you build focused versions of your listing, each designed for a specific audience, use case, or search intent.

A meditation app, for example, might create one CPP with screenshots showing sleep-focused features for users searching "sleep sounds app" and another with guided meditation screenshots for users searching "daily meditation." The app is the same, but the first impression changes to match what the user is actually looking for.

Each CPP gets a unique URL you can share through any channel — social media, email campaigns, websites, QR codes — and Apple now allows up to 70 Custom Product Pages per app, doubled from 35 in October 2025.

What You Can Customize on a CPP

Screenshots — completely different screenshot sets for each CPP
App preview videos — different video content per page
Promotional text — the 170-character text above the description

What Stays the Same Across All Pages

App name and subtitle
App icon
Description
Ratings and reviews
In-app purchases

This distinction matters. Your CPP strategy is primarily a visual strategy. The screenshots and video are where you make or break the conversion, so your CPP work will focus heavily on creating screenshot sets that match specific user intents. Tools like the AppDrift Screenshot Generator make it practical to produce multiple high-quality screenshot variants without hiring a designer for each set.

The 2025 Game-Changer: CPPs in Organic Search

Before mid-2025, Custom Product Pages were exclusively a paid acquisition tool. You could link a CPP to an Apple Search Ads campaign so that users who clicked your ad would land on a tailored page. Organic search always showed your default product page, no matter what the user searched.

That changed in July 2025 when Apple introduced keyword linking for CPPs. This is the single biggest update to CPPs since their launch, and it fundamentally changes how ASO works.

How Keyword Linking Works

Here's the mechanism: in App Store Connect, you can now assign keywords from your 100-character keyword field to specific Custom Product Pages. When a user searches for one of those assigned keywords, the App Store can show your CPP in the organic search results instead of your default page.

Let's say you have a photo editing app. Your keyword field includes terms like "collage maker," "photo filters," and "portrait editor." Before keyword linking, all three searches showed your default product page with the same generic screenshots. Now you can:

Create a CPP with collage-focused screenshots and assign the keyword "collage maker" to it
Create another CPP with filter-focused screenshots and assign "photo filters"
Create a third CPP highlighting portrait editing and assign "portrait editor"

Each user sees a product page that directly reflects what they searched for. The result? Higher relevance, higher tap-through rates, and higher conversion rates.

The Rules of Keyword Linking

There are important constraints to understand:

Keywords must come from your keyword field. You can only assign keywords that are already in your 100-character keyword field. You cannot add new keywords through CPPs.
Each keyword can be assigned to only one CPP. You can't assign the same keyword to multiple Custom Product Pages.
Unassigned keywords default to your default page. Any keyword in your keyword field that isn't linked to a CPP will continue showing your default product page.
Geographic availability is limited. As of early 2026, CPP keyword linking for organic search works in the United States and the United Kingdom. Other markets still see CPPs only through paid campaigns or direct links.
Apple decides when to show your CPP. Assigning a keyword to a CPP doesn't guarantee it will always appear. Apple's algorithm determines which page to surface based on relevance and other factors.

This means your keyword strategy and CPP strategy are now deeply intertwined. Every keyword you choose for your 100-character field should be evaluated not just for search volume and relevance, but for whether it warrants a dedicated CPP with tailored screenshots. Use a keyword tracking tool to monitor how your keywords perform across different CPPs and identify optimization opportunities.

Why CPPs Matter More Than Ever for ASO

The introduction of CPPs in organic search didn't just add a new feature — it changed the economics of App Store Optimization. Here's why:

Intent Matching at the Organic Level

Before keyword linking, ASO professionals had one shot at converting every user, regardless of their search query. A fitness app ranking for both "calorie counter" and "home workout" had to choose screenshots that either emphasized calorie tracking or exercise — inevitably losing some conversion on whichever intent wasn't highlighted.

Now you can match intent at the page level. Users searching "calorie counter" see screenshots of your food logging interface. Users searching "home workout" see screenshots of exercise routines. Same app, different first impression, better conversion on both terms.

This is particularly powerful for apps that serve multiple use cases. Think of apps like Notion (project management vs. note-taking vs. team wiki), Spotify (music streaming vs. podcast listening), or banking apps (payments vs. investing vs. budgeting). Each use case deserves its own visual story.

Higher Conversion Rates Without More Traffic

Most ASO strategies focus on getting more impressions — ranking higher, targeting more keywords. CPPs flip the script: they help you convert more of the impressions you already have. If your app ranks for 50 keywords but shows the same generic screenshots for all of them, you're likely converting well on 10-15 highly relevant terms and poorly on the rest.

Creating CPPs for your top-performing but under-converting keywords can lift your overall install rate without any change in ranking or visibility. It's pure conversion optimization.

Competitive Differentiation

Adoption of CPPs remains relatively low. According to recent ASO benchmark data, fewer than a third of top apps use Custom Product Pages at all. Among those that do, most have only a handful of CPPs, primarily for paid campaigns. The opportunity to outperform competitors through organic CPP optimization is wide open.

How to Create Custom Product Pages: Step-by-Step

Setting up CPPs requires both App Store Connect work and strategic planning. Here's the process from start to finish.

Step 1: Audit Your Keywords and Identify Intent Clusters

Before touching App Store Connect, analyze your keyword field and group keywords by user intent. Look for clusters where the same set of screenshots would resonate with users searching those terms.

For example, a language learning app might identify these clusters:

Casual learners: "learn spanish," "language app," "daily lessons"
Travel-focused: "travel phrases," "translation app," "conversation practice"
Test prep: "DELE prep," "language certification," "exam practice"

Each cluster represents a potential CPP. You don't need a CPP for every single keyword — you need one for each distinct intent group where different screenshots would meaningfully improve the user's first impression.

Step 2: Create Screenshot Sets for Each Intent

This is the most time-intensive part, but it's where the conversion lift actually happens. For each CPP, you need a full set of screenshots (up to 10 on iPhone) that tell a coherent visual story aligned with the keyword intent.

The first 1-3 screenshots are critical — they're what users see without scrolling in search results. Make sure your hero screenshots directly reflect the search intent. If the CPP is for "calorie counter," the first screenshot should show the food logging interface, not a generic workout screen.

The AppDrift Screenshot Generator is built for this kind of workflow. You can create professional screenshot sets for every device size (iPhone 6.9", iPad Pro, Android), customize backgrounds and text overlays, and batch export across multiple CPPs without starting from scratch each time.

Step 3: Set Up CPPs in App Store Connect

Open App Store Connect and navigate to your app
Go to the Custom Product Pages section in the sidebar
Click Create Custom Product Page
Enter a reference name (internal only — users won't see this). Use a descriptive name like "CPP - Calorie Counter Intent"
Select your target localization (you can add more localizations later)
Upload your custom screenshots and/or app preview video
Write your promotional text (170 characters). This should reinforce the intent — if the CPP targets "calorie counter," the promotional text should highlight food tracking features
Under the keyword linking section, assign the relevant keywords from your keyword field to this CPP
Submit the CPP for review. Apple typically reviews CPPs within 24-48 hours

Step 4: Localize Your CPPs

Every CPP can be localized for different markets. Since keyword linking is currently live in the US and UK, prioritize English localizations. But if you're running paid campaigns in other markets, localized CPPs for those campaigns can still drive significant conversion improvements.

If you need to localize your app metadata across multiple languages, AppDrift's metadata generation tools can produce ASO-optimized titles, subtitles, and descriptions that maintain keyword relevance across languages. Combine this with localized screenshot sets on your CPPs for maximum impact in each market.

Step 5: Monitor and Iterate

After your CPPs go live, track performance in App Store Analytics. Key metrics to watch:

Impressions — how often each CPP is shown in search results
Conversion rate — the percentage of users who install after viewing the CPP
Tap-through rate — how often users tap your listing in search results (impacted by your first screenshot)

Compare each CPP's conversion rate against your default page. If a CPP is underperforming, the screenshot messaging might not align well with the keyword intent, or the keyword itself might attract users who aren't your target audience.

CPP Limits and Technical Constraints

Understanding the boundaries will save you from wasted effort:

Maximum 70 CPPs per app — increased from 35 in October 2025. This is generous for most apps, but if you're managing a large keyword portfolio across many localizations, you'll need to prioritize.
CPPs require review. Every new CPP and every update to an existing CPP must be submitted for Apple review. Plan for 24-48 hour review times when scheduling launches.
CPPs are independent of app updates. You can create and update CPPs without submitting a new app version. This is a huge advantage — you can iterate on your store presence without waiting for a full app release cycle.
Keyword linking is limited to US and UK. In other markets, CPPs work through paid campaigns (Apple Search Ads) and direct links only.
Each keyword can link to only one CPP. If you have overlapping intent groups, you'll need to decide which CPP gets which keyword.
CPP URLs are unique and persistent. Each CPP gets its own URL that you can use in marketing materials. These URLs survive CPP updates, so your external links won't break.

One Install Motivation Per CPP: The Golden Rule

The single most important principle for effective CPP design is this: each Custom Product Page should communicate one clear reason to install.

This sounds obvious, but it's where most developers go wrong. They create a CPP, include a few different screenshots, and end up with a page that looks like a slightly rearranged version of their default listing. That won't move the needle.

An effective CPP tells a tight, focused story:

Screenshot 1-2: The hero moment. Show the feature or experience that matches the keyword intent. If the user searched "expense tracker," the first thing they should see is the expense tracking interface with a clear value proposition.
Screenshot 3-5: Supporting features that reinforce the primary motivation. For "expense tracker," this might be budget summaries, receipt scanning, and spending categories.
Screenshot 6-10: Social proof, breadth features, or secondary value. Show ratings, integrations, or features that complement the primary motivation without diluting it.

The promotional text should reinforce the same single motivation. Don't try to cram every feature into 170 characters. Pick the one value proposition that matches the keyword and hammer it home.

Building a CPP Strategy for Organic Search

A strong CPP strategy isn't about creating as many pages as possible. It's about identifying the highest-impact keyword-intent pairings and building pages that convert.

Prioritize Keywords by Volume and Conversion Gap

Start with your highest-volume keywords and assess how well your default page converts for each one. Keywords where your ranking is strong but your conversion rate is below average are prime CPP candidates. These are keywords where you're getting visibility but losing users because your default screenshots don't match their intent.

Study Competitor Listings for Intent Cues

Search for your target keywords and look at what competitors show in their first two screenshots. If the top three results for "budget planner" all show budget dashboards in their hero screenshots and your app shows a generic feature overview, you're losing on visual relevance. Your CPP for "budget planner" should lead with budget-specific visuals.

Group Keywords Strategically

Not every keyword needs its own CPP. Group keywords that share the same user intent and would be well-served by the same screenshot set. For a project management app:

CPP 1 (Task Management): "task manager," "to-do list," "task organizer"
CPP 2 (Team Collaboration): "team projects," "group tasks," "collaboration app"
CPP 3 (Calendar/Planning): "project planner," "timeline view," "gantt chart"

Three CPPs covering nine keywords is more sustainable than nine CPPs with marginally different screenshot sets. As you learn what works, you can break groups apart and create more targeted pages. Check your keyword selection strategy to ensure each group is built around terms that genuinely represent distinct user needs.

Align Promotional Text with Keywords

Your promotional text (170 characters) is the one text element you can customize per CPP. Use it to echo the keyword intent and create urgency. Example:

Default page: "The all-in-one fitness app trusted by 2M+ users. Track workouts, meals, and progress."
CPP for "calorie counter": "Track every meal in seconds. Smart calorie counter with barcode scanning, custom recipes, and daily goals."
CPP for "home workout": "700+ home workouts with zero equipment. New routines daily. Get fit on your schedule."

Notice how each version speaks directly to the user's search intent while keeping the app's broader value as background context.

A/B Testing CPPs for Organic Search

While Apple's Product Page Optimization (PPO) doesn't directly test CPPs against each other, you can still run structured experiments to improve CPP performance.

Sequential Testing

The most practical approach is sequential testing: run one version of a CPP for 2-4 weeks, collect performance data, then update the CPP with a new version and compare. This isn't a true A/B test (external factors can influence results between periods), but it's actionable and better than guessing.

For more advanced testing frameworks, read our complete guide to App Store A/B testing which covers both PPO and CPP optimization strategies in depth.

Paid Campaign Testing as a Proxy

A faster way to test CPP variations is through Apple Search Ads. Create two CPPs with different screenshot sets targeting the same keyword, run both as ad variations in a search results campaign, and measure which one has a higher conversion rate. The winner becomes your organic CPP for that keyword.

This approach uses paid traffic to get statistically significant results faster, then applies the winning creative to organic search. It costs money up front but can save weeks of sequential testing time.

Cross-CPP Performance Comparison

Even without formal A/B testing, comparing conversion rates across your CPPs reveals patterns. If your "sleep sounds" CPP converts at 42% and your "guided meditation" CPP converts at 28%, the sleep-focused messaging is clearly resonating more strongly. You might then investigate whether the meditation CPP's screenshots are too generic or whether the keyword itself attracts lower-intent users.

AppDrift's A/B testing features can help you structure these experiments and track conversion data across your CPP variants systematically.

CPP Optimization Best Practices

After working with CPPs across dozens of apps, these practices consistently produce the best results:

1. Lead With the Money Screenshot

Your first screenshot in search results is your ad. It needs to stop the scroll and communicate relevance in under a second. For every CPP, ask: "If a user sees only this one image, will they understand that my app does what they searched for?"

2. Use Consistent Visual Branding Across CPPs

While your screenshots should vary in content, maintain consistent brand elements: color palette, typography style, device framing. Users who see your app across multiple searches should recognize it as the same product. Inconsistent branding creates confusion and erodes trust.

3. Don't Repeat Your Default Page

If your CPP looks identical to your default listing with one screenshot swapped, it's not doing its job. Each CPP should feel purpose-built for its target keyword. Different hero screenshots, different feature emphasis, different promotional text.

4. Optimize for the Search Results View, Not Just the Product Page

Users make their first decision in the search results list, where they see your icon, name, subtitle, and the first 1-3 screenshots. Your CPP screenshots need to be compelling at small sizes in horizontal scroll view, not just when viewed full-screen on the product page.

5. Match Screenshot Text to Keyword Language

If your target keyword is "budget planner," use that exact phrase (or close variants) in your screenshot captions. Mirror the user's language. Don't use corporate-speak like "Financial Management Dashboard" when the user searched for "budget planner."

6. Refresh CPPs Regularly

Treat CPPs like any other marketing asset — they need periodic updates. Screenshot trends change, feature sets evolve, and users' visual expectations shift. Review and update your CPPs at least quarterly, or whenever you release a major feature that changes the value proposition for a keyword group.

7. Don't Forget Landscape and iPad Screenshots

If your app supports iPad, make sure your CPPs include iPad-specific screenshots. iPad users often see a different layout, and generic iPhone screenshots displayed on an iPad page look low-effort. Similarly, if your app has landscape features (games, video editors), include landscape screenshots where they make sense.

How AppDrift Helps With CPP Strategy

Building and maintaining multiple Custom Product Pages requires three things: great screenshots, optimized metadata, and performance tracking. AppDrift covers all three.

Screenshot Generation at Scale

The AppDrift Screenshot Generator is purpose-built for CPP workflows. Create professional app store screenshots with a free drag-and-drop editor, customize backgrounds, device frames, and text overlays, then batch export for every required device size. When you need 5-10 screenshot sets for different CPPs, this saves hours compared to manual design work.

Metadata Optimization for Keyword Alignment

Your CPP strategy is only as good as your keyword field. AppDrift's AI metadata generation uses GPT-4 and Gemini to produce ASO-optimized titles, subtitles, and keyword fields that maximize search relevance. When building CPPs, you need a keyword field that's strategically designed with keyword linking in mind — grouping terms by intent and ensuring each high-value keyword has a dedicated CPP.

Localization for Global CPP Rollout

When CPP keyword linking expands beyond the US and UK, localized CPPs will become essential. AppDrift's metadata translation tools handle 40+ languages with cultural adaptation, not just word-for-word translation. This ensures your keyword fields and promotional texts are locally relevant in every market.

Common CPP Mistakes to Avoid

These are the errors that most commonly undermine CPP performance:

Creating CPPs without intent research. A CPP that doesn't match a specific keyword intent is just a second product page. It won't convert better than your default.
Spreading keywords too thin. Assigning one keyword per CPP when you have 50 keywords means you need 50 CPPs. Focus on your top 10-15 keywords by volume and group them into 3-5 CPPs.
Ignoring promotional text. Many developers update screenshots but leave the promotional text unchanged from the default. This is a missed opportunity to reinforce intent alignment.
Setting and forgetting. CPPs need ongoing optimization. Check performance monthly and update underperforming pages.
Using the same screenshots with minor variations. If the difference between your CPP and default page is the order of screenshots, you haven't created a meaningfully different experience.
Not tracking CPP-specific metrics. If you're not measuring conversion rates per CPP, you can't improve. Use a structured ASO checklist that includes CPP performance review as a recurring task.

The Future of Custom Product Pages

Based on Apple's trajectory, here's what ASO professionals should prepare for:

Geographic expansion of keyword linking. The US and UK rollout is almost certainly a pilot. Expect additional English-speaking markets first (Canada, Australia), followed by major European and Asian markets throughout 2026.
More customization options. Apple may eventually allow different app descriptions or even subtitles per CPP. This would give developers even more control over intent matching.
Deeper analytics integration. Current CPP analytics are basic. Apple will likely add more granular reporting: keyword-level conversion data, funnel analytics, and retention metrics tied to acquisition page.
Google Play equivalents. Google already supports custom store listings and store listing experiments. It's likely they'll introduce tighter keyword-to-listing connections to match Apple's CPP capabilities.

The apps that build CPP infrastructure now — screenshot libraries, keyword-to-intent mapping, performance tracking systems — will be best positioned to capitalize as the feature set expands.

Putting It All Together: Your CPP Action Plan

Here's a practical roadmap for implementing CPPs in your ASO strategy:

Week 1: Keyword Audit. Pull your current keyword field and rank every keyword by search volume and your current conversion rate. Identify 3-5 keyword clusters where different screenshots would improve relevance.
Week 2: Screenshot Creation. Design focused screenshot sets for each keyword cluster. Use the AppDrift Screenshot Generator to produce professional assets quickly across all required device sizes.
Week 3: CPP Setup and Submission. Create your CPPs in App Store Connect, upload screenshots, write intent-aligned promotional text, and assign keywords. Submit for review.
Week 4-8: Monitoring. Track impression, conversion, and tap-through data for each CPP. Compare against default page performance.
Week 9+: Optimization. Update underperforming CPPs with new screenshots or reassigned keywords. Consider paid campaign testing to validate changes before applying to organic search.

The key is to start small, measure everything, and expand based on data. Three well-optimized CPPs will outperform 20 hastily assembled ones every time.

Frequently Asked Questions

What are Custom Product Pages on the App Store?

Custom Product Pages (CPPs) are additional versions of your App Store listing that you create in App Store Connect. Each CPP can have its own unique screenshots, preview videos, and promotional text. Since mid-2025, you can also assign keywords from your keyword field to specific CPPs so they appear in organic search results.

How many Custom Product Pages can I create per app?

As of October 2025, Apple allows up to 70 Custom Product Pages per app, doubled from the previous limit of 35. Each CPP can be fully localized for different countries and languages, giving you a massive surface area for targeted messaging.

Do Custom Product Pages appear in organic App Store search results?

Yes. Since July 2025, Apple introduced keyword linking for CPPs. You can assign keywords from your 100-character keyword field to specific Custom Product Pages, and when a user searches for that keyword, your CPP will appear in organic search results instead of the default page.

Can I A/B test Custom Product Pages against my default product page?

Not directly. Apple's Product Page Optimization (PPO) feature tests variations of your default product page. Custom Product Pages serve a different purpose: they let you show tailored pages for specific audiences or keywords. However, you can analyze CPP performance metrics in App Store Analytics to compare conversion rates across your pages.

What elements can I customize on a Custom Product Page?

You can customize screenshots, app preview videos, and promotional text on each CPP. The app name, subtitle, icon, and description remain the same as your default listing. Since July 2025, you can also assign specific keywords to each CPP to control which page appears for different search queries.

Are Custom Product Pages available in all countries?

CPP keyword linking for organic search is currently available in the United States and the United Kingdom. However, CPPs themselves can be created and used globally for paid campaigns and direct link sharing in all App Store markets.

Organic Search

Custom Product Pages: The Complete Guide to CPPs for ASO in 2026