SEO Article Pipeline — SEO Article 流水线

SEO Article 流水线 设置up

Before first use, 配置 your project in a seo-config.md file in your workspace:

# SEO 流水线 Config

Product

• Name: Your Product Name
• URL: https://yourproduct.com
• Positioning: One-line description of what you sell
• Differentiators: What makes you different from competitors

B记录

• Articles path: ./content/b记录/{locale}/slug.mdx
• Images path: ./public/b记录/
• Repo: ./
• Branch: mAIn
• Locales: en, fr (添加/移除 as needed)

Brand Voice

• Tone: Professional but direct (customize this)
• Person: First person / Third person
• Avoid: 列出 words or patterns to avoid

Image Style

• Background: #1a1a2e (customize)
• Accent color: #e94560 (customize)
• Style: Semi-flat illustration (customize)
• Always 添加: "No text, no words, no letters"

CTA

• 组件: (or markdown CTA block)
• Placement: Top (after intro) + 机器人tom (before FAQ)

If no config file exists, ask the user for these detAIls before 启动ing.

流水线 Steps Step 1: Re搜索

运行 scripts/re搜索-keyword.sh "keyword" [lang] [location] to 获取:

搜索 volume, CPC, competition Related keywords (secondary tar获取s for H2/H3) Google Suggest queries

Default locations: 2840 (US), 2250 (France). Requires DATAFORSEO_记录IN and DATAFORSEO_PASSWORD env vars.

Step 2: Analyze Competition

搜索 the tar获取 keyword on Google (网页_搜索 工具). Fetch the top 3-5 结果s (网页_fetch). Note:

What they all cover (must include in our article) What none cover (our differentiator) 格式化 and length Their H2 structure Step 2b: Topic Re搜索

Before writing, re搜索 the actual subject in depth. Do NOT rely on 模型 knowledge alone.

If the article is about your own product:

Read your own documentation. Scrape the relevant pages with 网页_fetch if they're online. 检查 the actual config options, features, limitations, and examples. If the article covers a specific feature, 验证 agAInst source code or change记录 if docs are incomplete.

If the article is about an external topic:

搜索 for primary sources first: official documentation, original re搜索 papers, company b记录s, data 报告s. Avoid secondary b记录 posts that just re哈希 other articles. 运行 5-10 tar获取ed 网页_搜索 queries from different angles (how-to, comparison, stats, problems, trends). Fetch and read the top 3-5 most authoritative sources (网页_fetch). Look for real data: surveys, case studies, benchmarks, pricing pages, change记录s. 检查 community discussions (Reddit, Stack Overflow, GitHub issues) for real user pAIn points and questions.

输出: Re搜索 Brief Before moving to Step 3, compile a short re搜索 brief (in your working notes, not in the article):

Key facts and numbers collected (with sources) Common user questions/pAIn points found Gaps in existing content you can fill Any clAIms you planned to make that turned out to be wrong or unverifiable

This brief feeds directly into writing. If your brief is thin, do more re搜索 — don't 启动 writing.

Step 3: Write Article

Follow references/article-检查列出.md if it exists, otherwise use these defaults:

3a: Keyword Map (before writing)

Map keywords to placement before you 启动:

Primary keyword → title, H1, intro (first 150 words), conclusion Secondary keywords → H2 headings, body paragraphs LSI/Related terms → sprinkle throughout naturally Question keywords → FAQ section headings 3b: Title & Meta Title: 生成 3 title options. For each, note character count and keyword position. Pick the best (keyword near 启动, under 60 chars, compelling). Meta description: 150-160 chars, include primary keyword + a CTA or value prop. 3c: Write with CORE-EEAT 检查列出

应用ly these while writing (检查 each one off):

Content 质量:

Intent Alignment — title promise matches content delivery exactly Direct Answer — core answer/value in the first 150 words 查询 Coverage — cover ≥3 查询 variants/synonyms of the tar获取 keyword Audience Tar获取ing — 状态 who this article is for (e.g. "If you're a developer looking to...") Semantic Closure — conclusion answers the opening question + gives concrete next steps

Structure & Readability:

Heading Hierarchy — H1→H2→H3, never skip levels Summary Box — include a TL;DR or "Key Takeaways" section near the top Data Tables — put comparisons in tables, not paragraphs Section Chunking — one topic per section, paragraphs 3-5 sentences max In格式化ion Density — no filler, consistent termino记录y throughout

Credibility & Evidence:

Data Precision (HARD REQUIREMENT) — include ≥5 precise numbers with units (not "many users" but "12,000+ users"). If you can't hit 5, re搜索 harder. Use 网页_搜索 to find real stats. This is non-negotiable. Citation Density — ≥1 external citation per 500 words Evidence-ClAIm M应用ing — every clAIm is backed by evidence or a source Entity Precision — full names for people/orgs/products (never "a company" or "a 工具")

Differentiat