google-search-console
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…
When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content
$ npx -y skills add kostja94/marketing-skills --skill content-optimization --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/content-optimizationContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content
name: content-optimization description: When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content structure." For keywords, use keyword-research. metadata: version: 1.2.1
Guides on-page content optimization: word count, heading keywords, keyword density vs stuffing, multimedia, tables, and lists. Complements **heading-structure** (structure) and **content-strategy** (planning).
**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.
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for target keywords and content type.
Identify: 1. **Content type**: Article, guide, listicle, pillar, news 2. **Target keyword**: Primary and secondary 3. **Competitors**: Top 10 average length and structure — see **competitor-research**
---
**Google does not rank by word count.** Length should match search intent and topic depth. A 1,000-word post that satisfies intent can outrank a 3,000-word thin piece.
For **article** word count by type (news, how-to, listicle, pillar, etc.), see **article-content**. Generic ranges:
| Content type | Word count | Notes | |--------------|-------------|-------| | **News / announcements** | 300–600 | Time-sensitive; concise | | **Standard articles / how-tos** | 1,000–1,500 | Single topic; actionable | | **Listicles / guides** | 1,200–2,000 | "Top 10," "Best X" | | **Pillar / cornerstone** | 2,000–3,500+ | Comprehensive; cluster hub |
1. **Analyze top 10** for target keyword — average length and depth 2. **Match intent** — informational often needs ~40% longer than transactional 3. **Value over padding** — each section must add genuine value; avoid fluff 4. **Comprehensive coverage** — answer the query and related questions
---
| Practice | Purpose | |----------|---------| | **Descriptive H2s** | Search engines understand context; users scan | | **Answer-first** | Place direct answer in first 40–50 words after H2 for Featured Snippets; see **featured-snippet** | | **Keyword variation** | Use related terms; avoid repeating exact phrase in every H2 | | **Logical flow** | H2s outline the article; support topical authority |
---
| Term | Meaning | |------|---------| | **Keyword density** | (Keyword count / Total words) × 100; a metric, not a ranking factor | | **Keyword stuffing** | Excessive, unnatural repetition to manipulate rankings; black-hat |
---
| Practice | Purpose | |----------|---------| | **Alt, file names, captions** | See **image-optimization** for full image SEO (alt, format, responsive, lazy loading, image sitemap, LCP, captions for Featured Snippets) | | **Original over stock** | Unique images signal E-E-A-T — see **eeat-signals** |
**Content placement**: Put images near relevant text; captions support snippet thumbnails. See **image-optimization** for captions; **featured-snippet** for snippet context.
| Practice | Purpose | |----------|---------| | **Embed + metadata** | VideoObject schema, video sitemap, thumbnail; see **video-optimization** | | **YouTube** | Google prioritizes YouTube in search; GEO citation; see **youtube-seo**, **generative-engine-optimization** | | **Featured Snippet (video)** | Video schema; timestamps/chapters; see **featured-snippet** |
| Type | Use case | SEO / Snippet | |--
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
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…
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…
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…
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic,"…
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4,"…
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,"…