article-content
article-content generates the body text for blog posts, how-to guides, and long-form articles, covering introductions, sections, and conclusions. Use this skill when creating article body copy, listicles, or guides where the focus is on what to write rather than page structure, metadata, or conversion-focused ad copy.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/article-content && cp -r /tmp/article-content/skills/content/article ~/.claude/skills/article-contentSKILL.md
# Content: Article Content Guides creation of **article body content**—the actual text (intro, body, conclusion) for blog posts, guides, and long-form pieces. Focus on **what to write**. For **where it goes** (page structure, schema, metadata), see **article-page-generator**. For short conversion copy (ads, landing pages, CTAs), see **copywriting**. **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. ## Scope - **Article body**: Introduction, body sections, conclusion, CTA - **Content structure**: Hook, QAE pattern, paragraph length, scannability - **Word count**: By article type and search intent - **Writing frameworks**: AIDA, PAS, BAB applied to articles - **GEO elements**: TL;DR, Key Takeaways, answer-first ## Article Types & Word Count (2025) **Quality over length**: Google prioritizes comprehensive coverage of search intent, not word count. Match length to topic depth and intent. | Type | Word count | Use case | |------|------------|----------| | **News / announcements** | 300–600 | Product updates, breaking news, FAQs | | **Short-form** | 500–800 | Landing pages, product pages (scannable) | | **Standard articles / how-tos** | 1,000–1,500 | Single topic; actionable; listicles | | **Listicles** | 1,200–2,000 | "Top 10," "Best X"; numbered lists boost CTR ~70% | | **Cluster articles** | 800–2,500 | Subtopic; links to pillar | | **Pillar / cornerstone** | 2,000–3,500+ | Comprehensive; cluster hub; 6–12 sections | | **Competitive keywords** | 1,800–2,500 | Page-one SEO posts avg ~2,400 words | **Intent-based** (Google 2025): Validate 1,200–2,000; Explore 2,000–3,500; Compare 600–1,200; Do 900–1,500; Know 300–800. Informational ~40% longer than transactional. **Avoid**: Under 300 words (thin); over 7,000 (often underperforms due to reduced focus). ## Content Creation Workflow ### Four Inputs Article content rests on **four inputs**. See **article-page-generator** for full workflow. | Input | Purpose | |-------|---------| | **Product** | Connection, features, CTA placement | | **Keywords** | Target keyword, primary/secondary | | **Article intent** | Informational, commercial, transactional | | **Competitor articles** | Structure to adopt, content gaps, length target | ### Information Gain (Content Density Over Word Count) **Information gain** = net new information a page provides beyond what exists in top-ranking results. Google evaluates unique value, not comprehensiveness. Content density (unique entities, data points, insights per 100 words) matters more than word count. Skyscraper Technique (longer = better) no longer differentiates; AI made comprehensiveness cheap. **Four sources of information gain**: - **Counter-narratives**: Why "best practice" fails in certain contexts; evidence-backed - **Temporal freshness**: Data or developments after competitors' content and LLM cutoff - **SME perspectives**: Direct quotes, practitioner experience; not repackaged advice - **Proprietary data**: Original surveys, internal benchmarks, user behavior patterns **Avoid consensus content**: Restating common facts across top 10 results = zero information gain. Audit SERP before writing; list the "consensus layer"; identify gaps (unanswered questions, outdated data, underserved segments). Lead with what is new; structure answer-first. **Density check**: Count unique data points, original insights, specific claims. If ratio of new information to word count is low, cut filler. High-density content (800-1,500 words with 3+ original points) often outperforms long rehashed guides. ### TL;DR or Key Takeaways (GEO) Choose one; place after intro. Content with these elements tends to be cited more frequently by AI engines. | Format | Spec | |--------|------| | **TL;DR** | 50–100 word bold summary paragraph | | **Key Takeaways** | 5–7 bullet points | See **generative-engine-optimization** for full GEO strategy. ### Introduction **Length**: 40–120 words; 2–3 paragraphs. Readers decide in ~8 seconds; hook must work instantly. | Element | Guideline | |---------|-----------| | **Hook** | First 1–2 sentences: pain point, stat, or question; curiosity gap; specific data or contrarian fact | | **Primary keyword** | In first 100 words | | **Expectations** | Set what reader will learn | **Hook types**: "You're doing X wrong"; "97% of Y…"; bold question; challenge assumption. Well-crafted hooks boost CTR 30–50%. ### Body | Element | Guideline | |---------|-----------| | **QAE pattern** | Question (H2) → Answer (2 sentences) → Evidence (data, examples, lists) | | **Answer-first** | Direct answer in first 40–60 words after each H2 | | **Answer blocks** | 100–200 words per section; direct answer + context + evidence | | **Paragraph length** | 40–80 words; 2–4 sentences; avoid walls of text | | **Break long blocks** | Lists, H3s, images, callout boxes every 2–3 paragraphs | | **Scannability** | Front-load key info (F-pattern); **bold** key phrases; one idea per paragraph | **Long-form (1,000+ words)**: Place engagement hooks every 500–600 words; mix 40–50% explanatory text, 20–25% examples, 10–15% data, 5–10% visuals. ### Conclusion **Summary** + **CTA**: newsletter signup, related content, **product** (link to product/feature when relevant). Product-linked content ties to product naturally. ### Product Connection Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content. Link to product/feature pages naturally in conclusion or when context fits. ## Writing Frameworks Apply **copywriting** frameworks to article structure. See **copywriting** for full PAS, AIDA, BAB. | Framework | Article use | |-----------|-------------| | **AIDA** | Intro (Attention); body (Interest, Desire); conclusion (Action/CTA) | | **PAS** | How-to guides: Problem in intro; Agitation in body
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.