Custom Product Pages Now Appear in Organic Search: What Changed in 2026
Apple's July 2025 keyword-linking update lets Custom Product Pages surface in organic App Store search results, not just paid ads. Here's what changed, how it works, and what ASO teams should do now.
Custom Product Pages Now Appear in Organic Search: What Changed in 2026
Apple's July 2025 keyword-linking update lets Custom Product Pages surface in organic App Store search results, not just paid ads. Here's what changed, how it works, and what ASO teams should do now.
The Update: CPPs Went Organic
In July 2025, Apple introduced a keyword-linking feature for Custom Product Pages. Before this update, CPPs only appeared when users clicked a specific CPP URL (typically from Apple Search Ads or external campaigns). They had no presence in organic App Store search.
After the update, CPPs can now surface in organic search results. When a user searches for a keyword that you've linked to a specific CPP, Apple may show that CPP instead of your default product page. This means your audience-specific pages can now reach users organically, not just through paid traffic.
This is a fundamental shift in how CPPs work. They moved from being a paid-acquisition targeting tool to a genuine organic search asset. ASO practitioners at Phiture, AppTweak, and other tool vendors have documented ranking evidence confirming that CPPs now appear in organic search.
At the same time, Apple raised the per-app CPP cap from 35 to 70. This is not a reward — it's an expectation. If organic search now serves CPP variants, the team with 70 tightly scoped pages has a structural advantage over the team still running three.
How Keyword Linking Works
The mechanism Apple introduced:
- 1.You create a CPP with screenshots and creative tailored to a specific use case or keyword theme.
- 2.In App Store Connect, you link that CPP to specific keywords (the terms you want it to rank for organically).
- 3.When a user searches for one of those keywords, Apple's algorithm decides whether to show your default product page or the linked CPP.
- 4.If the CPP is shown and the user taps through, they see the CPP's screenshots and creative — not your default listing.
Important nuances:
- •Apple's algorithm decides which page to show — you don't control it directly. Linking a keyword to a CPP increases the likelihood it appears, but doesn't guarantee it.
- •The CPP and your default page compete for the same keyword. Apple picks whichever it judges most relevant to the user's query.
- •CPPs can appear for both paid (ASA) and organic search. The same CPP might serve an ASA ad and an organic result for different queries.
- •Keywords you link to a CPP should also be in your core monitoring stack. If a CPP ranks organically for a keyword, that keyword's performance affects your overall strategy.
This is still a relatively new feature, and Apple may refine how keyword linking and CPP organic serving work over time. Treat current behavior as a strong direction, not a permanent rule.
Why This Changes ASO Strategy
Before this update, ASO teams treated CPPs as a paid-acquisition tool. You created CPPs to match Apple Search Ads campaigns — one CPP per ad group, tailored to the keyword theme. Organic search was handled entirely by your default product page.
Now, CPPs serve both paid and organic. This changes the math:
- 1.More CPPs = more organic surface area: each CPP you create and link to keywords is another page that can rank organically. With 70 CPPs available, you can target 70 different keyword themes with tailored creative.
- 2.Default page is no longer your only organic asset: your default product page used to be the only thing users saw in organic search. Now, a user searching 'interval timer' might see your fitness CPP, while a user searching 'marathon training plan' sees a different CPP. Each gets creative tailored to their intent.
- 3.Screenshot relevance matters more: if Apple is choosing between your default page and a CPP based on relevance to the query, your screenshots need to match the query intent. A CPP with screenshots showing interval timing will rank better for 'interval timer' than your default page with generic fitness screenshots.
- 4.Localization and CPPs interact: if a CPP ranks organically in Germany for a German-language query, the page needs German copy and screenshots. Organic reach with English-only creative is a missed conversion.
- 5.Monitoring complexity increases: you now need to track ranking for your default page AND each CPP. A keyword might rank via your default page one week and via a CPP the next.
How to Build a CPP Strategy for Organic Search
Step-by-step approach to using CPPs for organic search:
- 1.Identify your keyword themes: group your target keywords by user intent. 'Meditation for sleep', 'morning meditation', 'anxiety relief meditation' are three different intents, even though they all relate to meditation.
- 2.Create one CPP per intent: for each keyword theme, create a CPP with screenshots that directly address that intent. The first screenshot should show the use case the keyword describes.
- 3.Write intent-specific captions: your default page might say 'Track Sleep Patterns'. A CPP for 'meditation for sleep' should say 'Guided Sleep Meditation'. Match the language to the query.
- 4.Link keywords to CPPs: in App Store Connect, link each CPP to the keywords it should rank for organically.
- 5.Localize high-traffic CPPs: if a CPP targets a keyword with significant volume in a non-English market, localize that CPP's screenshots and copy for that market.
- 6.Monitor ranking per CPP: use ASO tools (AppTweak, Sensor Tower, AppFollow) to track which CPPs rank for which keywords. Adjust your linking and creative based on performance.
- 7.Test and iterate: treat CPPs like any other creative asset. A/B test different screenshots for the same intent. Apple's PPO can run on CPPs, not just your default page.
- 8.Don't neglect your default page: your default page still matters. It serves users who search for your brand name, browse categories, or arrive via links. Keep it optimized as the catch-all.
How Many CPPs Should You Create?
Apple allows up to 70 CPPs per app. Should you create all 70?
When to create many CPPs (30-70):
- •Your app serves multiple distinct use cases (e.g., a fitness app with running, cycling, yoga, strength training)
- •You target multiple languages and regions
- •You have the resources to create and monitor 70 unique screenshot sets
- •Your keyword research reveals 30+ distinct intent clusters
When fewer CPPs make sense (5-15):
- •Your app has a single core use case
- •You're a small team without capacity to manage many pages
- •Your keyword research reveals few distinct intent clusters
- •You're just starting with CPPs and want to test the approach
The mistake to avoid: creating 70 CPPs with nearly identical screenshots. If your CPPs don't differ meaningfully in their creative, keyword linking won't help — Apple's algorithm picks the most relevant page, and irrelevant or duplicate CPPs won't rank.
Quality over quantity: 10 CPPs with genuinely different creative, each targeting a distinct intent, will outperform 70 CPPs with minor variations. Start with your top 5-10 keyword themes, create strong CPPs for each, and expand from there.
Resource reality: each CPP needs its own screenshot set (potentially in multiple languages and device sizes). 70 CPPs × 3 languages × 4 device sizes = 840 screenshots. Use a screenshot generator that supports batch export to make this manageable.
Common CPP Mistakes After the Organic Update
Mistakes ASO teams make with CPPs in the organic search era:
- 1.Treating CPPs as paid-only: some teams still think CPPs only serve ASA traffic. After the July 2025 update, CPPs serve organic search too. Update your strategy.
- 2.Creating CPPs without keyword linking: a CPP without linked keywords won't appear in organic search. Linking is what triggers organic serving.
- 3.Using the same screenshots across CPPs: if all your CPPs have the same screenshots, there's no relevance advantage. Each CPP should have creative tailored to its keyword theme.
- 4.Ignoring localization for CPPs: a CPP ranking organically in Japan with English screenshots is a missed conversion. Localize your highest-traffic CPPs.
- 5.Not monitoring CPP ranking: if you don't track which CPPs rank for which keywords, you can't optimize. Use ASO tools that support per-CPP rank tracking.
- 6.Forgetting the default page: your default page still serves brand searches, category browse, and unlinked queries. Don't let it stagnate while you focus on CPPs.
- 7.Creating CPPs for every keyword: not every keyword needs a CPP. Focus on keywords with distinct intent and meaningful volume. Long-tail keywords with similar intent can share a CPP.
- 8.Not testing CPP creative: CPPs are creative assets like any other. A/B test different screenshots for the same intent using PPO on CPPs.
- 9.Setting and forgetting: CPP performance changes over time. Review monthly, update creative, and adjust keyword linking based on ranking data.
- 10.Overwhelming small teams: if you're a solo developer or small team, start with 3-5 CPPs for your top keyword themes. Don't try to manage 70 from day one.
Create Screenshots for All Your CPPs
Each CPP needs its own screenshot set. Create and export them in minutes. Free, no sign-up, batch ZIP export.
Create Screenshots for 70 CPPs (Free)Related Articles
ASO Best Practices for 2026: The Complete Guide
The definitive guide to App Store Optimization in 2026. Learn the latest best practices for screenshots, keywords, localization, and conversion optimization.
ASO Trends to Watch in 2026
Stay ahead of the curve with the top ASO trends for 2026. Auto localization, dark mode, video-first listings, and more.
App Store vs Google Play: Screenshot Differences Explained
Learn the key differences between App Store and Google Play screenshot requirements, sizes, and best practices.