# Chinese Article Body Writing

> Draft and revise Chinese SEO blog article body content from an approved outline. Use when the user asks to write, expand, optimize, or iterate a Chinese blog正文/正文草稿 based on a target keyword, search intent, SERP learnings, confirmed outline, FAQ/long-tail questions, product insertion needs, or asks to use “中文正文skill”.

- Skill: `linsiyan780-droid/chinese-article-body-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add linsiyan780-droid/chinese-article-body-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/linsiyan780-droid/chinese-article-body-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: linsiyan780-droid (https://skillmd.com/u/linsiyan780-droid)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/linsiyan780-droid/chinese-article-body-writing

---


# Chinese Article Body Writing

Use this skill to turn an approved Chinese SEO blog outline into a complete, practical, search-intent-matching article body. Prioritize reader usefulness, clear decision support, and natural Chinese expression over formulaic SEO writing.

## Core Workflow

1. Confirm the inputs already available: article title, target keyword, approved outline, target reader, product/brand insertion point, confirmed facts, SERP/search-intent notes, FAQ/long-tail questions, and any writing constraints.
2. Write from the reader's problem first. Start with a direct answer or decision shortcut when the query is comparison/choice-oriented.
3. Follow the approved outline, but merge or compress sections that repeat the same idea. Do not preserve a heading just because it appeared in the outline.
4. Cover the primary intent first, then secondary and latent intent: definitions, differences, limits, scenarios, risks, business choice, workflow, FAQ, and next steps.
5. Use tables, lists, flows, and image suggestions only when they improve scanning, understanding, or decision-making. Avoid turning every paragraph into bullets.
6. Insert product or brand content only where the reader's need naturally creates demand for the product capability.
7. After drafting, revise for repetition, stiff wording, hard-sell language, unsupported claims, keyword stuffing, and FAQ duplication.

## Structure Rules

- Use one H1 only: the article title.
- Use H2 for main sections.
- Use H3 only when a section has clear subtopics or practical steps.
- Do not make a standalone heading for a single emphasized sentence; bold it inside the paragraph instead.
- Keep the article long enough to satisfy intent, but not longer than the decision requires. For ordinary B2B/SEO blogs, prefer a focused medium-length draft over an oversized guide unless the keyword demands depth.
- If two adjacent sections repeat, merge them. For example, definitions can be folded into the conclusion-first intro when the concept is simple.

## Search Intent Coverage

When writing around a core keyword, include relevant variations naturally:

- Core keyword and close variants.
- Chinese and English product terms when readers may search both.
- Long-tail questions from PAA, related searches, autocomplete, competitor headings, and user-provided research.
- Business-intent terms only where relevant, such as pricing, limits, API, automation, CRM, software, tools, risks, compliance, and conversion.

Do not force every keyword into headings. Prefer natural body text when a phrase would make a heading awkward.

## Evidence And Source Handling

- Use confirmed facts from reliable sources. Do not invent platform limits, prices, policies, or statistics.
- For important numbers, limits, platform rules, policy statements, or data, cite an authoritative source with an anchor link when the final article format supports links.
- Avoid linking official help/policy pages if the user has asked to remove such links; in that case, use the information but omit the external URL or ask before including it.
- Competitor SERP content may inspire coverage and structure, but do not copy wording, tables, examples, or paragraph logic.

## Tables, Bullets, And Visual Formats

Use a table when comparing tools, plans, scenarios, features, pros/cons, or decision criteria. Keep tables compact and immediately useful.

Use bullet points for:

- TL;DR or key takeaways.
- Three or more parallel scenarios, risks, benefits, limits, or evaluation criteria.
- Sub-items inside steps.
- Scan-friendly data findings.

Avoid bullets when:

- Explaining a cause-and-effect chain.
- Telling a short example or business scenario.
- There are only one or two points.
- The whole article starts to feel like disconnected notes.

Use numbered steps for processes readers can follow. If a flow is central, express it as a simple chain such as:

`Step 1 -> Step 2 -> Step 3 -> Result`

## Image Suggestions

- Aim to include at least 1-2 high-value image suggestions in a complete article so the page is not only text and tables. Treat this as a default target, not a hard minimum or maximum.
- Add more suggestions when the article contains additional independent ideas that genuinely benefit from visualization. Do not cap the count at two, and do not add images merely to reach a quota.
- Prefer visuals that explain or demonstrate: comparison paths, decision trees, workflows, system relationships, scenarios, before/after states, dashboards, or essential interface screenshots.
- Do not suggest generic business stock photos, decorative illustrations, logo walls, or images that merely repeat nearby prose or a table.
- Keep tables as native text. Do not recommend turning a useful table into an image; pair it with a different visual only when that visual adds a new relationship or explanation.
- Place each suggestion exactly where the image should appear in the body, using this format:

  `[配图建议：图片类型；主要内容；帮助读者理解什么；Alt文本：……]`

- If no location is strictly necessary, still choose the single strongest visualization opportunity when one can add clear editorial value. If every possible image would be irrelevant or repetitive, omit the suggestion rather than forcing decoration.

## Product Insertion

When inserting SaleSmartly or another product, use this logic:

1. Identify the reader's operational problem.
2. Explain the capability needed to solve it.
3. Mention the product as one possible way to support that capability.
4. Show the workflow it enables.
5. Return to the article's main decision, not the product pitch.

Preferred tone:

- Natural: “这时，企业需要的就不只是 X，而是一套更完整的流程，可以借助 Y 这类工具……”
- Practical: describe tagging, segmentation, shared inbox, team assignment, AI/automation, tracking, follow-up, and conversion only when relevant.
- Balanced: make clear the product does not replace the original tools unless that is truly the case.

Avoid:

- “官网介绍其可……”
- “强大、领先、一站式、完美解决”等空泛夸法。
- Creating a separate product H2 unless the user explicitly wants a marketing section.
- Making the reader feel the article's purpose changed from solving the query to selling a tool.

## FAQ And Extended Reading

FAQ should answer questions readers may still have after reading the article. Do not repeat questions already fully answered in the body.

Good FAQ candidates:

- Adjacent long-tail searches.
- Safety, cost, account risk, missing feature, setup problems, alternatives, and next-step tool questions.
- Clarifications between similar concepts not deeply covered in the main body.

Extended reading should continue the reader's journey:

- Choose articles that are highly related.
- Prefer Chinese articles for Chinese blogs when the user specifies Chinese content.
- Use natural in-text anchor phrases, not awkward keyword blocks.
- If no exact anchor exists, suggest the smallest wording change that keeps the original meaning.

## Revision Checklist

Before final output, check:

- The first section answers the core query quickly.
- The article covers differences, scenarios, limits, risks, business choice, and next-step questions when relevant.
- Tables are useful and not excessive.
- Bullets serve scanning, evidence, or method.
- The draft includes 1-2 high-value image suggestions by default, or more when distinct visual needs justify them; every suggestion is placed at the relevant location and adds information rather than decoration.
- Product insertion follows a real reader need and does not sound forced.
- FAQ does not duplicate the main body.
- Wording sounds like professional Chinese business writing, not translated English or AI filler.
- The article has no unsupported claims, fake sources, or copied SERP wording.