By one estimate, English reaches only about 19% of people worldwide (Centus via App Store Localization, 2026), and localization has long paid off: in Distimo's one-week 2012 study of about 200 iPhone apps that added a native language, downloads rose 128% and revenue about 26%, though iPad apps saw no significant download growth and Distimo itself said it "is hard to tell" whether language alone drove the gain (Distimo, 2012). Treat that as direction, not a forecast. Yet plenty of apps still greet every storefront with one generic English page.
The usual response is one of two mistakes. Teams either run the listing through a translator and call it "localized," or they over-commit to a market they've never validated: full in-app localization, regional pricing, local support, legal review. Both are avoidable. A custom product page (CPP) can be localized without spending another page slot, which makes it the cheapest market-entry instrument you have. This is how to use it: which markets earn a page, how to adapt the pitch instead of just the words, and how to prove a market before you spend on it.
Key Takeaways
- Each custom product page is localizable, and its localizations live inside the page instead of using extra slots from the 70-per-app limit, so a market-specific listing costs almost nothing (Apple, 2026; Apple API docs, 2026).
- The famous "+128% downloads" localization stat comes from a one-week 2012 Distimo study of about 200 iPhone apps, so treat it as direction and prove each market with your own page (Distimo, 2012).
- Pick markets by existing traffic × conversion gap ÷ effort: build for storefronts already sending you volume, not the biggest theoretical market.
- Since keyword linking arrived (it began appearing in App Store Connect in late July 2025; Apple formally announced it on October 29, 2025), localized CPPs can win organic search per storefront, so they're no longer a paid-only tool (Apple, 2025; MobileAction, 2025).
Why are custom product pages a global-expansion tool, not just a conversion tool?
Apple describes every custom product page as localizable, and its localizations are managed inside that one page, not as extra pages against the 70-CPP limit (Apple, 2026; Apple API docs, 2026). Apple doesn't publish a cap on localizations per page; RespectASO and MobileAction both report a limit of three, so confirm what App Store Connect offers for your app before you plan around a number (RespectASO, 2026; MobileAction, 2026). Either way, a single "market" page costs you almost nothing against your budget. Most teams still think of CPPs as a paid-traffic conversion lever, and miss what they've quietly become.
Two 2025 changes reframed the tool. Apple made CPPs organically discoverable through keyword linking, which began appearing in App Store Connect in late July 2025, and on October 29, 2025 it formally announced keyword linking alongside a doubled limit of 70 pages per app (Apple, 2025). Put those together and a localized page isn't just a landing spot for Apple Ads in a new region. It's a market-specific listing that can surface in that storefront's organic search. The fixed parts of your listing stay fixed everywhere: app name, subtitle, icon, description, price, rating, and category don't change per page. What you adapt is the part that actually carries the pitch: up to 10 screenshots, 3 app previews, and 170 characters of promotional text.
How is that different from simply localizing your default listing? Default localization sets the baseline every visitor in a storefront sees. A custom product page segments on top of that baseline: a dedicated page for a specific audience, keyword, or campaign within the market. You want both: a solid localized default, plus targeted CPPs for the queries and campaigns worth a sharper pitch. For the full operating system behind running pages at scale, see our 5-phase CPP framework; this guide is the international slice of it.
A market doesn't earn a localized app until a localized page earns the install. The CPP is the cheapest localizable surface you own. Use it as a probe before you pay for in-app localization, regional pricing, and local support. The page proves the market; the market then justifies the engineering.
Which markets actually earn a custom product page?
Don't build flags on a map. Build for traffic you already have. As of 2026, the markets where apps are creating the most CPPs are English-adjacent first, then high-value localization markets: Great Britain leads with 4,550 newly created pages, followed by Canada, Australia, Germany, and Japan (MobileAction, 2026). That order is a signal: start where the friction is lowest, then move to where localization pays most.
The selection rule we use is simple: existing traffic × conversion gap ÷ localization effort. Read App Store Connect by territory and look for storefronts already sending you organic or paid volume against an English page, where conversion lags your home market. That gap is the relevance mismatch a localized page fixes. "Biggest total market" is the wrong first filter. A huge market you have no traffic in is a bet. An under-converting storefront you already reach is a measurable opportunity. To shortlist the languages worth a page, rank all 50 App Store languages first.
Where apps are creating the most custom product pages (2026)
It helps to sort candidates into tiers before you commit a single page. Tier one is the cheap win; tier three is the "not yet."
| Tier | Markets | Effort | Build when |
|---|---|---|---|
| 1. Translate-first | English-adjacent (GB, CA, AU) | Low: copy & trust tweaks | You already have traffic; convert it better now |
| 2. Full adaptation | High-value non-English (DE, JP, FR) | High: language, culture, creative | Traffic or paid intent exists and the conversion gap is real |
| 3. Wait | No measurable traffic yet | n/a | Probe with one page first; don't pre-build the gallery |
Our App Store localization fundamentals page covers the territory-by-territory groundwork that feeds this decision.
Why localize the value proposition, not just the words?
Translation is table stakes; the lift comes from changing what you lead with per market. Headspace adapts its custom product page value proposition across regions: meditation benefits in the US, practical sound features in Ireland, sleep and relaxation in Australia. It's the same app making a different first promise to each audience (MobileAction, 2026). Same product, different reason to install.
Why does that matter so much more than a clean translation? Because people in different markets justify the download for different reasons, and the first screenshot is where that justification either lands or doesn't. KAYAK localized for France by adapting both copy and screenshots, not just running English through a translator. FOREX.com goes further and localizes its trust signals: the Canadian page leads with institutional credibility and awards, while the US page emphasizes performance tools and risk management. Trust is cultural, and the proof a German fintech user wants is not the proof a US trader wants.
Seasonality is the same story. Zalando builds country-specific Black Friday pages across the UK, France, and Italy rather than rolling out one global promo. The moment, the offer framing, and the calendar all differ by market (here's when to ship Black Friday listing changes). When you adapt these elements together (screenshots, captions, trust markers, and seasonal hooks), you get a page that feels native, not one that feels imported.
A page that simply re-uses your English gallery with translated captions rarely beats a clean default localization. The pages that move conversion are the ones where frame one names the outcome that specific market actually buys on. That means rewriting the pitch, not the sentence.
One gap most guides skip: non-Western markets ask for more than language. Script direction, color meaning, local payment methods, and feature expectations all shift the creative. A page localized for Japan or Saudi Arabia that ignores those signals reads as foreign no matter how accurate the translation. When you do reach the screenshot stage, our guide to translating and adapting your screenshots per market covers the practical workflow.
How do you validate a market before you commit to full localization?
Full market entry is expensive: in-app localization, regional pricing, local support, sometimes legal review (see the full cost of in-app localization). A localized CPP is the cheapest probe you have: its localizations live inside a single page slot, so you can stand up a market-specific listing for almost no budget cost and point a small Apple Ads test or a linked locale keyword at it (Apple, 2026). Then you let tap-through and conversion tell you whether the market is real before you fund the engineering.
The loop is short. Ship one localized page. Read its conversion against the English default served to that same storefront. Then decide: go (fund full localization and pricing) or no-go (retire the page, move the slot). You don't need a full gallery to learn this. A new first screenshot and 170 characters of localized promo text is enough to test the concept. Pair it with a product page experiment if you want to isolate which creative is doing the work.
| Step | What you do | What it tells you |
|---|---|---|
| 1. Probe | Ship one localized CPP (one slot, localized for the target market) | Whether the localized pitch lands at all |
| 2. Point traffic | Small Apple Ads test or a linked locale keyword | Real demand at a real cost-per-install |
| 3. Read | Compare vs. the English default in that storefront | The true localization lift, isolated |
| 4. Decide | Go (full localization) or no-go (retire the slot) | A funded market, or a cheap lesson |
This is the use case competitors barely name. A CPP isn't only a conversion page. It's a market-validation instrument that costs one slot and a few days. Treated that way, "should we localize for Brazil?" stops being a strategy debate and becomes a test you can run next sprint.
How do localized pages win both organic and paid traffic per storefront?
Since keyword linking arrived in 2025 (it began appearing in App Store Connect in late July, and Apple formally announced it on October 29), custom product pages can appear in organic App Store search, so localized pages aren't just for Apple Ads anymore (Apple, 2025; MobileAction, 2025). You assign keywords from your existing keyword field for a storefront to the matching localized page, and that page can replace the default in organic results for those terms. A German searcher can land on your German page from a search, not only from an ad.
The discipline is to make organic and paid point at the same localized promise. Assign locale-specific keywords to the localized page so organic search routes correctly, and mirror your Apple Ads creative for that market so the ad and the page tell one story. Keyword linking works from your existing field and doesn't expand the character budget. So this is about pointing terms at the right page, not adding more terms. Placement context matters too: a tap from search results, the Search tab, and the Today tab each carries a different mindset, and the page should respect that.
Does the alignment pay off? Apple reports a 156% conversion-rate lift when users are referred to a custom product page instead of the default (Apple, 2026). That's an upper-bound, referred-traffic figure, but a clear signal that matching the page to the intent works. When the user's expectation, set by an ad, a search, or a referral, matches what the page delivers, conversion climbs. If you're wiring these pages to paid budgets, our guide to Apple Ads automation covers attaching the right localized page to each campaign.
Measure market pages against the right baseline (and respect the maintenance cost)
Judge a localized CPP against the English default served to that same storefront, never your global blended average. That comparison is the only one that isolates the localization lift. App Store Connect makes it doable: Apple added more than 100 CPP metrics in late 2025, including source-type filtering across organic, Apple Ads, and referrers, so you can attribute each conversion to the channel that drove it (RespectASO, 2026). Give small storefronts time to reach a readable sample. A market with low volume needs patience, not a verdict after a week.
English default vs. localized page, by storefront (illustrative)
Then weigh the part nobody likes to mention: maintenance. Seventy pages, multiplied by seasonal refreshes, multiplied by every localization you add to each, is real upkeep. A stale page pointing at last quarter's promo quietly drags conversion and eats a slot you could use elsewhere. Set a recurring portfolio review, hold low-traffic markets to a ~90% confidence bar before you call a winner, and retire pages that don't earn their place. The market itself is maturing in this direction. CPP conversion rates rose from 42.13% in 2023 to 55.87% in 2024 as teams got more disciplined (MobileAction, 2026).
Scale winning markets into the rest of your store
A validated market compounds. When a localized page beats the same-storefront default, the move isn't "build more pages." It's promoting the proven concept. Roll the winning creative into adjacent storefronts and languages, and feed those validated screenshots back into your default localization for that market so every visitor benefits, not just CPP traffic. That's where the payoff shows up: a lift you measured on your own storefront traffic, not one borrowed from a benchmark.
Pricing is part of scaling, not an afterthought. Business of Apps reports that paying in local currency can improve purchase acceptance by as much as 30%, and that supporting even two currencies adds 12.7% to growth (Business of Apps, 2026). A market you validated with a single page is a market ready for that fuller treatment. And if you run both stores, bring the same audience targeting to Android. Our guide to the Google Play equivalent, custom store listings, covers how the model differs there. Graduate winners, retire laggards, and loop the learning back into market selection. That's the difference between a pile of pages and a global program.
Frequently asked questions
Can you localize a custom product page by country?
Yes. Apple describes every custom product page as localizable: for each localization you adapt the screenshots, app previews, and 170-character promo text for a language and region. Those localizations live inside the page rather than counting as separate pages, so a market-specific page doesn't spend an extra slot from the 70-per-app limit (Apple, 2026; Apple API docs, 2026).
How many localizations can one custom product page have?
Apple doesn't publish a number. Its App Store Connect Help describes each custom product page as localizable, and its API manages localizations inside the page rather than as separate pages, so localizing doesn't spend extra slots from the 70-page maximum. Several ASO vendors, including RespectASO and MobileAction, report a cap of three localized versions per page, so check what App Store Connect offers for your app before you plan around that figure. Either way, one localized page is an unusually cheap way to test market-specific messaging before you commit to fully localizing the app (Apple, 2026; Apple API docs, 2026; RespectASO, 2026; MobileAction, 2026).
Do localized custom product pages show in organic search abroad?
Yes. Keyword assignment for custom product pages began appearing in App Store Connect in late July 2025, and Apple formally announced it on October 29, 2025. You assign keywords from your existing keyword field for a storefront to a specific localized page, and that page can replace the default in search results for those terms. A German searcher can land on the German page from organic search, not just from a paid ad (Apple, 2025; MobileAction, 2025).
Should I build a custom product page for every market I launch in?
No. Prioritize storefronts already sending you organic or paid traffic against an English page where conversion lags: existing traffic times the conversion gap, divided by localization effort. Build for traffic you already have, not flags on a map. English-adjacent markets are cheap first wins; high-value non-English markets pay most.
How much can localization improve performance?
Directionally, a lot, but the famous numbers are old. In Distimo's September 2012 study of about 200 iPhone apps that added a native language, downloads rose 128% and revenue about 26% in the following week, though iPad apps saw no significant download growth and Distimo said it was hard to tell whether language alone caused the lift. On pricing, Business of Apps reports that paying in local currency can improve purchase acceptance by as much as 30%. Validate each market with a localized page rather than banking on a benchmark (Distimo, 2012; Business of Apps, 2026).
The bottom line
Custom product pages turn international expansion from a big, all-at-once bet into a series of cheap, measurable tests. The economics are on your side: localizations that don't cost extra page slots, organic discoverability per storefront, and a 70-page ceiling you'll rarely need to reach.
- Pick markets by existing traffic × conversion gap ÷ effort, not by total addressable market. English-adjacent storefronts are the cheap first wins.
- Localize the value proposition, trust signals, and seasonal hooks together, not just the words. Remember that non-Western markets ask for more than translation.
- Use one localized page to validate a market before funding full localization, link locale keywords so the page wins organic and paid, and measure against the same-storefront English default.
- Scale winners into adjacent markets and your default listing; retire the pages that don't earn their slot.
