press-coverage-page-generator
# press-coverage-page-generator This Claude Code skill creates press coverage pages or "As Seen In" sections that aggregate third-party media mentions and awards to build audience trust. Use it when a user requests a dedicated press coverage page, wants to showcase media mentions on their homepage, or mentions related terms like "as featured in," "in the news," or "media coverage." The skill distinguishes between sparse coverage (implemented as a compact homepage section) and substantial coverage (a full dedicated page with headlines, publication links, and dates).
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/press-coverage-page-generator && cp -r /tmp/press-coverage-page-generator/skills/pages/marketing/press-coverage ~/.claude/skills/press-coverage-page-generatorSKILL.md
# Pages: Press Coverage
Guides press coverage and media mentions aggregation—showcasing third-party coverage from authoritative sites to build trust. Optional page; when coverage is sparse, implement as a small "As Seen In" or "As Featured In" section on homepage or elsewhere. Distinct from **media-kit-page-generator** (assets for journalists). For conceptual overview and comparison table, see [reference.md](reference.md).
**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 for company story and key messages.
Identify:
1. **Coverage volume**: Few mentions vs substantial
2. **Format**: Full page vs section
3. **Sources**: Publications, podcasts, awards, industry lists
## Full Page vs Section
| Format | When to Use | Placement |
|--------|-------------|-----------|
| **Full page** | Substantial coverage (10+ mentions); journalists visit for expert contacts; "inbound PR" | /press, /news, /in-the-news |
| **Section** | Sparse coverage (1–10); quick credibility; logo strip or quote carousel | Homepage below hero; About page; footer |
**Rule**: Homepage section = logos only, minimal, below main CTA. Full page = headlines, links, dates, contact.
## Full Page Structure
| Element | Guideline |
|---------|-----------|
| **Coverage list** | Chronological or by publication; headline, outlet, date, link |
| **Separation** | Press coverage (third-party) vs press releases (company-authored); coverage carries more credibility |
| **Types** | News, podcasts, video features, awards, "Best X" lists |
| **Contact** | Media inquiries; link to media kit |
| **Dates** | Optional on evergreen content; omit to keep timeless |
## Section Structure ("As Seen In" / "As Featured In")
| Element | Guideline |
|---------|-----------|
| **Logos** | Publication logos; high-contrast, consistent size |
| **Placement** | Below hero/CTA; above fold or just below |
| **Quote** | Optional: one compelling snippet; extract from best coverage |
| **Link** | Optional: "See all coverage" → full page if exists |
**Avoid**: Clutter; too many logos; low-authority outlets that dilute trust.
## Content Types to Aggregate
| Type | Example |
|------|---------|
| **News articles** | Forbes, Bloomberg, TechCrunch, industry trade |
| **Podcasts** | Interview features, guest appearances |
| **Video** | TV segments, YouTube features |
| **Awards** | "Best X 2024," "Top 10 Startups" |
| **Reviews** | Product reviews, roundups |
## Trust Principles
- **Third-party > self-authored**: Media mentions beat press releases for credibility
- **Authority matters**: Forbes, Bloomberg > unknown blogs
- **Recency**: Recent coverage signals active business; update regularly
## Output Format
- **Format** (full page vs section) recommendation
- **Structure** (elements, order)
- **Copy** (headline, intro if full page)
- **Placement** (URL, page location)
- **SEO**: Index for "company name press" / "company name news"; or noindex if thin
## Related Skills
- **media-kit-page-generator**: Press assets for journalists; press coverage page can link to media kit; distinct purposes (coverage = social proof for visitors; media kit = assets for press)
- **homepage-generator**: "As Seen In" section often on homepage
- **about-page-generator**: Press quotes can appear on About
- **customer-stories-page-generator**: Social proof; different from press (customer success vs media coverage)
- **trust-badges-generator**: "Trusted by" logos; similar visual treatment
- **public-relations**: Press release creation; coverage is outcome of PRWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
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 create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
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 create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.