Guide · 9 min read
App Store Custom Product Pages: How to Turn 70 CPPs Into an Organic Search Engine
App Store Custom Product Pages launched as a paid-advertising feature — alternate listings you built for Apple Search Ads campaigns, never seen by organic searchers. That changed in July 2025 when Apple added organic keyword assignment to CPPs, then doubled the page limit to 70 in October 2025. Now you can assign keywords from your metadata keyword field directly to specific custom pages; when the App Store serves an organic result for that term, your CPP shows instead of your default listing. Only 31% of apps use CPPs at all. The gap is yours to take.
App Store Custom Product Pages: 70 alternate listings, each with independent screenshots and copy
A Custom Product Page is a distinct App Store listing for your app — its own screenshots, app preview video, and promotional text — that lives at a unique URL and never replaces your default page. Until mid-2025, CPPs existed solely for paid acquisition: you built them for Apple Search Ads campaigns, each matched to a specific ad creative and audience, and organic users never encountered them. Apple raised the CPP limit from 35 to 70 in October 2025, and since July 2025, each CPP can be assigned to keywords for organic search, not just paid placements.
The structural difference from your default page is that you control screenshots and promotional text per CPP but inherit your app name, icon, description, and ratings from your default listing. That constraint is a feature: the social proof your default page has accumulated — reviews, ratings, install history — transfers automatically to every CPP. What you are adding is message specificity. A user searching for a narrow use case sees a page where every screenshot addresses exactly that use case rather than a general overview of everything your app does.
Before the organic update, building CPPs was only worthwhile if you could afford Apple Search Ads. After the update, CPPs became a free discovery asset — you build them once and the App Store serves them to relevant searchers indefinitely. For correct dimensions on the screenshots you include in each CPP, use the app store screenshot sizes reference — CPPs follow the same device-specific dimensions as your default listing.
CPP keyword assignment for organic search: how the Search Visibility field works
Keyword assignment for organic CPP visibility lives in App Store Connect under your CPP settings, in a field labeled Search Visibility. You select keywords from the set already entered in your app's metadata keyword field — you cannot assign terms that are not already there — and map each keyword or phrase to a specific CPP. When the App Store ranks your app for an assigned keyword in organic search, visitors see the CPP you designated rather than your default page.
The algorithmic side works identically to standard organic ranking: relevance, ratings, install velocity, and engagement signals still matter. The difference is that when your app wins a ranking slot for an assigned keyword, the landing page was engineered for that specific search intent rather than serving a general listing. Ranking consolidation typically appears within two to four weeks of assignment for keywords where your app already has proximity — meaning you already appear on page two or three for that term. For searches where you have no ranking proximity, keyword assignment alone does not manufacture ranking; underlying keyword relevance from your metadata still drives discovery.
One constraint Apple enforces strictly: each keyword combination must be assigned to a single CPP only. Assigning the same keyword to two pages is rejected in App Store Connect. This prevents internal cannibalization where multiple CPPs compete against each other for the same term. The practical implication is to plan your keyword-to-CPP map before you start assigning. The free ASO keyword research guide covers how to segment your keyword list by intent and volume — exactly the framework to apply before CPP assignment.
Conversion data: why CPPs outperform the default listing by 20–40%
Across active CPP programs, targeted custom pages consistently convert 20–40% higher than the default product page for the same search terms. Apple's own data makes this concrete: the average default App Store listing converts at 1.6%; apps directing traffic to a matched CPP see an average 2.5 percentage point improvement, representing a 156% relative increase. The driver is message-match — the alignment between what a user searched and what they see when they tap through.
When a user types 'habit tracker with streaks' into the App Store, they are telegraphing a specific mental model. If they tap your app and see a general overview of your feature set, they must do interpretation work — does this app do the specific thing I want? If the first screenshot is a close-up of your streak calendar with a caption reading 'build a 40-day streak you can see at a glance,' the question is answered immediately. The CPP removes one decision step between landing and downloading.
The conversion gap matters most for long-tail searches — specific, multi-word queries where a user has high intent but your default listing was never designed to answer their exact question. To explore which screenshot patterns move conversion in these cases, the screenshot A/B testing guide covers which screenshot position and caption copy changes translate directly to CPP creative decisions.
Which keywords to assign to CPPs — and which to leave to your default listing
Assign long-tail, use-case-specific keywords to CPPs, not the competitive head terms you are already working to rank for with your default page. Your default listing is built for broad appeal, which makes it adequate for broad queries. For specific, intent-driven queries like 'meal planner with grocery list and macros' or 'meditation app for sleep with timer,' a default listing covering eight features in five screenshots will always underperform a page with three screenshots all about the specific use case the user typed.
A useful segmentation approach: group your keyword list into clusters by user intent — planning-oriented users, comparison shoppers, problem-first searchers, feature-specific searchers — then build one CPP per cluster with screenshots and promotional text that speak directly to that intent. A finance app might run CPPs for 'budget tracker,' 'expense splitting app,' 'debt payoff calculator,' and 'net worth tracker' — four distinct search intents, four pages each converting better than a default page showing all four features at once. The long-tail ASO keyword strategy guide covers how App Store search behavior in 2026 has shifted toward more specific phrases, which is exactly where CPP assignment gives the highest return.
Leave branded and category head terms — your app name, your primary category keyword — to the default page. Those searches are high volume but low specificity; a specialized CPP would narrow the appeal unnecessarily. The subtitle and promotional text fields also interact with keyword ranking outside of CPPs — the App Store subtitle vs promotional text guide explains how those fields contribute to keyword relevance separately from what you assign to custom pages.
Setting up CPP keyword assignment in App Store Connect: step-by-step
Start in App Store Connect → Apps → [your app] → Custom Product Pages. Create a new CPP (or open an existing one), build the screenshots and promotional text for your target audience, and publish it. A CPP must be in a published state before keyword assignment is available — draft CPPs do not show the Search Visibility field. Once published, reopen the CPP and locate the Search Visibility section in the right sidebar. The keyword picker shows only keywords currently in your app's metadata keyword field.
If the keyword you want to assign is not in the picker, add it to your keyword field first and submit a metadata update before returning to assign it. Apple's metadata keyword field has a 100-character limit, so the terms you can assign to CPPs are bounded by what fits there. Before building CPPs, audit your keyword field and remove generic fill keywords not contributing to ranking — freeing character budget for intent-specific terms. The App Store search algorithm guide covers which field placements carry the most ranking weight, useful when deciding where to place CPP-targeted keywords.
For apps with existing CPPs built for paid campaigns: those pages are immediately eligible for organic keyword assignment without rebuilding. Open each existing CPP and assess whether its screenshots map to a clear search intent — many paid-only CPPs were optimized for ad creative coherence rather than organic search relevance. A CPP built for a 'get started free' ad creative might not be the right page to rank for 'habit tracker with streaks,' even if the screenshots overlap. The question is always: does a user arriving from organic search for that keyword see a page that specifically answers their query?
The 31% adoption gap: why building a CPP organic strategy now is the right call
Only 31% of apps use Custom Product Pages at all — and the share with organic keyword assignments is substantially lower, since keyword assignment arrived in July 2025 and most adoption data predates it. In practical terms, the majority of your category competitors either have no CPPs or are still running them as paid-only assets. The window where organic CPP assignment gives a structural advantage over competitors is open right now and will narrow as awareness of the organic ranking feature spreads.
The adoption barrier has historically been production effort: building 20 CPPs means producing 20 sets of screenshots. Using the screenshot editor, you create device-framed, captioned screenshots from a common template and swap specific elements per CPP without starting from scratch. The screenshot templates library includes starting points organized by app category, cutting CPP production time from hours to minutes. A 70-CPP strategy sounds like a large project; a 5-CPP strategy targeting your five highest-intent keyword clusters is achievable in an afternoon.
The right metric to track after keyword assignment is not impression volume — it is organic conversion rate split by page type (default vs. CPP). App Store Connect shows this breakdown in the App Acquisition section. After two to four weeks of assignment, check whether your CPPs are generating impressions for their target keywords and compare their conversion rates against your default listing for similar terms. A CPP generating 10% of your total impressions at 30% higher conversion contributes more installs than a default page capturing all impressions at a lower rate.
Build your first keyword-assigned CPP this week
The practical starting point is not planning 70 pages — it is picking the one keyword cluster where your app has the clearest differentiator and building one CPP that demonstrates that claim in three screenshots. Assign that cluster's top keyword in App Store Connect's Search Visibility section and let it run for three weeks. If conversion rate comes in meaningfully above your default listing, the strategy is proven; add the next cluster.
Every screenshot in the CPP should either show the specific feature the user searched for or answer the concern that prevents download. Build them from your existing screenshot assets in the screenshot editor — swapping captions and layout per audience is faster than rebuilding from scratch each time.
Build CPP screenshots →
Frequently asked questions
do app store custom product pages rank in organic search
Yes. Since July 2025, App Store Custom Product Pages can appear in organic search results. In App Store Connect, you assign keywords from your existing metadata keyword field to specific CPPs via the Search Visibility field. When the App Store serves an organic result for an assigned keyword, the CPP shows instead of your default product page.
how many custom product pages can i have on the app store
You can have up to 70 Custom Product Pages per app. Apple doubled the limit from 35 to 70 in October 2025. Each CPP can have its own screenshots, app preview video, and promotional text. All 70 can be assigned to different organic search keyword groups simultaneously.
how do i assign keywords to a custom product page for organic search
In App Store Connect, open a published Custom Product Page and locate the Search Visibility field in the right sidebar. The keyword picker shows only keywords currently in your app's metadata keyword field — terms not in that field do not appear. Select keywords to assign to the CPP; each keyword combination can only be assigned to one page. If your target keyword is missing from the picker, add it to your main keyword field first, submit a metadata update, then return to assign it.
do custom product pages improve app store conversion rate
Typically yes, significantly. Apps running CPPs report 20–40% higher conversion rates on targeted pages compared to the default listing for the same search terms. Apple's data shows CPPs averaging a 2.5 percentage point conversion improvement over the 1.6% default listing conversion rate — a 156% relative increase — because visitors see a page matched to their specific search intent.
can i use the same custom product page for apple search ads and organic search
Yes. A CPP can run in Apple Search Ads and organic search simultaneously — they are independent placements. Assigning organic keywords to an existing paid campaign CPP does not disrupt the ad campaign. Some developers maintain separate CPPs for paid and organic to optimize each independently, but running the same page in both is fully supported.