skills/seo/content/content-optimization/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills content-optimizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
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 |
| 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 |
<table>, <thead>, <tbody>, clear column headers| Type | Use case | SEO / Snippet |
|------|----------|---------------|
| Ordered (<ol>) | Steps, rankings, sequences, "Top 10" | List snippets (~19% of Featured Snippets); how-to; see featured-snippet |
| Unordered (<ul>) | Non-sequential items, features, options | Bullet snippets; definitions, options |
Best practices:
<ol> and <ul>; avoid divs styled as listsAnswer-first (direct answer in first 40–60 words after H2) supports both Featured Snippets and GEO. For article-level GEO (TL;DR, Key Takeaways, QAE pattern), see article-content and generative-engine-optimization. For Featured Snippet formats and optimization, see featured-snippet.
For article content audit (hook, QAE, product connection, CTA, references, gaps), see article-content. This skill covers generic content optimization (H2 keywords, multimedia, keyword density).
<ol> lists; HowTo vs FAQtesting
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
development
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
testing
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.