First Version English Outline

第一版英文大纲 Skill

Overview

Turn a target keyword or topic into an English-first blog outline with Chinese translations. Analyze and explain Steps 1–6 in Chinese. In the outline, place each English title, H2, H3, and FAQ question on one line and its Chinese translation on the next line. Base the structure on live Google Top 10 organic results, the reader's task, and the article's actual scope. Always include a context-appropriate product or brand integration and a search-backed, semantically non-duplicative FAQ.

Operating Mode

• Use seven-stage confirmation by default. Output one major stage, then wait for the user to confirm, revise, or continue.
• Do not output the full workflow in one pass unless the user explicitly requests a one-shot result.
• Apply user revisions to every later step.
• Write research, reasoning, comparisons, and recommendations in Chinese during Steps 1–6.
• Write the formal outline in English first, followed immediately by natural Chinese translations on separate lines.
• Preserve official spelling and capitalization for keywords, brands, products, standards, and industry terms.
• Keep the article reader-first. Do not let product promotion interrupt the primary answer path.
• Always integrate the designated product or brand. Adapt its role, placement, depth, frequency, wording, and conversion intensity to the topic.
• Always include a qualified FAQ after the main-body close.
• Do not add per-section keyword mapping, suggested-length fields, recommended-source fields, E-E-A-T modules, or standalone fact-checking modules.

Mandatory Google Research

• Use Google in Chrome through the installed Search Simulator extension.
• Search the exact target keyword first for the target market, location, and language.
• Gather the first 10 visible organic results in their displayed order before analyzing intent, proposing titles, or building the outline.
• Exclude ads, sponsored placements, AI Overviews, featured snippets, map packs, video packs, and other non-organic modules unless the user explicitly requests them.
• Do not substitute a generic web-search tool, another search engine, direct Google browsing without Search Simulator, or an inferred ranking list.
• Record the query, Google locale/domain, simulated location, language, search date, visible region, observable Chrome sign-in state, and evidence that Search Simulator was used.
• Explain that geography, language, timing, and other factors may change result order.
• If Chrome, Search Simulator, or Google cannot be accessed, stop before search-intent analysis and ask the user to restore access or provide a Google results screenshot/export produced through this process.

Workflow

Step 1: Confirm Input and Research Scope

Identify:

• Target keyword or topic.
• Target reader and business context.
• Target country or market, Google domain, simulated location, and English variant when provided.
• Product, brand, and URL that must be integrated. Obtain missing product details before finalizing the outline.

Inspect each accessible Top 10 page. Record exactly the same fields as the Chinese first-version outline workflow:

• Organic rank.
• Page title.
• URL.
• Site or brand.
• Content type.
• Title promise.
• Main H2s.
• Primary search intent.
• Content depth.
• Distinctive information.
• Apparent gaps.
• FAQ or long-tail questions.
• Whether the page body opened successfully.
• Reason it was inaccessible, when observable.

For inaccessible pages:

• Preserve the original Google rank.
• Record only visible or accessible information.
• Do not infer H2s, depth, FAQ, or body content.
• Do not replace the result with rank 11 or later.
• Label later results as supplemental if they are inspected.
• State how many Top 10 bodies were inspected and whether access failures materially weaken the comparison.

When useful, also inspect authoritative pages around the Top 20, People Also Ask, related searches, and autocomplete suggestions. Synthesize dominant formats, recurring H2 themes, repeated questions, common omissions, possible differentiation, and structures not worth copying.

Checkpoint:

Step 1 研究范围确认
- 目标关键词/主题：
- 目标读者：
- 业务背景：
- 目标市场与英语版本：
- 搜索意图初判：
- 必须植入的产品/品牌/URL：
- 实际搜索查询：
- Google 域名/地区版本：
- Search Simulator 模拟地区/语言：
- 搜索日期：
- 搜索结果页可见地区：
- Chrome 登录状态（如可观察）：
- Search Simulator 使用证据：
- Google 前 10 个自然结果是否已采集：

Top 10 逐条记录：
- 自然排名：
- 页面标题：
- URL：
- 网站/品牌：
- 内容类型：
- 标题承诺：
- 主要 H2：
- 主要搜索意图：
- 内容深度：
- 特色信息：
- 明显缺口：
- FAQ/长尾问题：
- 是否成功打开正文：
- 无法访问的原因（如适用）：

横向结论：
- Top 10 主流内容形式：
- 高频 H2 主题：
- 重复出现的问题：
- 普遍遗漏的内容：
- 可尝试的独特价值点（如有）：
- 不值得跟随的结构：
- 正文成功访问数量：
- 无法访问的结果及原因：
- 研究完整度与限制：

请确认、修改，或告诉我继续进入 Step 2。

Step 2: Summarize Search Intent and Reader Needs

Explain in Chinese, from the searcher's perspective:

• The immediate answer expected near the top of the article.
• Information needed before the reader can complete the main task.
• Steps, evidence, or criteria needed to complete it.
• Risks, limitations, misconceptions, or obstacles.
• Follow-up questions likely to remain.
• Needs that belong in the main body versus search-backed FAQ candidates.
• Questions that should not be expanded because they are weak, irrelevant, or outside scope.

Checkpoint:

Step 2 搜索意图和读者需求
- 核心搜索意图：
- 读者最想快速得到的答案：
- 完成主要任务前必须理解的信息：
- 完成任务所需的步骤、证据或判断依据：
- 可能阻碍任务完成的限制、风险和误区：
- 文章必须覆盖的问题：
- 适合作为 FAQ 候选的长尾问题：
- 不建议写/不应展开的问题：

请确认、修改，或告诉我继续进入 Step 3。

Step 3: Decide Positioning and Title Direction

Determine the dominant intent and expected format from the Top 10. Treat definition, tutorial, troubleshooting, comparison, decision, list, review, data analysis, case study, and resource intent as diagnostic categories, not templates.

Before proposing titles:

1. Define the article's central question, actual scope, and most valuable reader outcome.
2. Analyze Top 10 title patterns, promises, modifiers, keyword placement, and unaddressed angles.
3. Follow valid format expectations without copying competitor wording.
4. Use a differentiating angle when it is useful and evidence-supported. Prefer to add one, but do not force one when no meaningful gap exists.

Every English title must:

• Contain the target keyword naturally. This is mandatory, not merely preferred.
• Contain no more than 15 English words.
• Use natural, industry-appropriate English and the correct English variant.
• Use consistent title capitalization; preserve official brand and product styling.
• Avoid spelling mistakes, grammar errors, rare vocabulary, long constructions, keyword stuffing, and awkward phrasing.
• Make a clear promise that the planned article can fully deliver.

Do not use “difference,” “how to choose,” “complete guide,” “review,” “tested,” or “latest” unless the body and evidence justify the promise. Do not mention FAQ merely because the article contains one.

Checkpoint:

Step 3 文章定位和标题方向
- 文章定位：
- 主要搜索意图：
- SERP 主流内容形式：
- SERP 标题共同模式：
- 可利用的标题差异点（如有）：
- 文章实际覆盖范围：
- 目标关键词：
- 推荐英文标题：
- 中文翻译：
- 英文标题词数：
- 备选英文标题及中文翻译：
- 推荐理由：
- 关键词是否自然包含：
- 拼写、语法、大小写和行业表达是否正确：
- 标题承诺是否都能由正文兑现：

请确认、修改，或告诉我继续进入 Step 4。

Step 4: Build the Bilingual H2 Outline

Cluster researched queries, recurring competitor sections, related searches, and reader questions by intent. Derive a topic-specific answer path rather than applying a standard article template.

Build the structure under these rules:

1. Cover important shared content found across the strongest Top 10 pages when it is necessary for the target intent.
2. Prefer at least one evidence-supported unique value point when a useful gap exists. Omit it when research reveals no meaningful differentiation; never manufacture one.
3. Order H2s so the reader can complete the primary task continuously and naturally.
4. Assign one core question cluster to each H2.
5. Merge overlapping H2s and demote narrow secondary needs to H3, paragraph, table, callout, or FAQ.
6. Use the fewest H2s that fully satisfy intent. Do not create boilerplate H2s for completeness.
7. Make every English H2 immediately understandable, specific, conversational, grammatically correct, and appropriate to the industry.
8. Keep every English H2 between 8 and 10 words. Do not add filler merely to reach the range; rewrite the heading naturally while preserving clarity.
9. Place the Chinese translation immediately below each English H2.
10. Avoid rare vocabulary, spelling errors, grammar errors, keyword stuffing, and long or difficult constructions.
11. Plan each H2 body section to contain at least roughly 80–100 English words. Let final length grow dynamically with intent, complexity, and needed explanation; never pad for length.
12. When detailed H3s are requested or genuinely needed, plan roughly 60–100 English words for each H3 body. Do not create H3s mechanically.
13. Plan at least one and no more than three useful tables in the article. Use a table only when it improves comparison, scanning, or visualization. State its intended location and contents in the relevant section note. Icons may be used sparingly when they help recognition and do not replace text.
14. For a normal long article, use approximately one bullet block per 350–400 words when the material benefits from scanning. Keep each block to 3–5 items. Use bullets for findings, methods, evidence, checks, conditions, risks, or comparison criteria, not as a mechanical readability device.
15. If important content uses data, require authoritative data and a descriptive anchor link to the original webpage. Do not add a general recommended-source section.

Run a compression and quality check:

• Can any two H2s be mistaken for covering the same content?
• Can any H2 be removed without blocking the reader's task?
• Should any H2 become an H3, paragraph, table, callout, or FAQ?
• Does the sequence form a complete answer path rather than a topic inventory?
• Does every H2 support the primary search intent?
• Are Top 10 common needs covered without copying competitor structure?
• Is any proposed unique value useful and evidence-supported?
• Does every English H2 contain 8–10 words and read naturally?
• Are tables and bullet blocks useful rather than forced?

Checkpoint:

Step 4 初版英文文章大纲
- 文章需要帮助读者完成的主要任务：
- 大纲采用的回答逻辑：
- Top 10 共性内容覆盖：
- 独特价值点及依据（如有）：
- 主体收尾方式及原因：
- 表格规划（1–3 个）：
- Bullet block 规划原则：
- FAQ 候选问题及来源：
- 与初版正文可能重叠的问题：

# English Article Title
# 中文标题翻译

## English H2 With Eight to Ten Clear Words
## 中文 H2 翻译
（用中文说明本节回答的问题、正文方向、表格或 bullet 规划，以及与全文的关系）

## English H2 With Eight to Ten Clear Words
## 中文 H2 翻译
（用中文说明本节回答的问题、正文方向、表格或 bullet 规划，以及与全文的关系）

## FAQ
## 常见问题
（列出有搜索依据的候选问题及来源；Step 6 完成最终去重和定稿）

请确认、修改，或告诉我继续进入 Step 5。

Step 5: Integrate Product or Brand Messaging

Always integrate the designated product or brand. Decide how it should function, not whether it should appear.

1. Define its role: core solution, comparison subject, task-enabling tool, scenario-specific option, advanced alternative, implementation example, supporting resource, or next step.
2. Identify the exact reader problem it solves and the first natural point where that need appears.
3. Choose placement dynamically: introduction, quick answer, relevant body section, procedure, table, scenario, case, limitation-to-solution transition, close, FAQ, or standalone H2.
4. Use a standalone H2 only when the product is part of the primary intent or needs substantial explanation.
5. Scale depth, frequency, wording, and conversion intensity to relevance.
6. Make every mention useful by explaining fit, function, added value, limitation, or next action.
7. Avoid repeated selling points, unsupported claims, artificial pain points, excessive brand repetition, abrupt sales copy, and landing-page behavior.

Checkpoint:

Step 5 产品或品牌植入方案
- 产品与主搜索意图的关系：
- 产品在文章中的角色：
- 产品解决的具体读者问题：
- 首次自然出现的位置：
- 其他必要出现位置：
- 是否需要独立 H2：
- 建议篇幅：
- 建议出现次数：
- 英文表述方式：
- 转化强度：
- 与前后内容的衔接方式：
- 如何避免破坏主要搜索意图：
- 需要避免的重复或宣传性表达：

请确认、修改，或告诉我继续进入 Step 6。

Step 6: Finalize the Close and FAQ

Combine the confirmed outline and product plan.

1. Finalize a main-body close before the FAQ that provides synthesis, direction, validation, risk guidance, a useful next step, or another topic-specific function.
2. Do not merely repeat earlier H2 content.
3. Keep any product appearance consistent with Step 5.
4. Re-evaluate every FAQ candidate against all H2s, H3s, tables, callouts, product integrations, and the close.
5. Keep a question only when it is relevant, search-backed or clearly useful, unsuitable for full body treatment, independently answerable, and semantically non-duplicative.
6. Remove questions whose answers are already substantially covered anywhere in the plan.
7. Because FAQ is mandatory, replace every removed weak or duplicate question with another qualified search-backed question.
8. Mention the product in FAQ only when genuine tool, product, or solution intent supports it.
9. Write each final English FAQ question naturally and place its Chinese translation on the next line.

Checkpoint:

Step 6 主体收尾与 FAQ 定稿

主体收尾：
- 收尾模块需要帮助读者完成什么：
- 采用的收尾方式：
- 为什么适合当前主题和搜索意图：
- 是否只是重复正文：
- 产品是否出现：
- 与 Step 5 是否一致：

FAQ：
- FAQ 候选问题及来源：
- 每个问题的搜索或读者价值：
- 为什么不适合在正文中展开：
- 是否与正文、收尾或其他 FAQ 语义重复：
- 删除或替换的问题：
- 产品是否需要在某个 FAQ 中出现及原因：
- 是否存在关键词堆砌或强行推广：
- 最终英文 FAQ 及中文翻译：

请确认、修改，或告诉我继续输出最终版大纲。

Step 7: Output the Final Outline

Use this structure:

# English Article Title
# 中文标题翻译

## English H2 With Eight to Ten Clear Words
## 中文 H2 翻译
（用中文简述本节回答的问题、主要内容和必要写作提示）
（表格/Bullet：如有，注明位置、作用和内容方向）
（数据引用：如有，注明只使用权威数据并链接原始网页）
（产品植入：如有，注明产品角色、位置和英文表达方式）

### English H3 When a Detailed Outline Needs One
### 中文 H3 翻译
（用中文简述写作方向；仅在详细版或确有必要时使用）

## Main-Body Close
## 正文收尾
（说明收尾目的、主要结论和产品是否出现）

## FAQ
## 常见问题

### English FAQ Question
### 中文问题翻译
（用中文注明问题来源和回答方向）

If the user asks for only the title and H2 outline, omit ordinary H3s, full paragraphs, and a general source list. Still retain concise Chinese section notes, confirmed product integrations, the main-body close, table planning, and the finalized FAQ. If the user requests a detailed outline, add only useful H3s and bullet-level writing notes.

Before delivery, verify:

• The English title contains the target keyword and has no more than 15 words.
• Every English H2 has 8–10 words.
• English spelling, grammar, capitalization, vocabulary, and industry phrasing are correct and natural.
• Every English heading or FAQ question is immediately followed by its Chinese translation.
• The outline covers necessary Top 10 common content without mechanical imitation.
• Any unique value point is useful and evidence-supported; its absence is allowed when no meaningful gap exists.
• The structure is complete, logically sequenced, and free of substantial repetition.
• The plan contains 1–3 useful tables and applies bullet blocks only where appropriate.
• Important data, when planned, requires authoritative data and an anchor link to the original webpage.
• Product integration is present and context-appropriate.
• The FAQ is present, search-backed, useful, and semantically non-duplicative.