bencium-aeo
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAEO Content Optimization Skill
AEO内容优化技能
Answer Engine Optimization - Optimize content for AI citations, not traditional search rankings.
Answer Engine Optimization(答案引擎优化)——针对AI引用优化内容,而非传统搜索排名。
When to Use This Skill
适用场景
Use this skill when:
- User asks to optimize content for AI search/citations
- User mentions ChatGPT, Claude, Gemini visibility
- User wants FAQ schema, JSON-LD, or structured data for AI
- User asks about GEO (Generative Engine Optimization)
- User wants to analyze content for AI extraction readiness
- User mentions "AI Overviews" or "answer engines"
NOT for traditional SEO - This is specifically for AI/LLM citation optimization.
在以下场景中使用此技能:
- 用户要求为AI搜索/引用优化内容
- 用户提及ChatGPT、Claude、Gemini的可见性提升
- 用户需要为AI场景创建FAQ Schema、JSON-LD或结构化数据
- 用户询问GEO(生成式引擎优化)相关内容
- 用户希望分析内容是否具备LLM提取适配性
- 用户提及“AI概览”或“答案引擎”
不适用于传统SEO——此技能专门针对AI/LLM引用优化。
Core Reference
核心参考
Full templates and guidelines: Read in this directory for complete implementation details.
prd.md完整模板与指南: 阅读当前目录下的文件获取完整实现细节。
prd.mdQuick Reference: Key Principles
快速参考:核心原则
The 18-Token Extraction Rule
18令牌提取规则
LLMs extract self-contained sentences of ~18 tokens (~15-20 words). Key claims must be complete, quotable statements requiring zero surrounding context.
Good: "Eight-API synthesis reduces property analysis errors by 67%." (9 tokens)
Bad: "Our system is incredibly fast and delivers amazing results." (vague)
LLMs会提取约18个令牌(约15-20个单词)的独立完整句子。核心主张必须是无需上下文即可理解的完整、可引用语句。
优秀示例: "八API合成将属性分析错误率降低67%。"(9个令牌)
糟糕示例: "我们的系统速度极快,能带来出色的结果。"(表述模糊)
Single-Topic Focus Pages
单主题聚焦页面
Single-concept pages vastly outperform multi-topic content. Create focused URLs like rather than comprehensive guides.
domain.com/specific-concept单概念页面的表现远超多主题内容。创建如这类聚焦式URL,而非综合性指南。
domain.com/specific-conceptCitations + Statistics = 30-40% More Visibility
引用+数据统计=提升30-40%可见性
Every major claim needs:
- Verifiable data with methodology
- Date of data collection
- Expert attribution (Name + Credentials + Org)
每个核心主张都需要:
- 可验证的数据及研究方法
- 数据收集日期
- 专家署名(姓名+资质+所属机构)
Freshness is Critical
时效性至关重要
95% of AI citations come from content updated in last 10 months. Static content dies.
95%的AI引用来自过去10个月内更新的内容。静态内容会被淘汰。
Authority Level Determines Strategy
权威等级决定策略
| Authority Level | Optimization Approach |
|---|---|
| Challenger (new sites, low authority) | Aggressive: 5-7 extraction points per page, heavy citations, weekly micro-updates |
| Established (top-ranked, well-known) | Light touch: 1-2 strategic points, trust existing credibility, avoid over-optimization |
Princeton finding: Rank-5 sites gained 115% visibility with aggressive optimization. Rank-1 sites that over-optimized lost 30%.
| 权威等级 | 优化策略 |
|---|---|
| 挑战者(新站点,低权威) | 激进策略:每页设置5-7个提取点,大量引用,每周进行微更新 |
| 已建立权威(排名靠前,知名度高) | 轻量优化:每页设置1-2个关键提取点,依托现有可信度,避免过度优化 |
普林斯顿研究发现: 排名第5的站点通过激进优化获得了115%的可见性提升。而过度优化的排名第1站点则损失了30%的可见性。
What to Generate
生成内容类型
When user requests AEO content, generate:
当用户请求AEO内容时,需生成以下内容:
1. Product Overview (50 words)
1. 产品概述(50词左右)
- What it is (one clause)
- Scope/timeframe context
- Why it matters (value proposition)
- "Last updated" date
- 产品定义(单句)
- 适用范围/时间背景
- 核心价值(为何重要)
- “最后更新”日期
2. 15 FAQs with Schema
2. 带Schema的15个常见问题(FAQ)
- Questions: 7-12 words, natural language
- Answers: 30-50 words (sweet spot for AI extraction)
- FAQPage JSON-LD schema with and
datePublisheddateModified - Persistent anchor IDs (#faq-slug)
- 问题:7-12词,自然表述
- 答案:30-50词(AI提取的最佳长度)
- 包含和
datePublished的FAQPage JSON-LD SchemadateModified - 持久锚点ID(#faq-slug)
3. Evidence Panels
3. 证据面板
For every important claim:
- Claim statement
- Methodology
- Data source + URL
- Date of data collection
- Limitations
- Contact for questions
针对每个重要主张:
- 主张陈述
- 研究方法
- 数据源+URL
- 数据收集日期
- 局限性说明
- 咨询联系方式
4. JSON-LD Schema
4. JSON-LD Schema
- FAQPage (most important)
- HowTo (for guides)
- Product (for product pages)
- Organization (for About page)
- FAQPage(最重要)
- HowTo(适用于指南类内容)
- Product(适用于产品页面)
- Organization(适用于关于我们页面)
Anti-Patterns (What to Avoid)
反模式(需避免)
Traditional SEO Tactics Harm GEO
传统SEO策略会损害GEO效果
- Keyword stuffing
- Generic listicles without original insight
- Vague hedged language ("may help", "could potentially")
- Multi-topic comprehensive guides
- Over-optimization on established sites
- 关键词堆砌
- 无原创见解的通用列表文
- 模糊的不确定表述(“可能有帮助”、“或许潜在有效”)
- 多主题综合性指南
- 对已建立权威的站点过度优化
Content Structure Errors
内容结构错误
- FAQ answers over 50 words
- Buried answers (put conclusion first)
- Pronoun ambiguity ("it" instead of "the product")
- Missing dates and freshness signals
- No schema markup
- FAQ答案超过50词
- 结论后置(应将结论放在开头)
- 指代模糊(用“它”代替“该产品”)
- 缺失日期及时效性标识
- 未添加Schema标记
Assessment Framework
评估框架
When analyzing content for AEO readiness, score (0-10):
| Dimension | What to Check |
|---|---|
| Extraction | How many citation-ready sentences under 18 tokens? |
| Focus | Single topic or sprawling multi-topic? |
| Authority | Expert attribution with credentials? Citations? |
| Freshness | Updated within 90 days? Dated content? |
Quick test: Can you copy-paste 3 sentences that fully answer a question without context?
分析内容的AEO适配性时,按0-10分评分:
| 评估维度 | 检查要点 |
|---|---|
| 可提取性 | 页面中有多少个18令牌以内、可直接引用的句子? |
| 聚焦性 | 单主题还是多主题分散内容? |
| 权威性 | 是否有带资质的专家署名?是否有引用? |
| 时效性 | 是否在过去90天内更新?内容是否有明确日期? |
快速测试: 能否直接复制3个无需上下文即可完整回答问题的句子?
Implementation Checklist
实施检查清单
- Product overview: 50 words, dated, under H1
- 15 FAQs: 30-50 words each, natural questions
- Evidence panels: method, data, date, limitations
- "Last updated" dates on every section
- FAQPage JSON-LD schema in
<head> - Persistent anchor IDs for FAQs
- Validated with Google Rich Results Test
- 产品概述:50词左右,带日期,位于H1标题下方
- 15个FAQ:每个答案30-50词,表述自然
- 证据面板:包含方法、数据、日期、局限性
- 每个板块都有“最后更新”日期
- 中添加FAQPage JSON-LD Schema
<head> - 为FAQ设置持久锚点ID
- 通过Google富媒体结果测试验证
Testing Protocol
测试流程
After implementation, test with:
- Recognition: "What is [Product]?" (ChatGPT, Claude, Gemini)
- Comparison: "Compare [Product] to [Competitor]"
- Best for: "What's the best [category] for [use case]?"
- How-to: "How do I [task with product]?"
Track: Mentioned? Linked? Accurate? Evidence quoted?
实施完成后,通过以下方式测试:
- 识别测试: “[产品名称]是什么?”(在ChatGPT、Claude、Gemini中测试)
- 对比测试: “将[产品名称]与[竞品名称]对比”
- 适配场景测试: “针对[使用场景],最佳的[品类]是什么?”
- 操作指南测试: “如何使用[产品]完成[任务]?”
跟踪指标: 是否被提及?是否被链接?信息是否准确?证据是否被引用?
Full Documentation
完整文档
For complete templates, examples, and detailed guidelines, read:
- - Full AEO content generation guide with HTML templates
prd.md - - Framework summary from Princeton study
story-structured.md
如需完整模板、示例及详细指南,请阅读:
- - 包含HTML模板的完整AEO内容生成指南
prd.md - - 普林斯顿研究总结的框架摘要
story-structured.md