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 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.