关于 ai-search-optimization
ai-search-optimization 是介绍答案引擎优化和生成式引擎优化的内容策略技能,帮助内容团队调整页面结构与标记,以便 AI 搜索结果提取和引用内容。
主要功能
- 01AEO 与 GEO 基础
- 02语义化标题结构
- 03直接回答式内容模式
- 04结构化列表和表格
- 05Schema 标记指南
适用场景
- 01优化页面以争取 AI 答案引用
- 02重组文章以便提取答案
- 03为网站内容添加 Schema 标记
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ dirnbauer/ webconsulting-skills --skill ai-search-optimization安装后在 Claude Code 中输入/ai-search-optimization确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
SKILL-MEASUREMENT.mdreferences/04-e-e-a-t-signals-for-ai-trust.md05-content-freshness-strategy.md06-robots-txt-for-ai-crawlers.md07-conversational-query-optimization.md08-multimedia-optimization.md09-monitoring-ai-search-visibility.md10-ai-search-optimization-checklist.md11-platform-specific-optimization.md12-future-proofing-your-ai-search-strategy.md13-5-author-bio-schema-for-e-e-a-t.md13-typo3-implementation-guide.md14-markdown-and-mdx-implementation.md15-llms-txt-llm-site-index.mdcredits-and-attribution.mdfull-guide.mdresources-and-references.md详细介绍
AI 搜索优化(AEO 与 GEO)
范围: 针对 AI 驱动的搜索引擎和答案引擎优化内容 此技能介绍如何提升内容在 ChatGPT、Perplexity、Google AI Overviews、Microsoft Copilot 及其他生成式 AI 平台上的可见度。
1. 了解 AEO 与 GEO
什么是 AEO(答案引擎优化)?
答案引擎优化侧重于构建内容,为用户查询提供直接、简洁的答案,以适配 AI 驱动的平台。传统 SEO 的目标是获得链接点击,而 AEO 的目标是让内容被引用为答案来源。
目标平台:
- Google AI Overviews(原 SGE)
- Perplexity AI
- ChatGPT Search
- Microsoft Copilot Search
- 语音助手(Siri、Alexa、Google Assistant)
什么是 GEO(生成式引擎优化)?
生成式引擎优化是一项更广泛的工作,旨在提升内容在AI 生成的搜索结果中的可见度。它面向从多个来源综合生成答案的生成式引擎,而非呈现传统的链接列表。
与传统 SEO 的主要区别:
| 方面 | 传统 SEO | AEO/GEO |
|---|---|---|
| 目标 | 在 SERP 中获得排名 | 被 AI 答案引用 |
| 用户行为 | 点击进入网站 | 直接获取答案 |
| 内容格式 | 针对关键词优化的页面 | 结构化、可引用的内容 |
| 成功指标 | 点击率 | 引用频率 |
| 查询类型 | 短关键词 | 对话式长尾查询 |
AI 搜索格局(2025-2026)
- Google AI Overviews: 在 200 个国家/地区拥有每月超过 20 亿用户(TechCrunch)
- Google AI Mode: 在美国和印度拥有每月超过 1 亿用户
- ChatGPT Search: 提供实时网页搜索和引用
- Perplexity AI: 实时引用引擎,注重新鲜度
- Microsoft Copilot Search: 将 Bing 与生成式 AI 集成
- 零点击搜索: 全球约 60% 的搜索以用户未点击任何链接告终(neotype.ai)
2. 面向 AI 可读性的内容结构
语义 HTML 结构
AI 系统能更有效地从结构良好的内容中提取信息:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Descriptive, Question-Answering Title</title>
</head>
<body>
<article>
<header>
<h1>Primary Topic as Question or Clear Statement</h1>
<p class="summary">Direct 2-3 sentence answer to the main question.</p>
</header>
<main>
<section>
<h2>Subtopic Heading</h2>
<p>Detailed explanation with facts and data.</p>
<ul>
<li>Key point 1 with specific information</li>
<li>Key point 2 with verifiable data</li>
<li>Key point 3 with actionable insight</li>
</ul>
</section>
</main>
<aside>
<h3>Quick Facts</h3>
<dl>
<dt>Term</dt>
<dd>Definition</dd>
</dl>
</aside>
</article>
</body>
</html>
标题层级最佳实践
# H1: Main Topic (contains primary question/keyword)
└── ## H2: Major subtopic
└── ### H3: Specific aspect
└── #### H4: Details (use sparingly)
规则:
- 每个页面只使用一个 H1
- H1 应回答“此页面的主题是什么?”
- 适当使用问句形式的标题
- 自然融入目标关键词
倒金字塔模式
构建内容以便 AI 提取:
┌─────────────────────────────────────┐
│ DIRECT ANSWER (First 1-2 │ ← AI extracts this
│ sentences answer the query) │
├─────────────────────────────────────┤
│ KEY FACTS & CONTEXT │ ← Supporting evidence
│ (Bullet points, data, quotes) │
├─────────────────────────────────────┤
│ DETAILED EXPLANATION │ ← Comprehensive coverage
│ (Background, methodology, │
│ examples, case studies) │
├─────────────────────────────────────┤
│ RELATED TOPICS │ ← Topic authority signals
│ (Links to related content) │
└─────────────────────────────────────┘
便于提取的列表和表格
AI 引擎更偏好结构化数据格式:
<table>
<caption>Feature Comparison: Product A vs Product B</caption>
<thead>
<tr>
<th>Feature</th>
<th>Product A</th>
<th>Product B</th>
</tr>
</thead>
<tbody>
<tr>
<td>Price</td>
<td>$99/month</td>
<td>$149/month</td>
</tr>
</tbody>
</table>
<dl>
<dt>AEO</dt>
<dd>Answer Engine Optimization - optimizing content for direct answers</dd>
<dt>GEO</dt>
<dd>Generative Engine Optimization - visibility in AI-generated results</dd>
</dl>
<ol>
<li>Step one with clear action</li>
<li>Step two with measurable outcome</li>
<li>Step three with verification method</li>
</ol>
3. 帮助 AI 理解的 Schema 标记
必备 Schema 类型
研究表明,结构化数据能显著提升内容在 AI 搜索中的可见度:
- 结构化数据有助于机器解析和理解内容;但请注意,Google 文档指出,Schema 标记不会提升内容被纳入 AI Overviews 的机会
- Organization Schema: 引用频率提升 2.8 倍
- FAQPage Schema: 答案收录率提升 2.5 倍
- Article Schema: 内容引用量提升 2.2 倍
- 使用 15 种以上 Schema 类型的网站,引用率高出 2.4 倍(surgeboom.com)
FAQPage Schema
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Answer Engine Optimization?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Answer Engine Optimization (AEO) is a strategic approach to structuring content so AI platforms like ChatGPT, Perplexity, and Google AI Overviews can easily extract and cite it as direct answers to user queries."
}
},
{
"@type": "Question",
"name": "How is AEO different from SEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "While SEO focuses on ranking in traditional search results for clicks, AEO optimizes content to be cited directly in AI-generated answers, often resulting in zero-click interactions where users get information without visiting the source."
}
}
]
}
HowTo Schema
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Optimize Content for AI Search",
"description": "Step-by-step guide to improving visibility in AI-powered search engines",
"totalTime": "PT30M",
"step": [
{
"@type": "HowToStep",
"name": "Structure Content Semantically",
"text": "Use proper HTML5 semantic elements like article, section, and aside",
"position": 1
},
{
"@type": "HowToStep",
"name": "Implement Schema Markup",
"text": "Add FAQPage, HowTo, and Article schema to your pages",
"position": 2
},
{
"@type": "HowToStep",
"name": "Optimize for Conversational Queries",
"text": "Write content that answers natural language questions",
"position": 3
}
]
}
含作者信息的 Article Schema
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Complete Guide to AI Search Optimization",
"description": "Learn how to optimize content for ChatGPT, Perplexity, and Google AI Overviews",
"datePublished": "2025-01-15",
"dateModified": "2025-01-15",
"author": {
"@type": "Person",
"name": "Expert Name",
"url": "https://example.com/about/expert-name",
"jobTitle": "SEO Specialist",
"sameAs": [
"https://linkedin.com/in/expertname",
"https://twitter.com/expertname"
]
},
"publisher": {
"@type": "Organization",
"name": "Company Name",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
}
}
Organization Schema
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Company Name",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"description": "Brief description of what the organization does",
"foundingDate": "2010",
"sameAs": [
"https://www.linkedin.com/company/companyname",
"https://twitter.com/companyname",
"https://github.com/companyname"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-555-123-4567",
"contactType": "customer service",
"availableLanguage": ["English", "German"]
}
}
详细参考
如果任务需要详细示例、较长模板、故障排查矩阵、附录或上文未包含的章节,请阅读完整指南。对于范围较窄的任务,请勿加载此文件,以便技能遵循渐进式披露。
评论
支持 Markdown