blog-page-generator
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.
Best use case
blog-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using blog-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/blog/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How blog-page-generator Compares
| Feature / Agent | blog-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# 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
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.