Custom Product Pages (CPP)
Definition
Custom Product Pages (CPP) are alternative versions of an app's Apple App Store product page, each with unique screenshots, app preview videos, and promotional text. Since July 2025, CPPs can appear in organic search results — a major shift that transformed CPPs from a paid-traffic-only feature into a full ASO strategy tool.
Developers can create up to 35 Custom Product Pages, each tailored to different audiences, use cases, or keyword clusters.
How It Works
CPP structure:
Each CPP can customize:
- Screenshots (different images, different ordering)
- App Preview Videos (different videos)
- Promotional Text (different messaging)
Cannot customize per CPP: Title, subtitle, description, icon, keyword field (these remain consistent with the default page).
Pre-July 2025 (paid traffic only):
- CPPs were linked to Apple Search Ads campaigns and external marketing URLs
- When a user clicked an ad or deep link targeting a CPP, they saw the custom page
- Organic search always showed the default product page
Post-July 2025 (organic search integration):
- Developers can assign keywords from their keyword field to specific CPPs
- When the app ranks for an assigned keyword, the matching CPP may appear instead of the default page
- This means different search queries can show different product pages
- Keyword limit per CPP: up to 70 keywords (increased from 35 in 2025)
- Only keywords from the keyword field can be assigned (not title/subtitle keywords)
Example:
- Meditation app default page: screenshots showing meditation sessions
- CPP-A (keywords: "sleep,insomnia,sleep aid"): screenshots showing sleep stories feature
- CPP-B (keywords: "stress,anxiety,calm"): screenshots showing stress relief exercises
- When user searches "sleep aid" → sees CPP-A with sleep-focused screenshots
- When user searches "stress relief" → sees CPP-B with stress-focused screenshots
Strategic Impact
This is one of the most significant ASO developments in recent years because:
- Higher conversion for diverse keyword sets — show relevant creative for each keyword cluster
- Broader keyword targeting — can now target keywords that don't match default screenshots
- Category expansion — target adjacent categories with custom messaging
- User intent matching — align creative with specific search intent
The CPP-Metadata Relationship
CPPs only matter if your Metadata Optimization drives traffic to your listing first. Search drives between 65% and 70% of all app discoveries. If your metadata isn't optimized, your CPPs sit on pages no one visits. The algorithm decides which apps appear in search results based on metadata signals—title, subtitle, keywords, and description—long before anyone sees your screenshots.
Think of it this way: metadata gets users to your listing, CPPs convert them once they arrive. A perfectly designed CPP for "sleep aid" keywords is useless if your app doesn't rank for those keywords in the first place. Metadata optimization is the prerequisite; CPP optimization is the multiplier.
The workflow:
- Optimize metadata to rank for target keywords
- Create CPPs matching user intent for those keywords
- Assign keywords to relevant CPPs
- Monitor conversion lift per CPP
Formulas & Metrics
CPP performance tracking:
CPP_CVR = CPP_Installs / CPP_Impressions × 100%
CPP_Lift = (CPP_CVR - Default_CVR) / Default_CVR × 100%
Keyword-to-CPP assignment strategy:
For each keyword cluster:
1. Group related keywords by user intent
2. Create CPP with screenshots matching that intent
3. Assign keyword group to CPP
4. Monitor CVR vs. default page for those keywords
Best Practices
- Create CPPs for distinct user intents — don't create 35 minor variations. Focus on 3-5 genuinely different use cases or audience segments.
- Assign keywords strategically — group semantically related keywords and assign them to the same CPP. "sleep, insomnia, sleep aid, bedtime" → Sleep CPP.
- Measure CPP performance vs. default — in App Store Connect, compare each CPP's conversion rate against the default page. Remove underperforming CPPs.
- Update CPPs seasonally — "holiday recipes" CPP in December, "summer fitness" CPP in June.
- Use CPPs for competitive targeting — if you rank for a competitor's brand keyword, create a CPP showing features that differentiate you from that competitor.
- Start with 3-5 CPPs — don't create 35 immediately. Start small, measure impact, then expand.
- Align CPP screenshots with keyword intent — each CPP's screenshots should directly address the user need implied by its assigned keywords. For "sleep aid" keywords, show sleep-focused features in the first three screenshots—users decide whether to install within seconds of landing on the page.
- Verify all required device sizes — missing screenshots for a specific device size means your CPP won't appear in search results on that device. Upload screenshots for every required device size (iPhone 6.7", 6.5", 5.5"; iPad Pro 12.9", iPad Pro 11") for every CPP you create.
- Localize high-traffic CPPs — if you support multiple languages and a CPP drives significant installs, create localized versions. Localized screenshots significantly boost conversion rates, and CPPs multiply that effect by matching both language and user intent.
- Ensure clarity and relevance in screenshots — Screenshots must clearly convey the app's core functionalities and benefits to avoid diluting the message. They should align with target audience expectations for better engagement.
- Leverage innovations in screenshot creation — Consider using automation tools like Fastlane, which allow for efficient screenshot generation through scripting, or employ web technologies like HTML and CSS for flexible and appealing designs. Continuous integration and deployment (CI/CD) solutions can also streamline the process by automating metadata updates alongside screenshots.
- Engage in community feedback for continual improvement — Participate in discussions to refine your visuals and receive insights on clarity, design elements, and value propositions.
Dependencies
Influences (this term affects)
- Conversion Rate — CPPs improve CVR by matching creative to search intent
- Search Optimization — CPPs add a creative dimension to keyword strategy
- Organic Installs — better CVR per keyword → more installs
- Conversion Rate Optimization (CRO) — CPPs are a major CRO lever since 2025
Depends On (affected by)
- App Store Connect — CPPs created and managed in ASC
- Keyword Field — CPP keywords must come from the keyword field
- Apple Search Algorithm — algorithm decides when to show CPP vs. default
- Screenshot — CPP screenshots must be created for each page
- Apple Search Ads — CPPs still used for paid campaign targeting
- Metadata Optimization — drives the traffic that CPPs convert
Platform Comparison
| Aspect | Apple (CPP) | Google (Custom Store Listings) | Amazon |
|---|---|---|---|
| Number of custom pages | Up to 35 | Multiple (by country, pre-reg) | None |
| Organic search integration | Yes (July 2025) | No (country-based only) | N/A |
| Keyword assignment | Yes (up to 70 per CPP) | No | N/A |
| Customizable elements | Screenshots, video, promo text | All listing elements | N/A |
Related Terms
- Product Page Optimization (PPO)
- Store Listing Experiments
- Custom Store Listings
- Keyword Field
- Apple Search Ads
- Conversion Rate Optimization (CRO)
- App Store Connect
- Metadata Optimization
Recent Updates
- 2025-07-XX: Custom Product Pages began appearing in organic search results, expanding CPP strategy beyond paid traffic
- 2025-XX-XX: Keyword assignment limit per CPP increased from 35 to 70 keywords
- 2026-04-21: CPP strategy now requires metadata optimization as prerequisite for effective implementation
- 2026-05-09: Emphasis on clarity, user relevance, and innovations in screenshot creation for improved conversion rates.
- 2026-05-11: Automation tools for creating App Store screenshots are becoming essential, enhancing efficiency and consistency in visual asset production.