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 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.