seo-content-brief
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSEO Content Brief
SEO内容简报
Create data-driven content briefs via inference.sh CLI.
通过inference.sh CLI创建基于数据的内容简报。
Quick Start
快速开始
bash
curl -fsSL https://cli.inference.sh | sh && infsh loginbash
curl -fsSL https://cli.inference.sh | sh && infsh loginResearch target keyword
研究目标关键词
infsh app run tavily/search-assistant --input '{
"query": "best project management tools for small teams 2024"
}'
infsh app run tavily/search-assistant --input '{
"query": "best project management tools for small teams 2024"
}'
Analyze top-ranking content
分析排名靠前的内容
infsh app run exa/search --input '{
"query": "project management tools small teams comparison guide"
}'
undefinedinfsh app run exa/search --input '{
"query": "project management tools small teams comparison guide"
}'
undefinedContent Brief Template
内容简报模板
Every brief should answer these questions before writing begins:
markdown
undefined开始写作前,每份简报都应回答以下问题:
markdown
undefinedContent Brief: [Working Title]
内容简报: [暂定标题]
Target
目标
- Primary keyword: [exact keyword]
- Secondary keywords: [3-5 related terms]
- Search intent: [informational / commercial / transactional / navigational]
- Target word count: [X,XXX words]
- Target URL: /blog/[slug]
- 主关键词: [精准关键词]
- 次关键词: [3-5个相关术语]
- 搜索意图: [信息型 / 商业型 / 交易型 / 导航型]
- 目标字数: [X,XXX 字]
- 目标URL: /blog/[slug]
Search Intent Analysis
搜索意图分析
- What is the searcher trying to accomplish?
- What format do top results use? (listicle, guide, comparison, tutorial)
- What questions need answering?
- 用户想要达成什么目标?
- 排名靠前的结果采用了什么格式?(列表文、指南、对比文、教程)
- 需要回答哪些问题?
Outline
大纲
H1: [Title with primary keyword]
H2: [Section 1]
H3: [Subsection]
H2: [Section 2]
...
H1: [包含主关键词的标题]
H2: [章节1]
H3: [子章节]
H2: [章节2]
...
Competitors to Beat
需超越的竞争对手
- [URL] — [word count] — [what they do well] — [gap/weakness]
- [URL] — [word count] — [what they do well] — [gap/weakness]
- [URL] — [word count] — [what they do well] — [gap/weakness]
- [URL] — [字数] — [他们的优势] — [差距/不足]
- [URL] — [字数] — [他们的优势] — [差距/不足]
- [URL] — [字数] — [他们的优势] — [差距/不足]
Unique Angle
独特视角
What makes this piece different/better than what already ranks?
与已排名内容相比,本文的差异化优势是什么?
Internal Links
内部链接
- Link TO: [existing pages to link to from this article]
- Link FROM: [existing pages that should link to this new article]
undefined- 链向: [本文需链向的现有页面]
- 来自: [需链向本文的现有页面]
undefinedSearch Intent Types
搜索意图类型
| Intent | What Searcher Wants | Content Format | Example Query |
|---|---|---|---|
| Informational | Learn something | Guide, tutorial, explainer | "what is CI/CD" |
| Commercial | Compare before buying | Comparison, listicle, review | "best CI/CD tools 2024" |
| Transactional | Buy/sign up | Product page, pricing page | "GitHub Actions pricing" |
| Navigational | Find a specific page | — (don't target these) | "GitHub login" |
Match format to intent. If top 10 results are all listicles, write a listicle. If they're all tutorials, write a tutorial. Fighting the SERP format loses.
| 搜索意图 | 用户需求 | 内容格式 | 查询示例 |
|---|---|---|---|
| 信息型 | 学习知识 | 指南、教程、讲解文 | "what is CI/CD" |
| 商业型 | 对比后购买 | 对比文、列表文、评测 | "best CI/CD tools 2024" |
| 交易型 | 购买/注册 | 产品页、定价页 | "GitHub Actions pricing" |
| 导航型 | 查找特定页面 | —(无需针对此类) | "GitHub login" |
内容格式需匹配搜索意图。如果前10名结果均为列表文,那就写列表文;如果都是教程,那就写教程。违背SERP格式很难获得好排名。
SERP Analysis Process
SERP分析流程
bash
undefinedbash
undefinedStep 1: See what currently ranks
步骤1: 查看当前排名结果
infsh app run tavily/search-assistant --input '{
"query": "[your target keyword]"
}'
infsh app run tavily/search-assistant --input '{
"query": "[your target keyword]"
}'
Step 2: Analyze top-ranking content
步骤2: 分析排名靠前的内容
infsh app run tavily/extract --input '{
"urls": ["https://top-result-1.com/article", "https://top-result-2.com/article"]
}'
infsh app run tavily/extract --input '{
"urls": ["https://top-result-1.com/article", "https://top-result-2.com/article"]
}'
Step 3: Find related questions (People Also Ask)
步骤3: 查找相关问题(People Also Ask)
infsh app run tavily/search-assistant --input '{
"query": "[keyword] questions people ask FAQ"
}'
infsh app run tavily/search-assistant --input '{
"query": "[keyword] questions people ask FAQ"
}'
Step 4: Find content gaps
步骤4: 寻找内容差距
infsh app run exa/search --input '{
"query": "[keyword] [subtopic competitors miss]"
}'
undefinedinfsh app run exa/search --input '{
"query": "[keyword] [subtopic competitors miss]"
}'
undefinedWhat to Extract from Top Results
从排名靠前的结果中提取哪些信息
| Data Point | Why |
|---|---|
| Word count | Sets your minimum (match or exceed top 3) |
| Heading structure | Shows what Google considers complete coverage |
| Topics covered | Every topic they cover, you must cover |
| Topics missed | Your opportunity to be more comprehensive |
| Content format | Listicle, guide, tutorial, comparison |
| Media used | Images, videos, tables, infographics |
| Internal/external links | Reference quality signals |
| 数据项 | 原因 |
|---|---|
| 字数 | 设定最低标准(匹配或超越前三名) |
| 标题结构 | 显示谷歌认为的完整内容覆盖范围 |
| 涵盖主题 | 竞争对手覆盖的所有主题,你都必须覆盖 |
| 遗漏主题 | 你的内容可以更全面的机会 |
| 内容格式 | 列表文、指南、教程、对比文 |
| 使用的媒体 | 图片、视频、表格、信息图 |
| 内链/外链 | 参考质量信号 |
Keyword Research
关键词研究
Keyword Metrics
关键词指标
| Metric | What It Means | Target |
|---|---|---|
| Search volume | Monthly searches | Depends on niche (100+ for long-tail) |
| Keyword difficulty | Competition level | < 30 for new sites, < 50 for established |
| CPC | What advertisers pay | Higher CPC = more commercial value |
| Search intent | What users want | Must match your content type |
| 指标 | 含义 | 目标 |
|---|---|---|
| 搜索量 | 月搜索次数 | 取决于细分领域(长尾词需100+) |
| 关键词难度 | 竞争程度 | 新站<30,成熟站<50 |
| CPC | 广告主出价 | CPC越高,商业价值越高 |
| 搜索意图 | 用户需求 | 必须匹配你的内容类型 |
Finding Keywords
寻找关键词
bash
undefinedbash
undefinedSeed keyword research
种子关键词研究
infsh app run tavily/search-assistant --input '{
"query": "project management software long tail keywords related searches"
}'
infsh app run tavily/search-assistant --input '{
"query": "project management software long tail keywords related searches"
}'
Find question-based keywords
查找基于问题的关键词
infsh app run exa/search --input '{
"query": "questions about project management tools for startups"
}'
infsh app run exa/search --input '{
"query": "questions about project management tools for startups"
}'
Competitor keyword analysis
竞争对手关键词分析
infsh app run tavily/search-assistant --input '{
"query": "site:competitor.com/blog top performing pages topics"
}'
undefinedinfsh app run tavily/search-assistant --input '{
"query": "site:competitor.com/blog top performing pages topics"
}'
undefinedKeyword Clustering
关键词聚类
Group related keywords into one piece of content:
Primary: "best project management tools for small teams"
Cluster:
- "project management software small business"
- "project management tools comparison"
- "simple project management app"
- "project management for startups"
- "affordable project management software"One page per keyword cluster. Don't create separate pages for each variation — that's keyword cannibalization.
将相关关键词分组到单篇内容中:
主关键词: "best project management tools for small teams"
聚类:
- "project management software small business"
- "project management tools comparison"
- "simple project management app"
- "project management for startups"
- "affordable project management software"每个关键词聚类对应一个页面。不要为每个变体创建单独页面——这会导致关键词内耗。
Heading Structure
标题结构
Rules
规则
| Rule | Why |
|---|---|
| One H1 per page | SEO standard, contains primary keyword |
| H2s = main sections | Each should target a secondary keyword or question |
| H3s = subsections | Break up long H2 sections |
| Primary keyword in H1 | Direct ranking signal |
| Secondary keywords in H2s | Topical coverage signal |
| Question format for some H2s | Targets "People Also Ask" |
| Logical hierarchy | Never skip levels (H1 → H3 without H2) |
| 规则 | 原因 |
|---|---|
| 每页一个H1 | SEO标准,需包含主关键词 |
| H2为主要章节 | 每个H2应针对次关键词或问题 |
| H3为子章节 | 拆分较长的H2章节 |
| H1中包含主关键词 | 直接排名信号 |
| H2中包含次关键词 | 主题覆盖信号 |
| 部分H2采用问题格式 | 针对“People Also Ask” |
| 逻辑层级清晰 | 不要跳过层级(如H1直接到H3,中间无H2) |
Example Structure
示例结构
H1: Best Project Management Tools for Small Teams (2025)
H2: How We Evaluated These Tools
H2: Top 10 Project Management Tools Compared
H3: 1. Tool A — Best for [use case]
H3: 2. Tool B — Best for [use case]
...
H2: Feature Comparison Table
H2: How to Choose the Right Tool for Your Team
H3: Team Size Considerations
H3: Budget Considerations
H2: Frequently Asked Questions
H3: What is the easiest project management tool?
H3: Do small teams need project management software?
H2: ConclusionH1: 2025年小型团队最佳项目管理工具
H2: 我们如何评估这些工具
H2: 十大项目管理工具对比
H3: 1. 工具A — 最适合[使用场景]
H3: 2. 工具B — 最适合[使用场景]
...
H2: 功能对比表
H2: 如何为你的团队选择合适的工具
H3: 团队规模考量因素
H3: 预算考量因素
H2: 常见问题
H3: 最简单的项目管理工具是什么?
H3: 小型团队需要项目管理软件吗?
H2: 结论Word Count Targets
字数目标
| Content Type | Word Count | When |
|---|---|---|
| Short-form blog | 800-1,200 | News, updates, opinions |
| Standard blog | 1,500-2,000 | How-tos, tutorials |
| Long-form guide | 2,500-4,000 | Comprehensive guides, comparisons |
| Pillar content | 4,000-7,000 | Definitive guides, hub pages |
| Glossary/definition | 300-800 | Quick reference terms |
Rule: match or exceed the average word count of the top 3 ranking results. Don't pad — every word should add value.
| 内容类型 | 字数范围 | 适用场景 |
|---|---|---|
| 短篇博客 | 800-1200字 | 新闻、更新、观点文 |
| 标准博客 | 1500-2000字 | 操作指南、教程 |
| 长篇指南 | 2500-4000字 | 全面指南、对比文 |
| 支柱内容 | 4000-7000字 | 权威指南、枢纽页面 |
| 术语表/定义 | 300-800字 | 快速参考术语 |
规则:匹配或超越前三名排名结果的平均字数。不要凑字数——每个字都应具备价值。
On-Page SEO Checklist
页面内SEO检查清单
| Element | Rule |
|---|---|
| Title tag | Primary keyword + compelling hook, 50-60 characters |
| Meta description | Includes keyword, 150-160 characters, includes CTA |
| URL slug | Short, keyword-rich: |
| H1 | Primary keyword, matches search intent |
| First 100 words | Include primary keyword naturally |
| Image alt text | Descriptive, includes keyword where natural |
| Internal links | 3-5 links to related content |
| External links | 2-3 authoritative sources |
| Schema markup | FAQ, HowTo, or Article schema where applicable |
| 元素 | 规则 |
|---|---|
| 标题标签 | 包含主关键词+吸睛钩子,50-60字符 |
| 元描述 | 包含关键词,150-160字符,包含行动号召 |
| URL slug | 简短、含关键词: |
| H1 | 包含主关键词,匹配搜索意图 |
| 开头100字 | 自然融入主关键词 |
| 图片替代文本 | 描述性,自然融入关键词 |
| 内部链接 | 3-5个指向相关内容的链接 |
| 外部链接 | 2-3个权威来源链接 |
| Schema标记 | 适用时添加FAQ、HowTo或Article schema |
Content Differentiation
内容差异化
Unique Angles
独特视角
| Angle | Example |
|---|---|
| Original data | "We surveyed 500 PMs — here's what they use" |
| Expert quotes | Interview practitioners for original insights |
| Real examples | Screenshots, case studies, not just descriptions |
| More comprehensive | Cover subtopics competitors skip |
| More current | Updated data, newer tools, recent changes |
| Better visuals | Comparison tables, infographics, decision trees |
bash
undefined| 视角 | 示例 |
|---|---|
| 原创数据 | "我们调研了500位项目经理——以下是他们的选择" |
| 专家引用 | 采访从业者获取原创见解 |
| 真实案例 | 截图、案例研究,而非单纯描述 |
| 更全面覆盖 | 覆盖竞争对手遗漏的子主题 |
| 时效性更强 | 更新数据、新工具、近期变化 |
| 更优视觉效果 | 对比表、信息图、决策树 |
bash
undefinedGenerate comparison infographic
生成对比信息图
infsh app run infsh/html-to-image --input '{
"html": "<div style="width:1200px;height:800px;background:white;padding:40px;font-family:system-ui"><h2 style="font-size:28px;color:#1e293b;text-align:center;margin-bottom:30px">Project Management Tools Comparison</h2><table style="width:100%;border-collapse:collapse;font-size:16px"><tr style="background:#f1f5f9"><th style="padding:12px;text-align:left;border-bottom:2px solid #cbd5e1">Feature</th><th style="padding:12px;text-align:center;border-bottom:2px solid #cbd5e1">Tool A</th><th style="padding:12px;text-align:center;border-bottom:2px solid #cbd5e1">Tool B</th><th style="padding:12px;text-align:center;border-bottom:2px solid #cbd5e1">Tool C</th></tr><tr><td style="padding:12px;border-bottom:1px solid #e2e8f0">Free tier</td><td style="padding:12px;text-align:center;border-bottom:1px solid #e2e8f0">✅</td><td style="padding:12px;text-align:center;border-bottom:1px solid #e2e8f0">✅</td><td style="padding:12px;text-align:center;border-bottom:1px solid #e2e8f0">❌</td></tr></table></div>"
}'
undefinedinfsh app run infsh/html-to-image --input '{
"html": "<div style="width:1200px;height:800px;background:white;padding:40px;font-family:system-ui"><h2 style="font-size:28px;color:#1e293b;text-align:center;margin-bottom:30px">Project Management Tools Comparison</h2><table style="width:100%;border-collapse:collapse;font-size:16px"><tr style="background:#f1f5f9"><th style="padding:12px;text-align:left;border-bottom:2px solid #cbd5e1">Feature</th><th style="padding:12px;text-align:center;border-bottom:2px solid #cbd5e1">Tool A</th><th style="padding:12px;text-align:center;border-bottom:2px solid #cbd5e1">Tool B</th><th style="padding:12px;text-align:center;border-bottom:2px solid #cbd5e1">Tool C</th></tr><tr><td style="padding:12px;border-bottom:1px solid #e2e8f0">Free tier</td><td style="padding:12px;text-align:center;border-bottom:1px solid #e2e8f0">✅</td><td style="padding:12px;text-align:center;border-bottom:1px solid #e2e8f0">✅</td><td style="padding:12px;text-align:center;border-bottom:1px solid #e2e8f0">❌</td></tr></table></div>"
}'
undefinedInternal Linking Strategy
内部链接策略
| Type | Purpose |
|---|---|
| Hub → Spoke | Pillar page links to all subtopic articles |
| Spoke → Hub | Subtopic articles link back to pillar page |
| Spoke → Spoke | Related articles cross-link to each other |
| Contextual | Natural in-text links where topic is mentioned |
| 类型 | 目的 |
|---|---|
| 枢纽→分支 | 支柱页面链接至所有子主题文章 |
| 分支→枢纽 | 子主题文章链接回支柱页面 |
| 分支→分支 | 相关文章互相交叉链接 |
| 上下文链接 | 在主题提及处自然添加文中链接 |
Rules
规则
- 3-5 internal links minimum per article
- Anchor text should be descriptive (not "click here")
- Link to relevant pages, not random ones
- Update old articles to link to new ones
- Most important pages should have the most internal links
- 每篇文章至少3-5个内部链接
- 锚文本应具描述性(而非“点击此处”)
- 链接至相关页面,而非随机页面
- 更新旧文章以链接至新文章
- 最重要的页面应获得最多内部链接
Common Mistakes
常见错误
| Mistake | Problem | Fix |
|---|---|---|
| No SERP analysis | Writing blind, wrong format | Always analyze top 3-5 before writing |
| Wrong intent match | Guide when they want comparison, or vice versa | Match SERP format exactly |
| Keyword stuffing | Penalized, reads poorly | Use naturally, 1-2% density max |
| Ignoring "People Also Ask" | Missing easy ranking opportunities | Answer PAA questions in your content |
| Too short | Can't compete with comprehensive results | Match or exceed top 3 word count |
| No unique angle | Just another "me too" article | Original data, expert quotes, better visuals |
| Keyword cannibalization | Multiple pages competing | One page per keyword cluster |
| No internal links | Wasted link equity, poor site structure | 3-5 internal links per article |
| Missing meta description | Google generates one (often poorly) | Write compelling meta with keyword + CTA |
| 错误 | 问题 | 解决方法 |
|---|---|---|
| 未做SERP分析 | 盲目写作,格式错误 | 写作前务必分析前3-5名结果 |
| 意图匹配错误 | 用户需要对比文却写了指南,反之亦然 | 完全匹配SERP格式 |
| 关键词堆砌 | 被惩罚,可读性差 | 自然使用,密度不超过1-2% |
| 忽略“People Also Ask” | 错失轻松排名机会 | 在内容中回答PAA问题 |
| 内容过短 | 无法与全面的结果竞争 | 匹配或超越前三名的字数 |
| 无独特视角 | 只是又一篇“跟风”文章 | 原创数据、专家引用、更优视觉效果 |
| 关键词内耗 | 多个页面竞争同一关键词 | 每个关键词聚类对应一个页面 |
| 无内部链接 | 浪费链接权重,网站结构差 | 每篇文章添加3-5个内部链接 |
| 缺失元描述 | 谷歌自动生成(通常效果不佳) | 撰写包含关键词与行动号召的吸引人元描述 |
Related Skills
相关技能
bash
npx skills add inference-sh/skills@seo
npx skills add inference-sh/skills@technical-blog-writing
npx skills add inference-sh/skills@web-searchBrowse all apps:
infsh app listbash
npx skills add inference-sh/skills@seo
npx skills add inference-sh/skills@technical-blog-writing
npx skills add inference-sh/skills@web-search浏览所有应用:
infsh app list