Apple reports a 156% conversion-rate lift when a user lands on a custom product page instead of your default App Store listing (Apple). Yet most apps still send every visitor — a high-intent keyword searcher, someone tapping a paid ad, a lapsed user being re-engaged — to the exact same page.
Two changes in 2025 made that waste harder to justify. Apple doubled the custom product page (CPP) limit to 70 per app, and it made CPPs organically searchable through keyword linking. CPPs are no longer just a paid-traffic tool; they're a core ASO lever. The problem is that teams ship them without a system — no opportunity research, no prioritization, no honest measurement — so they can't tell which page earned the install. This is the framework that fixes that: research, prioritize, build, measure, and scale.
Key Takeaways
- Apple doubled custom product pages to 70 per app (October 2025) and made them organically discoverable via keyword linking (July 2025) (RespectASO, 2026).
- The CPP framework runs in five phases: research → prioritize → build → measure → scale (AppTweak, 2026).
- Don't build all 70. Prioritize where your default page is most wrong for your highest-volume traffic — score by mismatch × traffic ÷ effort.
- Apple's 156% lift is a referred-traffic figure; a more typical CPP conversion lift is 5.9% for apps and 3.5% for games (AppTweak, 2026). Measure each page against the right baseline.
What is a custom product page (and what changed in 2026)?
A custom product page is a persistent, audience-specific version of your App Store product page. Each one carries its own screenshots (up to 10), app previews (up to 3), and promotional text (170 characters), and it's reachable by a unique ppid URL. What you can't change stays fixed across every page: the app name, subtitle, icon, description, price, rating, and category are the same everywhere. A CPP changes the creative and the pitch, not your core identity (RespectASO, 2026).
Two 2025 updates are why this framework matters now. First, Apple doubled the limit to 70 CPPs per app in late October 2025, up from 35. Second — and bigger for ASO — CPPs became organically discoverable in July 2025 through keyword linking: you assign keywords from your existing keyword field to a specific page, and that page can surface in organic search. Before that, CPPs only appeared through paid Apple Ads or direct links. Localizations are generous too: a single CPP can carry up to three languages without counting as separate slots toward the 70 (RespectASO, 2026).
This is the App Store counterpart to a Google-Play-only feature. If you run both stores, our guide to the Google Play equivalent, custom store listings covers how the same idea works on Android — where the targeting model is broader but the keyword-linking trick doesn't exist.
A custom product page is a promise, not a page. Every CPP should answer one audience's "why this app, for me, right now?" — the ad they tapped, the keyword they searched, the moment they're in. If you can't name the single promise a page makes, you're building decoration, not a CPP.
Phase 1: Research opportunities across teams
The framework opens with opportunity research, and the unlock is cross-team alignment. A single CPP can serve organic search, Apple Ads, and retargeting at once, so your opportunity list has to span all three. Pull keyword targets from whoever owns the keyword clusters worth a dedicated page, paid queries and campaigns from the Apple Ads team, and re-engagement or feature-adoption goals from user acquisition and CRM (AppTweak, 2026).
The opportunities cluster into a few repeatable sources: high-intent keyword themes your generic page underserves, top paid campaigns where the ad promises something the default page doesn't deliver, re-engagement and feature-adoption flows aimed at existing users, and off-store traffic from email, influencers, or QR codes. Each deserves a tailored landing experience. The mistake at this stage is creative-led ideation — chasing the page that sounds fun to design rather than cataloguing where real, measurable mismatch exists.
In our own audits, we start by listing every meaningful traffic source and asking one question of each: does the page it lands on answer the reason the user is there? The recurring finding is that the loudest mismatch is rarely the most creative idea on the whiteboard. It's usually mundane. A paid campaign whose ad sells one specific outcome, while the default page opens with a generic feature tour. Or a branded keyword whose searchers already want the app but get the same cold pitch as a first-time visitor. Naming those gaps source by source is what turns a vague "we should do CPPs" into a concrete build list.
Babbel is the textbook example: it built 14 custom product pages targeting language-specific searches like "learn Spanish" or "learn French," each with screenshots tuned to that exact intent, so a searcher saw their goal reflected back at them (AppTweak, 2026). That's research-led, not creative-led: the pages exist because the queries do.
Phase 2: Prioritize for impact (the rule competitors skip)
Don't build all 70. Most guides list every targeting option and then leave you to guess where to start — that's the gap this phase fills. Prioritize where your default page is most wrong for the highest-volume traffic hitting it. The simple scoring rule: mismatch × traffic ÷ effort. A page that's badly mismatched for a large, cheap-to-build audience beats a perfectly tuned page for a trickle of traffic.
There's enormous room to move here. An AppTweak study found that 69% of the top 1,000 apps and 74% of the top 1,000 games in the U.S. App Store ran no Apple Ads campaigns using CPPs at all (AppTweak, 2026). The feature is underused even among the biggest players, which means a disciplined CPP program is still a genuine edge rather than table stakes.
A starting priority order for custom product pages
Start each chosen page minimum-viable — a new first screenshot and fresh promo text is often enough to test the concept before you rebuild the whole gallery. Building lean keeps the next phases honest, because you're testing one clear idea per page.
Phase 3: Build pages around traffic and intent
Build each CPP from the query or campaign that brings the user. For an organic, keyword-linked page, the first screenshot should restate the benefit behind the search term — someone searching "budget planner" should see budgeting in frame one, not a generic feature tour. For an Apple Ads page, mirror the ad creative exactly; ad-to-page message match is where paid drop-off gets recovered. SoundCloud did this with AppTweak and saw a 58% conversion increase alongside a 39% drop in cost-per-install by aligning the page to the campaign (AppTweak, 2026).
When we build these pages, the highest-impact edit is almost always the first screenshot, not the promo text. A keyword page that simply reuses the default gallery rarely beats the default; the pages that move are the ones where frame one names the exact outcome the searcher typed. So we treat the first creative slot as the headline and write the rest of the page to support it — the same discipline a good ad takes to its hook.
Keyword linking has rules worth knowing before you build. You assign keywords from your existing 100-character keyword field — linking does not expand it — and each keyword combination maps to a single page, so you can't point the same term at two CPPs (RespectASO, 2026). Localize the pages that earn it (up to three languages per CPP, free of the 70-page cap), and use deep links to drop users into a specific in-app section on iOS 18 and later.
| Phase | Core question it answers | Main output |
|---|---|---|
| 1. Research | Where is our default page mismatched to real traffic? | A cross-team list of CPP opportunities |
| 2. Prioritize | Which page do we build first? | A ranked queue (mismatch × traffic ÷ effort) |
| 3. Build | What does this audience need to see? | A live page matched to one intent |
| 4. Measure | Did it beat the right baseline? | Per-page conversion vs. same-audience default |
| 5. Scale | What proven concept do we expand? | Localized, templated, promoted winners |
If you're wiring CPPs to paid traffic, our guide to Apple Ads automation covers how to attach the right page to each campaign so the message match holds as budgets scale.
Phase 4: Measure CPP impact the right way
Measure each CPP against the default page for the same audience — never against your blended average. A keyword page should be judged against what those searchers convert at on your default listing, not your all-traffic number. App Store Connect makes this easier than it used to be. Apple added more than 100 new CPP metrics in late 2025, including source-type filtering across organic search, Apple Ads, app referrers, and web referrers. That lets you attribute each conversion to the channel that actually drove it (RespectASO, 2026).
Product page conversion by page type (illustrative)
Read the headline numbers honestly. Apple's 156% conversion lift describes referred traffic landing on a CPP versus the default page — an upper bound, not a promise for every page you ship (Apple). A more representative benchmark is AppTweak's 5.9% conversion lift for apps and 3.5% for games (AppTweak, 2026). Both are real; they just answer different questions. The same conversion-rate optimization fundamentals that govern your default page apply inside every CPP — and conversion rate feeds the algorithm, which is why it shows up among the App Store ranking factors as a quality signal in its own right.
Phase 5: Scale what works
Scaling isn't "build more pages" — it's promoting proven concepts. When a CPP beats its baseline, roll its winning creative into adjacent keyword clusters and markets, and localize the top performers (localizations don't count against the 70-page cap) — the core of how custom product pages support global expansion. Then feed those validated screenshots back into your default listing so every visitor benefits, not just the segment. Retire the pages that underperform to stay under the ceiling, and loop the learnings back into Phase 1.
The market is maturing in exactly this direction. CPP conversion rates rose from 42.13% in 2023 to 55.87% in 2024, a roughly 32% year-over-year improvement as teams got better at matching pages to audiences (MobileAction, 2026). Scaling winners is also how localization compounds: a page that converts in one market often converts in neighboring ones once the screenshots inside each winning page are properly localized rather than just translated.
In practice, scaling well comes down to a small set of habits. Template the winning page — its layout, its first-screenshot logic, its promo angle — so the next ten pages start from a proven pattern instead of a blank canvas. Keep a standing review of the full portfolio and retire weak pages on a schedule. A stale CPP pointing at last quarter's promo quietly drags conversion and eats one of your 70 slots. Most important, treat the default listing as the ultimate beneficiary: every creative insight a CPP earns should be a candidate for the page every visitor sees. Done consistently, the five phases stop being a one-off project and become a loop — each cycle of winners feeds the next round of research.
Custom product pages vs. product page experiments
These two tools get conflated, but they do different jobs. Custom product pages segment your audience — a persistent, always-on page per keyword or campaign. Product page experiments (PPO) test creative — an A/B/C split on a single audience to find a statistical winner, with up to three treatments against your default. One decides who sees what; the other decides which creative wins (Adapty, 2026).
They work best stacked. Use an experiment to validate which screenshots or app preview convert best, then deploy that proven winner — as your new default or inside the relevant CPP. The common mistake is treating a custom product page as if it were an experiment: shipping it with no control and no clean before-and-after, then guessing whether it helped. Test to learn; segment to deploy.
Frequently asked questions
How many custom product pages can you have in 2026?
Up to 70 per app, doubled from 35 in October 2025. Localizations don't count against the limit — one page can carry up to three languages and still occupy a single slot. Each page has its own screenshots, app previews, and promotional text (RespectASO, 2026).
Do custom product pages show up in organic App Store search?
Yes. Since July 2025, CPPs became organically discoverable through keyword linking. You assign keywords from your existing keyword field to a specific page, and that page can surface in organic results. Before that, CPPs appeared only through paid Apple Ads and direct links (RespectASO, 2026).
What's the difference between a custom product page and a product page experiment?
A custom product page segments your audience with a persistent page for a keyword or campaign. A product page experiment A/B tests creative on one audience to find a winner. Test with an experiment, then deploy the winning creative as your default or inside a CPP.
How much do custom product pages improve conversion?
Apple reports a 156% lift on referred CPP traffic versus the default page, but that's an upper-bound figure. AppTweak benchmarks a more typical 5.9% conversion lift for apps and 3.5% for games. Real results depend on how well the page matches the audience (AppTweak, 2026).
Does keyword linking expand my App Store keyword field?
No. Keyword linking assigns terms from your existing 100-character field to specific pages; it doesn't add characters, and each keyword combination maps to a single page. It changes which page ranks for a term, not how many terms you can target (RespectASO, 2026).
The bottom line
Custom product pages turn one App Store listing into up to 70, each matched to a specific audience — and since 2025 they earn organic search traffic, not just paid clicks. The framework rewards system over volume:
- Research opportunities across teams, then prioritize by mismatch × traffic ÷ effort — build the highest-impact page first, not all 70.
- Build each page around the intent that brought the user, measure it against the same-audience default (not your blended average), and read Apple's 156% as an upper bound against the more typical 5.9% / 3.5% lift.
- Scale winners by localizing, templating, and feeding proven creative back into your default listing — and remember a CPP segments while a product page experiment tests.
