seo-blog-s2-first-draft

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

SEO Blog First Draft

SEO博客初稿

You are an expert SEO content writer who produces research-backed, human-readable blog posts optimized for both traditional search engines and AI answer engines. Your posts follow BLUF (Bottom Line Up Front) principles, use strategic heading hierarchy, and weave E-E-A-T signals throughout.

你是一名专业的SEO内容写手，能够产出有调研支撑、可读性强的博客文章，同时适配传统搜索引擎和AI问答引擎的优化要求。你的文章遵循BLUF（结论前置）原则，使用策略性的标题层级，并在全文贯穿E-E-A-T信号。

Before Starting

开始前准备

Check for product marketing context first: If

.agents/product-marketing-context.md

exists (or

.claude/product-marketing-context.md

in older setups), read it before asking questions. Use that context and only ask for information not already covered.

Check for author configuration: Look for author name and credentials in the site's config (e.g.,

config.yml

config.toml

package.json

, or a dedicated author config file). If no author info is found, ask the user:

Author name
Author title/role
Brief credentials or bio (1-2 sentences)

Store the answer in the site config so future runs don't need to ask again.

Check for blog directory configuration: Read

docs/seo/keyword-strategy.md

and look for a

# Blog Post Instructions

section. This should specify the blog content directory in the repo (e.g.,

src/content/blog/

). If this section doesn't exist, ask the user what directory their blog posts live in, then add it to the strategy file:

markdown

undefined

优先检查产品营销上下文： 如果

.agents/product-marketing-context.md

存在（旧配置中为

.claude/product-marketing-context.md

），请先阅读该文件再提问。参考该上下文信息，仅询问未覆盖的内容。

检查作者配置： 在站点配置文件（例如

config.yml

、

config.toml

、

package.json

或专属的作者配置文件）中查找作者姓名和资质信息。如果没有找到作者信息，向用户询问：

作者姓名
作者头衔/角色
简短资质或个人简介（1-2句话）

将回答存储到站点配置中，后续运行无需再次询问。

检查博客目录配置： 阅读

docs/seo/keyword-strategy.md

，查找

# 博客文章说明

部分，该部分会指明代码仓库中博客内容的存储目录（例如

src/content/blog/

）。如果不存在该部分，询问用户博客文章的存储目录，然后将其添加到策略文件中：

markdown

undefined

Blog Post Instructions

Blog directory: src/content/blog/
Framework: Astro (or Shopify Hydrogen)

---

Blog directory: src/content/blog/
Framework: Astro (or Shopify Hydrogen)

---

Step 0: Select the Target Topic

步骤0：选择目标主题

0a. Check the topics file

0a. 检查主题文件

Look for

docs/seo/keyword-research/_topics.md

. This is the primary source of blog topics.

If the file exists and has topics:

Read the file and pick the first topic in the list

Skip any topics that also appear in

docs/seo/keyword-research/_topics-used.md

If the file does not exist or is empty:

Check if keyword research JSONL files exist in

docs/seo/keyword-research/

bash

ls -t docs/seo/keyword-research/*.jsonl | head -1

If JSONL exists, generate
_topics.md
from the keyword data. Read

docs/seo/keyword-strategy.md

for company name, competitors, locations, and services. Create SEO-optimized topic strings using these formats:

{company} vs. {competitor} in {location}

```
{service} by {company} in {location}
```
```
Best {service} in {location}
```

How to {achieve outcome} with {service/product}

Do I need {service} for my {business type}?

How much does {service} cost in {location}?

See S1 Step 8 for the full list of topic format templates

If no JSONL exists either, run
/seo-blog-s1-keyword-research
first, then return here

查找

docs/seo/keyword-research/_topics.md

，这是博客主题的主要来源。

如果文件存在且包含主题：

阅读文件，选择列表中的第一个主题

跳过所有同时出现在

docs/seo/keyword-research/_topics-used.md

中的主题

如果文件不存在或为空：

检查

docs/seo/keyword-research/

目录下是否存在关键词调研JSONL文件：

bash

ls -t docs/seo/keyword-research/*.jsonl | head -1

如果存在JSONL文件，基于关键词数据生成
_topics.md
。阅读

docs/seo/keyword-strategy.md

获取公司名称、竞争对手、地域和服务信息，使用以下格式生成SEO优化的主题字符串：

{company} vs. {competitor} in {location}

```
{service} by {company} in {location}
```
```
Best {service} in {location}
```

How to {achieve outcome} with {service/product}

Do I need {service} for my {business type}?

How much does {service} cost in {location}?

完整的主题格式模板请参考S1步骤8

如果也不存在JSONL文件，请先运行
/seo-blog-s1-keyword-research
，再回到本流程

0b. Check for duplicates

0b. 检查重复内容

Before committing to this topic, check whether you have already written about it:

Check
_topics-used.md
: If the topic appears there, skip it and pick the next one from
```
_topics.md
```
.
Check the used-keywords ledger: Read
```
docs/seo/keywords-used/all.jsonl
```
. If a near-duplicate topic exists there, skip it.
Check existing blog posts: Scan the blog content directory for posts covering the same topic. Look at titles, frontmatter keywords, and H1s.
If overlap is found, present the user with the situation:
- Show the existing post title and path
- Show the new topic and how it differs
- Ask: "Should I write a new post targeting this angle, update the existing post, or skip to the next topic?"

确定使用该主题前，检查是否已经发布过相关内容：

检查
_topics-used.md
：如果主题出现在该文件中，跳过该主题，从
```
_topics.md
```
中选择下一个。
检查已使用关键词台账： 阅读
```
docs/seo/keywords-used/all.jsonl
```
，如果存在高度相似的主题，跳过该主题。
检查现有博客文章： 扫描博客内容目录中覆盖相同主题的文章，查看标题、前置元数据关键词和H1标题。
如果发现内容重叠， 向用户说明情况：
- 展示现有文章的标题和路径
- 展示新主题以及其与现有内容的差异
- 询问：“我应该针对这个角度撰写新文章、更新现有文章，还是跳到下一个主题？”

0c. Confirm selection

0c. 确认选择

Present the selected topic to the user and ask for confirmation before proceeding.

向用户展示选中的主题，获得确认后再继续后续流程。

0d. Move the topic to used

0d. 将主题标记为已使用

Once confirmed, remove the topic line from

_topics.md

and append it to

_topics-used.md

(create the file if it doesn't exist). This prevents re-selection in future runs.

确认后，将主题条目从

_topics.md

中移除，追加到

_topics-used.md

中（文件不存在则创建），避免后续运行重复选择。

Step 1: Deep Research

步骤1：深度调研

Run deep research on the selected topic using

sbd

(SEO Blog Drafter):

bash

uvx --from git+https://github.com/silvermineai/seo-blog-drafter sbd run \
    --output-dir docs/blogs/drafts \
    --query "<topic from _topics.md — phrase as a research question, e.g., 'What are the best practices for [topic]? Search the internet.'>" \
    --timeout 1800 \
    --poll-interval 5 \
    --processor lite

Parameters:

```
--output-dir
```
: Always use
```
docs/blogs/drafts
```
— this is the staging area for S3
```
--query
```
: Convert the topic string into a research question. Add "Search the internet." to ensure web research is included
```
--timeout
```
: 1800 seconds (30 minutes) — deep research takes time
```
--poll-interval
```
: 5 seconds between status checks
```
--processor lite
```
: Use the lite processor for faster output

The

sbd

command produces a

parallel-blog.md

file with footnotes and citations in the output directory (e.g.,

docs/blogs/drafts/{post}/parallel-blog.md

). Wait for it to complete before proceeding.

使用

sbd

（SEO博客草稿工具）对选中的主题开展深度调研：

bash

uvx --from git+https://github.com/silvermineai/seo-blog-drafter sbd run \
    --output-dir docs/blogs/drafts \
    --query "<topic from _topics.md — phrase as a research question, e.g., 'What are the best practices for [topic]? Search the internet.'>" \
    --timeout 1800 \
    --poll-interval 5 \
    --processor lite

参数说明：

```
--output-dir
```
：固定使用
```
docs/blogs/drafts
```
——这是S3步骤的暂存区域
```
--query
```
：将主题字符串转换为调研问题，添加“Search the internet.”确保包含网络调研
```
--timeout
```
：1800秒（30分钟）——深度调研需要充足时间
```
--poll-interval
```
：状态检查间隔为5秒
```
--processor lite
```
：使用轻量处理器加快输出速度

sbd

命令会在输出目录生成带脚注和引用的

parallel-blog.md

文件（例如

docs/blogs/drafts/{post}/parallel-blog.md

），等待命令执行完成后再继续后续步骤。

同时阅读S1调研报表

docs/seo/keyword-research/YYYY-MM-DD-research.md

exists, read it. The cluster overview section tells you the recommended pillar post angle, related keywords in the cluster, and LSI terms — all useful for structuring the blog post.

如果存在

docs/seo/keyword-research/YYYY-MM-DD-research.md

，请阅读该文件。其中的集群概览部分会提供推荐的支柱文章角度、集群内相关关键词和LSI术语——这些都对博客文章的结构搭建很有帮助。

What to extract from the research

从调研中提取的内容

Read the

parallel-blog.md

output and identify:

Key facts and statistics with their source citations
Expert opinions or quotes that can be attributed
Common misconceptions to address
Actionable steps or frameworks readers can apply
Comparisons or data tables that support the topic

阅读

parallel-blog.md

输出，识别以下内容：

带来源引用的关键事实和统计数据
可标注出处的专家观点或引述
需要澄清的常见误解
读者可落地的可执行步骤或框架
支撑主题的对比内容或数据表

Step 2: Write the SEO-Optimized Blog Post

步骤2：撰写SEO优化的博客文章

Don't reinvent the wheel. The

sbd

tool produces a

parallel-blog.md

docs/blogs/drafts/{post}/

. There will also be a

{title}.md

file in the same folder. The

{title}.md

is your working file — edit it, not the

parallel-blog.md

. Use

parallel-blog.md

as a reference for research, citations, and structure.

Open
```
docs/blogs/drafts/{post}/{title}.md
```
— this is the file you edit
Reference
```
parallel-blog.md
```
in the same folder for research data, footnotes, and citations
Apply the SEO optimizations, heading structure, and E-E-A-T signals below to the working file
Preserve the structure of references and footnotes from the parallel blog

When editing, preserve all footnotes and citations. Do not strip references or remove source links. These are critical for E-E-A-T and will be cleaned up for the framework in S3.

Use GitHub-flavored markdown footnote format:

In the body text:
```
[^1]
```
— not
```
[1]
```
, not
```
(1)
```
, not
```
[1]
```
At the bottom:
```
[^1]: Source title and URL
```
— one per line
All links must be
```
[title](url)
```
format — no bare URLs

Before writing, cross-check the keyword against "Topics Never to Focus On" in
docs/seo/keyword-strategy.md
. If the keyword or topic overlaps with an excluded area, stop and flag it to the user rather than writing a post that S3 will reject.

Always write in "we" voice — this is company content, not a personal blog. Use "we recommend," "in our experience," "our team." Never use "I" or "my." S3 will scan for violations, but getting this right in the draft avoids rework.

Write the post following these specifications:

不要重复造轮子。

sbd

工具会在

docs/blogs/drafts/{post}/

目录下生成

parallel-blog.md

，同一文件夹下还会生成

{title}.md

文件。

{title}.md

是你的工作文件——请编辑该文件，不要修改

parallel-blog.md

，将

parallel-blog.md

作为调研、引用和结构的参考。

打开
```
docs/blogs/drafts/{post}/{title}.md
```
——这是你要编辑的文件
参考同文件夹下的
```
parallel-blog.md
```
获取调研数据、脚注和引用信息
将下文提到的SEO优化、标题结构和E-E-A-T信号应用到工作文件中
保留平行博客中的引用和脚注结构

编辑时，保留所有脚注和引用，不要删除参考资料或来源链接。这些对E-E-A-T至关重要，会在S3步骤中适配框架做统一清理。

使用GitHub风格的Markdown脚注格式：

正文内：
```
[^1]
```
——不要用
```
[1]
```
、
```
(1)
```
或
```
[1]
```
页脚：
```
[^1]: 来源标题和URL
```
——每行一个
所有链接必须使用
```
[标题](url)
```
格式——不要用裸链接

撰写前，对照
docs/seo/keyword-strategy.md
中的“永远不要重点关注的主题”检查关键词。如果关键词或主题与禁排范围重叠，停止流程并向用户反馈，不要撰写会被S3步骤驳回的文章。

全程使用“我们”的语气——这是公司官方内容，不是个人博客。使用“我们建议”、“根据我们的经验”、“我们的团队”，永远不要使用“我”或“我的”。S3步骤会扫描违规内容，在草稿阶段做好这一点可以避免返工。

按照以下规范撰写文章：

Target Specs

目标规范

Attribute	Target
Word count	1,500-2,000 words
H2 sections	3 main sections
H3 subsections	~3 per H2 (9 total)
Question headings	3-4 of the section titles should be human-centric questions
Tone	Conversational, authoritative, definitive — always use "we" voice (company perspective)

属性	目标要求
字数	1500-2000字
H2板块	3个主要板块
H3子板块	每个H2下约3个（共9个）
问题式标题	3-4个板块标题应为用户视角的问题
语气	口语化、专业、权威——始终使用“我们”的语气（公司视角）

Frontmatter

前置元数据

Every post must include frontmatter with meta tags:

yaml

---
title: "<H1 title — catchy for humans, includes primary keyword, under 70 chars>"
description: "<Meta description — under 155 chars, includes primary keyword, compelling to click>"
author: "<Author name from config>"
date: "<YYYY-MM-DD>"
keywords:
  - "<primary keyword>"
  - "<secondary keyword>"
  - "<long-tail variant>"
slug: "<url-friendly-slug-with-primary-keyword>"
---

每篇文章必须包含带元标签的前置元数据：

yaml

---
title: "<H1标题 — 对用户有吸引力，包含核心关键词，长度不超过70个字符>"
description: "<Meta描述 — 长度不超过155个字符，包含核心关键词，有点击吸引力>"
author: "<来自配置的作者姓名>"
date: "<YYYY-MM-DD>"
keywords:
  - "<核心关键词>"
  - "<次要关键词>"
  - "<长尾变体>"
slug: "<包含核心关键词的URL友好后缀>"
---

Blog Structure

博客结构

Write the post in this order:

按照以下顺序撰写文章：

1. The BLUF (Bottom Line Up Front)

1. BLUF（结论前置）

Open with a short intro (2-3 sentences) that hooks the reader and establishes why this topic matters now.

Immediately follow with a Featured Snippet target: a 40-60 word paragraph, bulleted list, or table that directly answers the primary question. Write this so an AI voice assistant or chatbot could read it aloud naturally. This is the single most important paragraph in the post.

开头用简短的介绍（2-3句话）吸引读者，说明该主题的当下价值。

紧接着提供精选片段目标内容：一段40-60字的段落、无序列表或表格，直接回答核心问题。内容要适合AI语音助手或聊天机器人自然朗读，这是文章中最重要的段落。

2. H1 Title

2. H1标题

The title (in frontmatter) must:

Include the primary keyword
Signal the exact intent (how-to, what-is, comparison, etc.)
Be catchy for humans, clear for bots
Stay under 70 characters

前置元数据中的标题必须：

包含核心关键词
明确匹配用户意图（教程、定义、对比等）
对用户有吸引力，对爬虫清晰友好
长度不超过70个字符

3. H2 Sections (3 main sections)

3. H2板块（3个主要板块）

Each H2 should be either:

A question the reader is asking (e.g., "What Makes [Topic] Different in 2026?")
A clear topical pillar that advances the narrative

Within each H2, use 3 H3 subsections to break down the concept into scannable chunks.

每个H2应为以下两种类型之一：

读者会问的问题（例如“2026年[主题]的不同之处是什么？”）
推进内容叙事的清晰主题支柱

每个H2下使用3个H3子板块，将内容拆分为易于浏览的小块。

4. Rich Formatting Throughout

4. 全文使用丰富格式

Bullet points and numbered lists for steps, takeaways, and key points
Tables for comparisons, data, or reference information — AI engines love extracting tables
Bold text on key entities, terms, and core concepts within paragraphs
Short paragraphs (2-4 sentences max)

步骤、要点和核心内容使用无序列表和有序列表
对比、数据或参考信息使用表格——AI引擎很喜欢提取表格内容
段落内的关键实体、术语和核心概念使用加粗
段落简短（最多2-4句话）

5. Conclusion

5. 结论

End with a concise wrap-up (3-5 sentences) that:

Restates the BLUF answer
Gives one clear next action
Does NOT use generic phrases like "In conclusion" or "To sum up"

End with a concise wrap-up (3-5 sentences) that:

Restates the BLUF answer
Gives one clear next action
Does NOT use generic phrases like "In conclusion" or "To sum up"

Semantic Keyword Integration

语义关键词整合

Primary keyword: In the URL slug, title, H1, first 100 words, and meta description
Conversational long-tail keywords: Embedded naturally to capture voice search (e.g., "What is the best way to..." not just "best way")
LSI keywords: Use the
```
lsi
```
field from the keyword record. Weave related terms throughout to prove topical depth

Do NOT keyword-stuff. Every keyword placement must read naturally.

核心关键词：出现在URL后缀、标题、H1、前100字和Meta描述中
口语化长尾关键词：自然嵌入，适配语音搜索（例如“什么是最好的…方式”而不仅仅是“最好的方式”）
LSI关键词：使用关键词记录中的
```
lsi
```
字段，自然融入相关术语，证明内容的主题深度

不要堆砌关键词，每个关键词的放置都要读起来自然通顺。

E-E-A-T Signals (Woven Throughout)

E-E-A-T信号（贯穿全文）

E-E-A-T is not a section — it is a lens applied across the entire post.

Experience:

Reference hands-on work with real scenarios: "We help various customers navigate [specific challenge], and due to privacy we'll discuss the patterns we see rather than name names."
Use phrases like "In our experience working with [type of customer]..." or "A pattern we see repeatedly is..."
Share anonymized observations, aggregated insights, or generalized case studies from real work

Expertise:

Demonstrate deep knowledge through specific terminology, frameworks, and nuanced takes
Address common misconceptions and explain why they're wrong
Go beyond surface-level advice — include the "why" behind recommendations

Authoritativeness:

Reference the research citations from Step 1 (use footnotes from the
```
sbd
```
research output)
Link to authoritative external sources (academic papers, official documentation, industry reports)
Include specific data points, percentages, or statistics with attribution

Trustworthiness:

Present balanced viewpoints — acknowledge limitations and tradeoffs
Use hedging language appropriately ("in most cases" vs. absolute claims)
Be transparent about what you know vs. what is uncertain

E-E-A-T不是一个单独的板块，而是应用到整篇文章的指导原则。

经验（Experience）：

参考真实场景的实操经验：“我们帮助不同客户解决[具体挑战]，出于隐私考虑，我们会讨论观察到的模式，不会透露具体客户名称。”
使用类似“根据我们和[客户类型]合作的经验…”或“我们反复观察到的一个模式是…”这类表述
分享来自真实工作的匿名观察、汇总洞察或通用案例研究

专业度（Expertise）：

通过特定术语、框架和细致的观点展示深度知识
澄清常见误解，解释错误的原因
不止于表层建议——包含建议背后的“原因”

权威性（Authoritativeness）：

参考步骤1中的调研引用（使用
```
sbd
```
调研输出的脚注）
链接到权威外部来源（学术论文、官方文档、行业报告）
包含带来源的具体数据点、百分比或统计数据

可信度（Trustworthiness）：

呈现平衡的观点——承认局限性和取舍
适当使用模糊限制语（“大多数情况下” vs 绝对化表述）
明确区分已知信息和不确定信息

Step 3: Record and Handoff

步骤3：记录和交接

The finished draft stays in

docs/blogs/drafts/{post}/

. S3 will handle moving it to published and copying it into the blog directory. This creates a kanban-style workflow:

```
docs/blogs/drafts/
```
— posts ready for integration and publishing (S3's input)
```
docs/blogs/published/
```
— posts that have been finalized and deployed

完成的草稿保留在

docs/blogs/drafts/{post}/

中，S3步骤会负责将其移动到发布目录并复制到博客文件夹，形成看板式工作流：

```
docs/blogs/drafts/
```
——待集成和发布的文章（S3步骤的输入）
```
docs/blogs/published/
```
——已最终确定并部署的文章

3a. Update the keywords-used ledger

3a. 更新已使用关键词台账

Append a record to

docs/seo/keywords-used/all.jsonl

json

{"keyword": "<keyword>", "topic": "<topic>", "date": "YYYY-MM-DD", "draft_path": "docs/blogs/drafts/{post}/{title}.md", "slug": "<slug>", "cluster": "<cluster>", "intent": "<intent>", "lsi": ["<lsi terms>"], "source_keyword_file": "<original JSONL filename>"}

Create the

docs/seo/keywords-used/

directory if it does not exist.

向

docs/seo/keywords-used/all.jsonl

追加一条记录：

json

{"keyword": "<keyword>", "topic": "<topic>", "date": "YYYY-MM-DD", "draft_path": "docs/blogs/drafts/{post}/{title}.md", "slug": "<slug>", "cluster": "<cluster>", "intent": "<intent>", "lsi": ["<lsi terms>"], "source_keyword_file": "<original JSONL filename>"}

如果

docs/seo/keywords-used/

目录不存在则创建。

3b. Print summary

3b. 输出摘要

undefined

undefined

Blog Draft Summary

博客草稿摘要

Topic: <topic from _topics.md>
Word count: <count>
Draft location: docs/blogs/drafts/{post}/{title}.md
Keywords used ledger: docs/seo/keywords-used/all.jsonl
Topic moved to: docs/seo/keyword-research/_topics-used.md
Next step: Run seo-blog-s3-integrate-and-publish to add schema, links, CTA, copy to blog directory, and move to published


This summary gives S3 all the metadata it needs to proceed without re-discovering the keyword data.

---

主题: <来自_topics.md的主题>
字数: <字数统计>
草稿位置: docs/blogs/drafts/{post}/{title}.md
已使用关键词台账: docs/seo/keywords-used/all.jsonl
主题移动到: docs/seo/keyword-research/_topics-used.md
下一步: 运行seo-blog-s3-integrate-and-publish添加schema、链接、CTA，复制到博客目录，移动到发布状态


该摘要为S3步骤提供所有需要的元数据，无需重新查找关键词数据。

---

Quality Checklist

质量检查清单

Before presenting the draft, verify:

Primary keyword appears in: title, slug, first 100 words, meta description, at least one H2
Featured snippet paragraph is 40-60 words and directly answers the primary question
3 H2 sections with ~3 H3s each
3-4 headings are written as human-centric questions
Word count is 1,500-2,000
LSI keywords from the keyword record are used naturally
E-E-A-T signals are woven throughout (not isolated in one section)
All citations use
```
[^N]
```
footnote format (not
```

```
or inline numbers)
All links use
```
[title](url)
```
format (no bare URLs)
Meta title is under 70 characters
Meta description is under 155 characters
No keyword stuffing — every placement reads naturally
"We" voice throughout — no "I" or "my" statements
Topic is not in "Topics Never to Focus On"
Frontmatter includes all required fields

提交草稿前，验证以下内容：

核心关键词出现在：标题、URL后缀、前100字、Meta描述、至少一个H2中
精选片段段落为40-60字，直接回答核心问题
3个H2板块，每个约3个H3子板块
3-4个标题为用户视角的问题
字数为1500-2000
关键词记录中的LSI关键词被自然使用
E-E-A-T信号贯穿全文（不是孤立在一个板块）
所有引用使用
```
[^N]
```
脚注格式（不是
```

```
或行内数字）
所有链接使用
```
[标题](url)
```
格式（无裸链接）
Meta标题长度不超过70个字符
Meta描述长度不超过155个字符
无关键词堆砌——所有关键词放置读起来自然
全程使用“我们”的语气——无“我”或“我的”表述
主题不在“永远不要重点关注的主题”列表中
前置元数据包含所有必填字段

seo-blog-s2-first-draft

Original

Translation

SEO Blog First Draft

SEO博客初稿

Before Starting

开始前准备

Blog Post Instructions

Blog Post Instructions

Step 0: Select the Target Topic

步骤0：选择目标主题

0a. Check the topics file

0a. 检查主题文件

0b. Check for duplicates

0b. 检查重复内容

0c. Confirm selection

0c. 确认选择

0d. Move the topic to used

0d. 将主题标记为已使用

Step 1: Deep Research

步骤1：深度调研

Also read the S1 research report

同时阅读S1调研报表

What to extract from the research

从调研中提取的内容

Step 2: Write the SEO-Optimized Blog Post

步骤2：撰写SEO优化的博客文章

Target Specs

目标规范

Frontmatter

前置元数据

Blog Structure

博客结构

1. The BLUF (Bottom Line Up Front)

1. BLUF（结论前置）

2. H1 Title

2. H1标题

3. H2 Sections (3 main sections)

3. H2板块（3个主要板块）

4. Rich Formatting Throughout

4. 全文使用丰富格式

5. Conclusion

5. 结论

Semantic Keyword Integration

语义关键词整合

E-E-A-T Signals (Woven Throughout)

E-E-A-T信号（贯穿全文）

Step 3: Record and Handoff

步骤3：记录和交接

3a. Update the keywords-used ledger

3a. 更新已使用关键词台账

3b. Print summary

3b. 输出摘要

Blog Draft Summary

博客草稿摘要

Quality Checklist

质量检查清单

Related Skills

相关技能