blog-page-generator
# blog-page-generator This skill guides the structure, SEO optimization, and content strategy for blog index and listing pages rather than individual posts. Use it when creating or auditing a blog homepage, index layout, content hub organization, subdomain versus subdirectory setup, or overall blog architecture and SEO performance. It covers placement decisions, page section organization, topical authority strategy, and quality metrics tied to conversion goals.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/blog-page-generator && cp -r /tmp/blog-page-generator/skills/pages/content/blog ~/.claude/skills/blog-page-generatorSKILL.md
# 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
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
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 create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
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 create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.