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
- Content mix: Pillar pages, cluster content, news
- Audience: Buyers, existing customers, developers
Best Practices
Blog Placement: Subdomain vs Subdirectory
| Option | Example | SEO / Use |
|---|
| Subdirectory | INLINECODE2 | 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.
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
页面:博客
指导博客页面结构、SEO和内容营销最佳实践。
调用时:在首次使用时,如有帮助,先用1-2句话介绍此技能涵盖的内容及其重要性,然后提供主要输出。在后续使用或用户要求跳过时,直接进入主要输出。
初始评估
首先检查项目上下文: 如果存在 .claude/project-context.md 或 .cursor/project-context.md,读取其中的主题、受众和关键词。
识别:
- 1. 博客目的:SEO流量、思想领导力、产品教育
- 内容组合:支柱页面、集群内容、新闻
- 受众:买家、现有客户、开发者
最佳实践
博客放置:子目录 vs 子域名
| 选项 | 示例 | SEO / 用途 |
|---|
| 子目录 | example.com/blog | SEO权重流向主域名;推荐用于产品博客 |
| 子域名 |
blog.example.com | 被视为独立实体;考虑用于独立品牌或技术隔离 |
根据SEO权重分配、品牌一致性和技术架构进行选择。详情参见 Alignify子域名与子目录指南。
博客索引页面结构
| 部分 | 用途 |
|---|
| 精选/最新 | 突出显示最新或最重要的文章 |
| 分类/主题 |
帮助用户按主题查找 |
|
编辑推荐 | 策划最佳内容 |
|
相关文章 | 每篇文章的推荐 |
|
搜索 | 帮助用户查找特定主题 |
内容策略
- - 主题权威性:主题集群 -> 每个核心主题的支柱页面 + 6-12篇集群文章
- 意图映射:交易型、问题认知型、信息型
- EEAT信号:作者简介、组织架构、引用、更新日志
- 刷新 > 新建:对于成熟网站,更新现有内容通常比发布新文章效果更好;避免仅更改日期而无实质性编辑
- 质量 > 数量:少量高质量文章胜过大量平庸文章;考虑删除、合并或刷新表现不佳的内容
- 主题聚焦:避免盲目扩展主题;内容稀释可能损害核心主题的权威性
- 转化为北极星:SEO关键绩效指标应与线索、注册或销售挂钩 -> 而不仅仅是流量
SEO
- - 标题:55个字符,强力词汇,主要关键词
- 元描述:描述中包含清晰的行动号召
- 标题:H1-H3层级,目录
- 内容深度:支柱文章2500+字;八年级阅读水平
- URL:使用 url-slug-generator -> 简洁的slug,3-5个词,不超过60个字符
- 结构化数据:Article、BlogPosting、FAQPage(如相关)
技术
- - 核心网页指标:移动端LCP < 1.0秒
- 图片:WebP格式,压缩
- IndexNow:用于新文章的快速索引
设计
- - 可扫描性:预览文案、缩略图、主图
- 社交分享:文章页面的分享按钮 -> 参见 social-share-generator
- 快速答案:定义框、迷你常见问题解答(用于AEO)
- 目录:用于精选摘要的目录;长文章中的跳转链接;参见 featured-snippet、toc-generator
- 行动号召放置:侧边栏行动号召或段落内行动号召,放置在关键转化点
- 相关/最新文章:手动策划或插件;同一主题集群
输出格式
- - 结构:博客索引和文章模板
- 内容策略(支柱 + 集群)
- SEO元数据和结构化数据
- 内部链接方法
相关技能
- - card:博客索引的文章卡片结构;封面图片、标题、摘要、日期
- grid、list:网格用于视觉展示;列表用于文字密集的博客索引
- article-page-generator:单篇文章/帖子页面结构、SEO、结构化数据 -> 用于单个文章模板
- 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:文章结构化数据
- resources-page-generator:博客可能是资源中心的一部分