geo-aeo-optimization

GEO 与 AEO 优化框架

提升内容在 AI 驱动的搜索引擎和生成式 AI 回复中的可见度的专业方法。

了解 GEO、AEO 与 SEO

SEO  → Rank in traditional search results (blue links)
AEO  → Appear in featured snippets, AI Overviews, voice answers
GEO  → Get cited in generative AI responses (ChatGPT, Claude, Perplexity)

2025 年现状：

• 58% 的查询采用对话形式
• Google 搜索中约 47% 会显示 AI 概览
• 由于 AI 答案，传统搜索结果中排名靠前的结果点击率下降了 34.5%
• 这些策略相辅相成，并非相互竞争

何时使用此技能

• 为 AI 搜索引擎优化内容
• 提高精选摘要的获取率
• 审核内容是否符合 AI 引用要求
• 重构内容，使其更易于 AI 提取
• 实施 E-E-A-T 信号
• 为语音搜索做好准备

三重威胁框架

1. E-E-A-T 基础（必需）

AI 系统优先选择可信且权威的来源：

Experience   → First-hand knowledge, case studies, original research
Expertise    → Credentials, depth of knowledge, technical accuracy
Authority    → Citations, backlinks, mentions, brand recognition
Trustworthiness → Accuracy, transparency, clear sourcing

实施检查清单：

□ Author bio with credentials on every article
□ Link to authoritative sources
□ Include original data/research
□ Show methodology and sources
□ Update content regularly with visible dates
□ Display contact information
□ Include editorial guidelines

2. AEO：精选摘要与 AI 概览

开篇直接给出答案：

• 前 40-60 个字应直接回答查询
• 使用疑问句形式的 H2 标题
• 提供简洁、易于提取的定义

AEO 内容结构：

## What is [Topic]?

[Direct answer in 1-2 sentences that can be extracted as a snippet]

[Supporting details and context follow]

针对摘要优化的格式：

查询类型	最佳格式
“什么是 X？”	定义段落（40-60 个字）
“如何做 X”	编号步骤（5-8 步）
“最佳 X”	附带简短说明的项目符号列表
“X 与 Y 的对比”	对比表格
“为什么选择 X？”	直接回答 + 解释

3. GEO：AI 引用优化

CRASP 框架：

C - Clarity    → Unambiguous statements AI can quote
R - Relevance  → Match conversational query intent
A - Authority  → Cited sources, expert credentials
S - Structure  → Scannable, extractable format
P - Precision  → Specific facts, numbers, dates

有助于获得引用的内容元素：

1. TL;DR 摘要块，置于顶部
2. 附带来源的统计数据（“根据 [来源]，X 增长了 Y%”）
3. 注明出处的专家引言
4. 关键术语的定义列表
5. 数据清晰的对比表格
6. 包含完整答案的常见问题解答部分

内容结构模板

# [H1: Primary Question or Topic]

**TL;DR:** [2-3 sentence summary with key facts]

## What is [Topic]? {#definition}

[Direct definition in 40-60 words - optimized for extraction]

[Expanded explanation with context]

## How [Topic] Works {#how-it-works}

[Step-by-step explanation]

1. **Step One**: [Description]
2. **Step Two**: [Description]
3. **Step Three**: [Description]

## Key Statistics

| Metric | Value | Source |
|--------|-------|--------|
| [Stat 1] | [Value] | [Source, Year] |
| [Stat 2] | [Value] | [Source, Year] |

## [Topic] vs [Alternative]

| Factor | [Topic] | [Alternative] |
|--------|---------|---------------|
| [Factor 1] | [Value] | [Value] |
| [Factor 2] | [Value] | [Value] |

## Frequently Asked Questions

### [Question 1]?

[Complete, standalone answer - 50-100 words]

### [Question 2]?

[Complete, standalone answer - 50-100 words]

## Expert Insights

> "[Quotable statement with specific insight]"
> — [Expert Name], [Title], [Organization]

---
*Last updated: [Date] | Author: [Name], [Credentials]*

事实密度检查清单

Extractability:
□ TL;DR or summary present at top
□ Paragraphs <120 words each
□ Clear topic sentences (first sentence = main point)
□ Bullet lists for features/benefits
□ Tables for comparisons
□ FAQ section with schema

Fact-Density:
□ Statistics with sources cited
□ Specific numbers and dates
□ Verifiable data points
□ Expert quotes with attribution
□ Original research/data
□ Named entities (people, companies, places)

Structure for AI:
□ Question-based H2 headers
□ Direct answers in first 40-60 words
□ Logical information hierarchy
□ Schema markup (FAQPage, HowTo, Article)

AI 爬虫配置

用于提升 AI 搜索可见度的 robots.txt：

# ALLOW search/chat features
User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

# OPTIONAL: Block training (keeps search)
User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

重要： 确保使用服务器端渲染。AI 爬虫通常无法很好地执行 JavaScript。

面向 AI 的 Schema 标记

优先使用的 Schema 类型：

1. FAQPage - 对 AI 引用影响最大
2. HowTo - 提升分步骤内容的可见度
3. Article + Author - E-E-A-T 信号
4. Organization - 品牌权威性

FAQPage 示例：

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What is [topic]?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "[Complete answer that can be extracted]"
    }
  }]
}

输出格式

# GEO/AEO Audit Report

**Page:** [URL]
**Date:** [Date]
**Overall Score:** X/100

## Executive Summary
[2-3 sentence AI search readiness assessment]

## Scores by Category

| Category | Score | Status |
|----------|-------|--------|
| E-E-A-T Signals | X/25 | [Good/Needs Work/Critical] |
| Content Structure | X/20 | [Good/Needs Work/Critical] |
| Fact-Density | X/20 | [Good/Needs Work/Critical] |
| Extractability | X/20 | [Good/Needs Work/Critical] |
| AI Technical Readiness | X/15 | [Good/Needs Work/Critical] |

## Priority Issues
1. **[Issue]** - [Impact] - [Fix]
2. **[Issue]** - [Impact] - [Fix]
3. **[Issue]** - [Impact] - [Fix]

## AI Visibility Assessment
[Current citation probability and gaps]

## Action Plan

**Immediate:**
- [ ] Add TL;DR to top articles
- [ ] Implement FAQ schema

**Short-term:**
- [ ] Restructure headers as questions
- [ ] Add author credentials

**Ongoing:**
- [ ] Monitor AI platform citations
- [ ] Update content freshness

快速审核（5 点检查）

1. TL;DR - 顶部是否有摘要？
2. 结构 - 标题是否采用疑问句形式？
3. 事实 - 统计数据是否注明来源？
4. E-E-A-T - 作者资历是否清晰可见？
5. Schema - 是否包含 FAQPage/HowTo 标记？

评分指南

• 90-100： 优秀 - 获得 AI 引用的概率高
• 70-89： 良好 - 稍作改进后很可能获得引用
• 50-69： 有待改进 - 需要进行大量优化
• 低于 50： 严重不足 - 需要进行重大重构