download-page-generator
The download-page-generator skill guides creation and optimization of desktop and mobile app download pages. It provides structure for presenting value propositions, platform-specific download options, trust signals, and visual proof to maximize conversion from visitor to installer. Use it when creating a new download page, auditing an existing one, or optimizing for better performance across Windows, macOS, Linux, iOS, and Android platforms.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/download-page-generator && cp -r /tmp/download-page-generator/skills/pages/marketing/download ~/.claude/skills/download-page-generatorSKILL.md
# Pages: Download Page Guides download page structure and optimization for desktop and mobile app downloads. Purpose: convert visitors into installers by clearly presenting value, platform options, and trust signals. **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 value proposition. Identify: 1. **App type**: Desktop (Windows, macOS, Linux) or mobile (iOS, Android, both) 2. **Traffic source**: Organic, paid, email, referral 3. **Distribution**: App Store / Play Store only, direct download, or both ## Page Purpose | Purpose | Goal | |---------|------| | **Download** | Guide users to install desktop or mobile app | | **Trust** | Build confidence before download (security, privacy, reviews) | | **Conversion** | Maximize download rate, store visits, install conversion | ## Download Page Structure | Step | Purpose | Elements | |------|---------|----------| | **1. Value proposition** | Why download | Headline, benefit-focused copy, key features | | **2. Platform selection** | Clear path | Desktop: OS detection or manual pick; Mobile: App Store / Play Store buttons | | **3. Trust signals** | Reduce friction | Ratings, download count, security badges, privacy note | | **4. Visual proof** | Show the app | Screenshots, app previews, video | | **5. CTA** | Primary action | Single, prominent download button | ## Platform-Specific Layout ### Desktop App - **OS detection**: Auto-detect OS or show "Download for Windows / macOS / Linux" - **Direct download**: One-click .exe / .dmg / .deb etc. - **Alternatives**: Optional "Other platforms" or "Command line" for power users ### Mobile App - **Dual store**: App Store + Play Store buttons side by side - **Smart redirect**: Detect device and show relevant store first; still show both - **QR code**: Optional for desktop visitors to scan and install on phone ## Optimization Best Practices ### Performance - **Load time**: Under 3 seconds; each extra second can cost ~7% conversion - **Mobile-first**: Most app download traffic is mobile; responsive, thumb-reachable CTAs - **Image optimization**: WebP, lazy loading, compression (e.g. TinyPNG, ImageOptim) ### Conversion - **Single primary CTA**: "Download Free Now," "Get on App Store," "Get for Windows" - **Above the fold**: CTA visible without scrolling - **Repeat CTA**: On longer pages, repeat at logical points - **A/B test**: CTA color, size, copy, placement ### Trust & Social Proof - **Star ratings**: Show App Store / Play Store ratings - **Download count**: "10M+ downloads," "Trusted by X users" - **Testimonials**: User quotes, media logos - **Security**: Security badges if collecting sensitive info ### Content - **Top 3–5 features**: Benefit-focused, scannable bullet points - **Screenshots**: High-quality, show app in action - **Video**: App preview or demo video ### Alignment with Traffic - **Ads**: If from PPC, ensure message matches ad (offer, platform); see **paid-ads-strategy** - **Email**: Match campaign message and CTA ## Output Format - **Headline** and subheadline - **Structure** (5-step flow sections) - **Platform layout** (desktop vs mobile) - **CTA** copy and placement - **Trust signals** placement - **SEO** metadata (if page is indexed) ## Related Skills ### Pages - **landing-page-generator**: Download page is a type of landing page; apply LP principles - **homepage-generator**: Homepage often links to download page - **features-page-generator**: Feature copy for "Explain value" section ### Components - **hero-generator**: Hero section (value proposition) - **cta-generator**: Download button design - **trust-badges-generator**: Social proof, ratings - **testimonials-generator**: User testimonials ### SEO - **title-tag, meta-description, page-metadata**: Download 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.