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.
What this skill does
# 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 in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".