Back to Details

blog-page-generator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
提供博客页面结构、SEO和内容营销最佳实践指南。
调用规则：首次使用时，如果有帮助，可以先用1-2句话介绍本技能涵盖的内容及其价值，再提供核心输出。后续使用或用户要求跳过介绍时，直接输出核心内容即可。

Initial Assessment

初始评估

Check for product marketing context first: If 
.claude/product-marketing-context.md
or 
.cursor/product-marketing-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
首先检查产品营销上下文：如果存在
.claude/product-marketing-context.md
或
.cursor/product-marketing-context.md
，读取文件了解主题、受众和关键词。
识别以下信息：
  1. 博客定位：SEO引流、思想领导力打造、产品教育
  2. 内容组合：支柱页面、集群内容、新闻
  3. 受众：潜在买家、存量客户、开发者

Best Practices

最佳实践

Blog Placement: Subdomain vs Subdirectory

博客部署位置：子域名 vs 子目录

OptionExampleSEO / 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 for details.
选项示例SEO效果/适用场景
子目录
example.com/blog
SEO权重会流向主域名；推荐产品类博客使用
子域名
blog.example.com
会被搜索引擎视为独立实体；适合独立品牌或需要技术隔离的场景
根据SEO权重分配需求、品牌一致性和技术架构选择部署方式。详见Alignify子域名vs子目录指南。

Blog Index Page Structure

博客索引页结构

SectionPurpose
Featured/RecentHighlight newest or most important posts
Categories/TopicsHelp users find by theme
Editor's PicksCurate best content
Related postsPer-article recommendations
SearchHelp 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
  • 主题权威性：主题集群模式 -> 每个核心主题对应1个支柱页面 + 6-12篇集群文章
  • 意图匹配：交易型、问题感知型、信息获取型
  • EEAT信号：作者简介、Organization schema、引用来源、更新日志
  • 内容更新优于新发布：对于成熟站点，更新现有内容的效果通常优于发布新内容；避免仅修改发布日期而不做实质性更新
  • 质量优于数量：少量高质量内容远胜于大量平庸内容；可考虑删除、合并或更新表现不佳的内容
  • 主题聚焦：不要盲目拓展主题；内容过于分散会损害核心主题的权威性
  • 转化为核心目标：SEO KPI需要与线索、注册或销售挂钩，而非仅看流量

SEO

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
  • 标题：55字符以内，使用有力词汇，包含主关键词
  • Meta描述：描述中包含清晰的CTA
  • 标题层级：遵循H1-H3层级结构，配置目录
  • 内容深度：支柱页面不少于2500字；可读性达到8年级水平
  • URL：使用url-slug-generator生成简洁slug，3-5个单词，长度不超过60字符
  • Schema：适用场景下配置Article、BlogPosting、FAQPage类型的Schema

Technical

技术优化

  • Core Web Vitals: LCP < 1.0s on mobile
  • Images: WebP, compressed
  • IndexNow: For fast indexing of new posts
  • Core Web Vitals：移动端LCP < 1.0s
  • 图片：使用WebP格式，压缩处理
  • IndexNow：用于新文章快速收录

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
  • 易扫读：配置预览文案、缩略图、头图
  • 社交分享：文章页配置分享按钮 -> 参考social-share-generator
  • 快速答疑：定义框、迷你FAQ用于AEO优化
  • 目录：为获取精选片段配置目录；长文章配置跳转锚点；参考featured-snippet、toc-generator
  • CTA位置：在关键转化点配置侧边栏CTA或段落内CTA
  • 相关/最新文章：手动精选或插件实现；优先推荐相同主题集群的内容

Output Format

输出格式

  • Structure for blog index and post template
  • Content strategy (pillar + clusters)
  • SEO metadata and schema
  • Internal linking approach
  • 博客索引页和文章模板的结构
  • 内容策略（支柱+集群）
  • SEO元数据和Schema
  • 内链方案

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
  • card：博客索引页的文章卡片结构；包含封面图、标题、摘要、日期
  • grid, list：网格布局适合视觉向博客索引；列表布局适合文字向博客索引
  • article-page-generator：单篇文章/博文页面结构、SEO、Schema -> 用于单篇文章模板
  • featured-snippet：目录、答案优先格式用于获取精选片段机会
  • url-slug-generator：生成博客文章URL slug；3-5个单词，包含主关键词
  • content-strategy：内容集群、编辑日历
  • keyword-research：博客主题关键词挖掘
  • title-tag, meta-description, page-metadata, open-graph, twitter-cards：博客元数据和社交预览配置
  • schema-markup：文章Schema配置
  • resources-page-generator：博客可作为资源中心的一部分