Blog Page Generator
Design or audit a blog index or listing hub—placement, layout, and SEO—not individual article pages.
Overview
blog-page-generator is an agent skill most often used in Launch (also Grow) that structures and optimizes blog index and listing pages for SEO and content hubs.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill blog-page-generatorWhat is this skill?
- Covers blog index and listing structure—not single-post SEO (points to article-page-generator for posts)
- Compares subdirectory vs subdomain placement with SEO weight implications
- Initial assessment for blog purpose, content mix (pillar/cluster/news), and audience
- Reads .claude/project-context.md or .cursor/project-context.md when present for topics and keywords
- Versioned skill metadata (1.1.0) for blog homepage and content hub work
- skill metadata version 1.1.0
Adoption & trust: 844 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have posts planned but no clear blog homepage structure, URL strategy, or listing-page SEO for your product site.
Who is it for?
Indie SaaS and content founders launching or reorganizing example.com/blog-style hubs on the main domain.
Skip if: Single article optimization, paid ads landing pages, or app-store listing ASO without a web blog index.
When should I use this skill?
User mentions blog page, blog index, blog layout, content hub, blog listing, subdomain vs subdirectory, or blog SEO (not single post).
What do I get? / Deliverables
You get an assessed blog hub plan—placement, purpose, content mix, and listing SEO—ready to implement or hand off to article-page-generator for individual posts.
- Blog placement recommendation (subdirectory vs subdomain)
- Index/listing structure and SEO assessment
- Content mix alignment (pillar, cluster, news)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Blog hub structure directly affects discoverability and internal linking at Launch; ongoing content strategy also touches Grow. SEO subphase fits subdirectory vs subdomain decisions, index architecture, and listing-page signals rather than single-post schema.
Where it fits
Decide example.com/blog vs blog.example.com before publishing your first cluster.
Shape the blog homepage as the entry point for thought-leadership and product education.
Re-audit listing architecture when adding pillar pages and news mixes.
How it compares
Blog listing and hub architecture—not the article-page-generator skill for per-post schema and on-page SEO.
Common Questions / FAQ
Who is blog-page-generator for?
Solo builders and marketers using agents to launch or refactor a blog index, content hub, or listing layout for SEO traffic and education.
When should I use blog-page-generator?
At Launch when choosing blog URL structure and hub layout; at Grow when expanding pillar/cluster organization or auditing an existing blog homepage.
Is blog-page-generator safe to install?
It produces SEO and structure guidance only; review the Security Audits panel on this Prism page for the marketing-skills package before installing.
Workflow Chain
Then invoke: article page generator
SKILL.md
READMESKILL.md - Blog Page Generator
# 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