$npx -y skills add rshankras/claude-code-apple-skills --skill custom-product-pagesGenerates Custom Product Page metadata templates with screenshot strategies, keyword targeting, and audience-specific messaging for up to 35 page variants. Use when creating targeted App Store pages for different audiences, ad campaigns, or traffic sources.
| 1 | # Custom Product Pages Generator |
| 2 | |
| 3 | Generate metadata templates for Custom Product Pages (CPPs) — targeted App Store product page variants optimized for specific audiences, ad campaigns, or traffic sources. |
| 4 | |
| 5 | ## When This Skill Activates |
| 6 | |
| 7 | Use this skill when the user: |
| 8 | - Asks to create "custom product pages" or "targeted App Store pages" |
| 9 | - Mentions "different App Store pages for different audiences" |
| 10 | - Wants to create pages for specific ad campaigns (Apple Search Ads, social media) |
| 11 | - Asks about A/B testing product page messaging |
| 12 | - Has multiple user personas and wants tailored messaging |
| 13 | |
| 14 | ## Minimum Eligibility |
| 15 | |
| 16 | **CPPs only make sense when you have enough traffic to meaningfully split across pages.** |
| 17 | |
| 18 | | Monthly Impressions | Recommendation | |
| 19 | |--------------------|----| |
| 20 | | **Under 2,000** | Don't create CPPs. Focus on optimizing your single default page. You won't have enough traffic per page to know if it's working. | |
| 21 | | **2,000-10,000** | Create 1 CPP max for your most distinct audience segment or highest-spend ad campaign. Monitor for 4+ weeks. | |
| 22 | | **10,000-50,000** | Create 2-3 CPPs. Enough traffic to compare performance across pages. | |
| 23 | | **50,000+** | Full CPP strategy. Multiple pages per segment, ad campaign-specific pages, seasonal variants. | |
| 24 | |
| 25 | **Exception:** If you're running paid Apple Search Ads campaigns, CPPs are valuable even at lower organic volume because ad traffic is directed specifically to your CPP — you're not splitting organic impressions. |
| 26 | |
| 27 | ## How Custom Product Pages Work |
| 28 | |
| 29 | - You can create up to **35 custom product pages** per app — prioritize a few distinctive pages over filling all 35 |
| 30 | - Each page gets a unique URL: your default App Store link plus a product-page-ID parameter; devices below iOS 15 (or a disabled page) fall back to the default page |
| 31 | - You can customize: **screenshots**, **app previews**, and **promotional text** |
| 32 | - The app icon, name, subtitle, and description remain the same across all pages |
| 33 | - Each page is fully localizable, independently of the default page |
| 34 | - Available on iOS 15+ and macOS 12+; the App Store Connect API automates page creation at scale |
| 35 | |
| 36 | ### Review & Compliance |
| 37 | |
| 38 | - CPP metadata goes through App Review (Guideline 2.3 — accurate metadata), though submission is binary-independent — no new build needed |
| 39 | - ❌ No pricing, offers, or sales language in page metadata ("50% off", "free trial") — prices vary by region and change without the page changing |
| 40 | - Partner/ad-network tracking against CPP traffic requires App Tracking Transparency consent |
| 41 | - Today-tab Apple Search Ads campaigns require a CPP with **≥4 portrait or ≥5 landscape assets** plus a separate creative review |
| 42 | |
| 43 | ### Search Keyword Assignment (WWDC25) |
| 44 | |
| 45 | You can assign keywords to a custom product page, per language, so App Store searches on that keyword land on the matching CPP instead of the default page: |
| 46 | |
| 47 | - Assignment alone needs no App Review — the page was already approved |
| 48 | - Make keyword selections unique per page — don't point multiple pages at the same term |
| 49 | - Read per-CPP search traffic in App Analytics to see which assignments pull weight |
| 50 | |
| 51 | ### CPP vs Product Page Optimization (PPO) |
| 52 | | Feature | Custom Product Pages | Product Page Optimization | |
| 53 | |---------|---------------------|--------------------------| |
| 54 | | Purpose | Targeted pages for specific audiences | A/B test default page | |
| 55 | | Count | Up to 35 pages | Up to 3 treatments | |
| 56 | | Elements | Screenshots, previews, promo text | Icon, screenshots, previews | |
| 57 | | URL | Unique URL per page | Same URL, random distribution | |
| 58 | | Use with ads | Yes (assign to ad groups) | No | |
| 59 | |
| 60 | ## Configuration Questions |
| 61 | |
| 62 | Ask user via AskUserQuestion: |
| 63 | |
| 64 | 1. **How many custom pages?** |
| 65 | - 1 page (single audience variant) |
| 66 | - 2-3 pages (A/B campaign testing) |
| 67 | - 4+ pages (multi-audience strategy) |
| 68 | |
| 69 | 2. **What are your distinct audiences?** |
| 70 | - Different user roles (e.g., students vs. professionals) |
| 71 | - Different use cases (e.g., personal vs. business) |
| 72 | - Different traffic sources (e.g., Instagram vs. Google) |
| 73 | - Different geographies/languages |
| 74 | |
| 75 | 3. **What will you customize?** |
| 76 | - Screenshots only |
| 77 | - Screenshots + app previews |
| 78 | - Screenshots + promotional text |
| 79 | - All three |
| 80 | |
| 81 | 4. **Traffic sources for each page?** |
| 82 | - Apple Search Ads |
| 83 | - Social media (Instagram, TikTok, etc.) |
| 84 | - Website/blog |
| 85 | - Email campaigns |
| 86 | - Influencer partnerships |
| 87 | - Organic/direct link |
| 88 | |
| 89 | ## Generation Process |
| 90 | |
| 91 | ### Step 1: Audience Analysis |
| 92 | |
| 93 | For each audience segment: |
| 94 | - Define the primary value proposition |
| 95 | - Identify pain points this audience has |
| 96 | - Deter |