custom-product-pages
Generates 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.
What this skill does
# Custom Product Pages Generator Generate metadata templates for Custom Product Pages (CPPs) — targeted App Store product page variants optimized for specific audiences, ad campaigns, or traffic sources. ## When This Skill Activates Use this skill when the user: - Asks to create "custom product pages" or "targeted App Store pages" - Mentions "different App Store pages for different audiences" - Wants to create pages for specific ad campaigns (Apple Search Ads, social media) - Asks about A/B testing product page messaging - Has multiple user personas and wants tailored messaging ## Minimum Eligibility **CPPs only make sense when you have enough traffic to meaningfully split across pages.** | Monthly Impressions | Recommendation | |--------------------|----| | **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. | | **2,000-10,000** | Create 1 CPP max for your most distinct audience segment or highest-spend ad campaign. Monitor for 4+ weeks. | | **10,000-50,000** | Create 2-3 CPPs. Enough traffic to compare performance across pages. | | **50,000+** | Full CPP strategy. Multiple pages per segment, ad campaign-specific pages, seasonal variants. | **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. ## How Custom Product Pages Work - You can create up to **35 custom product pages** per app - Each page gets a unique URL you can share or use in ad campaigns - You can customize: **screenshots**, **app previews**, and **promotional text** - The app icon, name, subtitle, and description remain the same across all pages - Each page can be localized independently - Available on iOS 15+ and macOS 12+ ### CPP vs Product Page Optimization (PPO) | Feature | Custom Product Pages | Product Page Optimization | |---------|---------------------|--------------------------| | Purpose | Targeted pages for specific audiences | A/B test default page | | Count | Up to 35 pages | Up to 3 treatments | | Elements | Screenshots, previews, promo text | Icon, screenshots, previews | | URL | Unique URL per page | Same URL, random distribution | | Use with ads | Yes (assign to ad groups) | No | ## Configuration Questions Ask user via AskUserQuestion: 1. **How many custom pages?** - 1 page (single audience variant) - 2-3 pages (A/B campaign testing) - 4+ pages (multi-audience strategy) 2. **What are your distinct audiences?** - Different user roles (e.g., students vs. professionals) - Different use cases (e.g., personal vs. business) - Different traffic sources (e.g., Instagram vs. Google) - Different geographies/languages 3. **What will you customize?** - Screenshots only - Screenshots + app previews - Screenshots + promotional text - All three 4. **Traffic sources for each page?** - Apple Search Ads - Social media (Instagram, TikTok, etc.) - Website/blog - Email campaigns - Influencer partnerships - Organic/direct link ## Generation Process ### Step 1: Audience Analysis For each audience segment: - Define the primary value proposition - Identify pain points this audience has - Determine which features matter most - Choose the emotional angle (productivity, creativity, fun, savings) ### Step 2: Generate Page Metadata For each custom page: 1. **Page name** (internal reference) 2. **Promotional text** (170 characters, customizable per page) 3. **Screenshot strategy** (which features to highlight, in what order) 4. **App preview strategy** (optional, what to show in video) 5. **URL** (generated by App Store Connect, but plan the naming) ### Step 3: Screenshot Sequencing Design the screenshot order for each page to match the audience's priorities: - **Screenshot 1**: The hook — the single most compelling feature for this audience - **Screenshot 2-3**: Core value proof — features that solve their specific problem - **Screenshot 4-5**: Depth and trust — breadth of features, social proof ### Step 4: Produce Strategy Document ## Output Format ```markdown # Custom Product Pages Strategy: [App Name] ## Audience Segments | Segment | Description | Traffic Source | Page URL | |---------|-------------|---------------|----------| | [Name] | [Who they are] | [Where they come from] | [CPP URL] | --- ## Page 1: [Audience Name] ### Audience Profile - **Who**: [Description] - **Pain point**: [What frustrates them] - **Value prop**: [What you solve for them] - **Traffic source**: [Where this page is linked] ### Promotional Text (170 chars) > [Customized promotional text targeting this audience] ### Screenshot Strategy | Position | Feature | Caption | Why This Audience Cares | |----------|---------|---------|------------------------| | 1 | [Feature] | [Caption text] | [Relevance to audience] | | 2 | [Feature] | [Caption text] | [Relevance to audience] | | 3 | [Feature] | [Caption text] | [Relevance to audience] | | 4 | [Feature] | [Caption text] | [Relevance to audience] | | 5 | [Feature] | [Caption text] | [Relevance to audience] | ### App Preview (if applicable) - **Opening shot**: [What to show first] - **Key demo**: [Core feature for this audience] - **Closing CTA**: [Call to action] ### Keyword Alignment Keywords this audience is likely searching for: - [keyword 1] - [keyword 2] - [keyword 3] --- ## Page 2: [Audience Name] [Same format as Page 1] --- ## Implementation Checklist - [ ] Create custom pages in App Store Connect - [ ] Upload audience-specific screenshots for each page - [ ] Write promotional text for each page - [ ] Get unique URLs for each page - [ ] Configure Apple Search Ads to use specific pages (if applicable) - [ ] Set up UTM tracking for non-ASA traffic sources - [ ] Monitor conversion rates per page - [ ] A/B test within pages after initial launch ``` ## Strategy Templates by Use Case ### Multi-Persona App Example: Productivity app for students, freelancers, and teams | Page | Audience | Screenshot Focus | Promo Text Angle | |------|----------|-----------------|-----------------| | Default | General | Overview of all features | Broad appeal | | CPP 1 | Students | Note-taking, study tools, price | "The study companion that..." | | CPP 2 | Freelancers | Time tracking, invoicing, clients | "Manage your freelance..." | | CPP 3 | Teams | Collaboration, sharing, admin | "Team productivity that..." | ### Campaign-Specific Pages Example: Fitness app running ads on multiple channels | Page | Channel | Visual Style | Messaging | |------|---------|-------------|-----------| | Default | Organic | Clean, professional | Feature-focused | | CPP 1 | Instagram | Lifestyle, aspirational | Transformation stories | | CPP 2 | Google Search | Results-oriented | Data and progress tracking | | CPP 3 | Podcast | Social proof | "As heard on [podcast]" | ### Feature-Specific Pages Example: Photo editing app with multiple use cases | Page | Feature | Target Search Terms | |------|---------|-------------------| | Default | All features | "photo editor" | | CPP 1 | Portrait mode | "portrait editor", "selfie" | | CPP 2 | Filters | "photo filters", "instagram" | | CPP 3 | Collage maker | "photo collage", "grid" | ## Measurement & Optimization ### Key Metrics per Page - **Impressions**: How many people see the page - **Conversion rate**: Impressions → Downloads - **Retention**: Do users from this page stick around? - **Revenue**: Do users from this page convert to paid? ### Optimization Cadence 1. **Week 1-2**: Launch all pages, gather baseline data 2. **Week 3-4**: Identify best and worst performing pages 3. **Month 2**: Iterate screenshots on underperforming pages 4. **Month 3**: Test new promotional text variations 5. **Ongoing**: Refresh screenshots quarterly, adjust for seasonal relevance ## References - Related: `generators/product-page-optimization` — A/
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".