/blog
When the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or
$ npx -y skills add kostja94/marketing-skills --skill blog --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/blog
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or
SKILL.md
blog.SKILL.mdname: blog-page-generator
description: When the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or "blog SEO." For single post page SEO and schema, use article-page-generator.
metadata:
version: 1.1.0
Pages: Blog
Guides blog page structure, SEO, and content marketing best practices.
**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 it for topics, audience, and keywords.
Identify: 1. **Blog purpose**: SEO traffic, thought leadership, product education 2. **Content mix**: Pillar pages, cluster content, news 3. **Audience**: Buyers, existing customers, developers
Best Practices
Blog Placement: Subdomain vs Subdirectory
| Option | Example | SEO / Use | |--------|---------|-----------| | **Subdirectory** | `example.com/blog` | SEO weight flows to main domain; recommended for product blogs | | **Subdomain** | `blog.example.com` | Treated as separate entity; consider for distinct brands or technical isolation |
Choose based on SEO weight distribution, brand consistency, and technical architecture. See [Alignify subdomain vs subdirectory guide](https://alignify.co/zh/seo/create-blog) for details.
Blog Index Page Structure
| Section | Purpose | |---------|---------| | **Featured/Recent** | Highlight newest or most important posts | | **Categories/Topics** | Help users find by theme | | **Editor's Picks** | Curate best content | | **Related posts** | Per-article recommendations | | **Search** | Help users find specific topics |
Content Strategy
- **Topical authority**: Topic clusters -> pillar page per core topic + 6-12 cluster articles
- **Intent mapping**: Transactional, problem-aware, informational
- **EEAT signals**: Author bios, Organization schema, citations, changelog
- **Refresh > new**: For established sites, updating existing content often outperforms publishing new posts; avoid changing only the date without substantive edits
- **Quality > quantity**: Fewer high-quality posts beat many mediocre ones; consider deleting, merging, or refreshing underperformers
- **Topic focus**: Avoid blindly expanding topics; dilution can hurt authority on core topics
- **Conversion as north star**: SEO KPIs should tie to leads, signups, or sales -> not just traffic
SEO
- **Title**: 55 chars, power words, primary keyword
- **Meta**: Clear CTA in description
- **Headers**: H1-H3 hierarchy, table of contents
- **Content depth**: 2,500+ words for pillars; Grade 8 readability
- **URL**: Use **url-slug-generator** -> clean slugs, 3-5 words, under 60 chars
- **Schema**: Article, BlogPosting, FAQPage where relevant
Technical
- **Core Web Vitals**: LCP < 1.0s on mobile
- **Images**: WebP, compressed
- **IndexNow**: For fast indexing of new posts
Design
- **Scannable**: Preview copy, thumbnails, hero images
- **Social sharing**: Share buttons on article pages -> see **social-share-generator**
- **Quick answers**: Definition boxes, mini-FAQs for AEO
- **TOC**: Table of contents for Featured Snippets; jump links in long articles; see **featured-snippet**, **toc-generator**
- **CTA placement**: Sidebar CTA or in-paragraph CTA at key conversion points
- **Related/Recent posts**: Manual curation or plugin; same topic cluster
Output Format
- **Structure** for blog index and post template
- **Content** strategy (pillar + clusters)
- **SEO** metadata and schema
- **Internal linking** approach
Related Skills
- **card**: Article card structure for blog index; cover image, title, excerpt, date
- **grid, list**: Grid for visual; list for text-heavy blog index
- **article-page-generator**: Single article/post page structure, SEO, schema -> use for individual post templates
- **featured-snippet**: TOC, answer-first format for snippet opportunities
- **url-slug-generator**: URL slug for blog posts; 3-5 words, primary keyword
- **content-strategy**: Content clusters, editorial calendar
- **keyword-research**: Keywords for blog topics
- **title-tag, meta-description, page-metadata, open-graph, twitter-cards**: Blog metadata and social previews
- **schema-markup**: Article schema
- **resources-page-generator**: Blog may be part of resources hub
Read more
name: blog-page-generator description: When the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or "blog SEO." For single post page SEO and schema, use article-page-generator. metadata: version: 1.1.0
Pages: Blog
Guides blog page structure, SEO, and content marketing best practices.
**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 it for topics, audience, and keywords.
Identify: 1. **Blog purpose**: SEO traffic, thought leadership, product education 2. **Content mix**: Pillar pages, cluster content, news 3. **Audience**: Buyers, existing customers, developers
Best Practices
Blog Placement: Subdomain vs Subdirectory
| Option | Example | SEO / Use | |--------|---------|-----------| | **Subdirectory** | `example.com/blog` | SEO weight flows to main domain; recommended for product blogs | | **Subdomain** | `blog.example.com` | Treated as separate entity; consider for distinct brands or technical isolation |
Choose based on SEO weight distribution, brand consistency, and technical architecture. See [Alignify subdomain vs subdirectory guide](https://alignify.co/zh/seo/create-blog) for details.
Blog Index Page Structure
| Section | Purpose | |---------|---------| | **Featured/Recent** | Highlight newest or most important posts | | **Categories/Topics** | Help users find by theme | | **Editor's Picks** | Curate best content | | **Related posts** | Per-article recommendations | | **Search** | Help users find specific topics |
Content Strategy
- **Topical authority**: Topic clusters -> pillar page per core topic + 6-12 cluster articles
- **Intent mapping**: Transactional, problem-aware, informational
- **EEAT signals**: Author bios, Organization schema, citations, changelog
- **Refresh > new**: For established sites, updating existing content often outperforms publishing new posts; avoid changing only the date without substantive edits
- **Quality > quantity**: Fewer high-quality posts beat many mediocre ones; consider deleting, merging, or refreshing underperformers
- **Topic focus**: Avoid blindly expanding topics; dilution can hurt authority on core topics
- **Conversion as north star**: SEO KPIs should tie to leads, signups, or sales -> not just traffic
SEO
- **Title**: 55 chars, power words, primary keyword
- **Meta**: Clear CTA in description
- **Headers**: H1-H3 hierarchy, table of contents
- **Content depth**: 2,500+ words for pillars; Grade 8 readability
- **URL**: Use **url-slug-generator** -> clean slugs, 3-5 words, under 60 chars
- **Schema**: Article, BlogPosting, FAQPage where relevant
Technical
- **Core Web Vitals**: LCP < 1.0s on mobile
- **Images**: WebP, compressed
- **IndexNow**: For fast indexing of new posts
Design
- **Scannable**: Preview copy, thumbnails, hero images
- **Social sharing**: Share buttons on article pages -> see **social-share-generator**
- **Quick answers**: Definition boxes, mini-FAQs for AEO
- **TOC**: Table of contents for Featured Snippets; jump links in long articles; see **featured-snippet**, **toc-generator**
- **CTA placement**: Sidebar CTA or in-paragraph CTA at key conversion points
- **Related/Recent posts**: Manual curation or plugin; same topic cluster
Output Format
- **Structure** for blog index and post template
- **Content** strategy (pillar + clusters)
- **SEO** metadata and schema
- **Internal linking** approach
Related Skills
- **card**: Article card structure for blog index; cover image, title, excerpt, date
- **grid, list**: Grid for visual; list for text-heavy blog index
- **article-page-generator**: Single article/post page structure, SEO, schema -> use for individual post templates
- **featured-snippet**: TOC, answer-first format for snippet opportunities
- **url-slug-generator**: URL slug for blog posts; 3-5 words, primary keyword
- **content-strategy**: Content clusters, editorial calendar
- **keyword-research**: Keywords for blog topics
- **title-tag, meta-description, page-metadata, open-graph, twitter-cards**: Blog metadata and social previews
- **schema-markup**: Article schema
- **resources-page-generator**: Blog may be part of resources hub
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
Other skills on kostja94-marketing-skills.
- /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 Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
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,"
Open skill - /ai-traffic
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
Open skill - /traffic
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
Open skill - /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
Open skill - /community-forum
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,"
Open skill

