affiliate-page-generator
The affiliate-page-generator skill guides creation and optimization of affiliate program pages designed to convert prospective partners into quality signups. Use it when building or improving affiliate program pages, partner landing pages, commission structure pages, or referral program content. The skill addresses the four key questions affiliates ask, provides commission structure templates, emphasizes transparent earning specifics, ensures product credibility through social proof, and applies conversion-focused design principles including mobile-first layouts and clear value propositions.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/affiliate-page-generator && cp -r /tmp/affiliate-page-generator/skills/pages/marketing/affiliate-program ~/.claude/skills/affiliate-page-generatorSKILL.md
# Pages: Affiliate Program Guides affiliate program page content and structure for conversion and quality affiliate signups. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and proof points. Identify: 1. **Commission model**: Percentage, flat rate, recurring, one-time 2. **Target affiliates**: Bloggers, influencers, agencies, etc. 3. **Product fit**: Why affiliates would promote you ## Best Practices ### Four Key Questions Affiliates Ask 1. **How much can I earn?** ? Be specific upfront 2. **Is this product worth promoting?** ? Product value, audience fit 3. **Will I be set up for success?** ? Resources, support, tracking 4. **Can I trust you to pay me?** ? Payment terms, proof ### Commission Structure (Transparency) | Item | Include | |------|---------| | Commission rate | Percentage or flat | | Recurring vs. one-time | Duration of recurring | | Cookie/tracking window | How long the cookie lasts | | Minimum payout | Threshold to receive payment | | Payment schedule | When payouts occur | | Payment methods | PayPal, bank transfer, etc. | | Refund/chargeback policy | How they affect commissions | ### Value Proposition - **Specific numbers**: "Earn 30% recurring--up to $147/month per customer" - **Earning calculator**: Help affiliates visualize income - **Avoid vague**: "Great commissions" ? "30% recurring for 12 months" ### Product Information Affiliates stake their reputation; convince them it's worth promoting: - What it does (clear, jargon-free) - Who it's for (audience, use cases) - Why it's superior (differentiators) - Social proof (customers, testimonials, logos) ### Design - Treat like a product landing page—professional, engaging; same quality as main marketing pages - **Single-focused offer**: One primary goal (signup); pages with multiple offers get ~266% fewer leads - **Minimal navigation**: Remove or reduce nav links; can increase conversion 2–28% - **Mobile-first**: Thumb-reachable CTA above fold; ~70% of users consider page speed - **Hero image/video**: Visuals can improve conversion up to 80% - **FTC-compliant disclosure**: Affiliate relationship disclosure required ### Post-Launch - Submit to affiliate program directories for discoverability - Add affiliate page link to main nav or footer ## Output Format - **Headline** and value proposition - **Commission** section structure - **Product** summary for affiliates - **FAQ** for common affiliate questions - **CTA** and signup flow - **SEO** metadata ## Related Skills - **affiliate-marketing**: Affiliate marketing strategy, recruitment, channels - **landing-page-generator**: Generic landing page structure, CTA, conversion flow; apply to affiliate signup - **pricing-page-generator**: Commission structure clarity - **customer-stories-page-generator**: Social proof for product - **homepage-generator**: Link from homepage - **hero-generator, cta-generator**: Hero and CTA design for affiliate page - **title-tag, meta-description, page-metadata**: Affiliate page metadata
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.