AI引擎优化(AEO)指南：提升品牌在ChatGPT、Claude等AI答案中的引用率

aeo-optimization by alinaqi/claude-bootstrap

189 周安装量

570 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/alinaqi/claude-bootstrap --skill aeo-optimization

AI/机器学习内容创作 SEO

🇨🇳中文介绍

AI Engine Optimization (AEO) 技能

加载方式：base.md + web-content.md + site-architecture.md

目的： 针对 AI 引擎（ChatGPT、Claude、Perplexity、Google AI Overviews）优化内容，以便您的品牌在 AI 生成的答案中被引用。

来源： 基于 HubSpot 的 AEO 指南和行业最佳实践。

为何 AEO 现在很重要

┌────────────────────────────────────────────────────────────────┐
│  THE GREAT DECOUPLING                                          │
│  ────────────────────────────────────────────────────────────  │
│  Impressions ≠ Clicks anymore.                                 │
│  AI engines compile answers from multiple sources.             │
│  More buyer journey happens inside chat experiences.           │
│  58% of Google searches = zero clicks (AI overviews).          │
├────────────────────────────────────────────────────────────────┤
│  THE OPPORTUNITY                                               │
│  ────────────────────────────────────────────────────────────  │
│  Shape what AI engines say about your category and product.    │
│  Get cited as the authoritative source.                        │
│  Best answer > Best page ranking.                              │
└────────────────────────────────────────────────────────────────┘

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

AI 引擎如何选择答案

AI 引擎使用三个主要信号来选择用于答案的内容：

在多个可信来源中出现的事实会获得信任并被重复使用。

如何建立共识：

在您自己的页面中一致地重复关键事实
使用与行业领导者相同的术语
链接到权威的外部来源并从中获得链接
创建相互强化的内部内容集群

全新的洞察力胜过通用建议。AI 引擎更喜欢能增加价值的内容。

如何增加信息增益：

原创研究和数据
包含具体细节的实例
明确的观点（不模棱两可）
带有资历的专家引述
包含指标的案例研究

清晰的实体和整洁的结构可以减少歧义并提高可引用性。

如何优化结构：

使用语义三元组（主语 → 谓语 → 宾语）
使用带有实体名称的清晰标题
Schema 标记（Article、FAQ、Product）
简短、可快速浏览的段落（2-4 句话）

语义三元组（对 AEO 至关重要）

定义： 简洁明了的事实，AI 引擎（和人类）不会误解。

模式： [主语] [谓语] [宾语]。

✅ GOOD (clear triples):
- HubSpot CRM syncs contact and company data.
- Lead Scoring assigns priority based on engagement.
- Workflows trigger email sequences from events.

❌ BAD (vague, no clear entity):
- The system helps with various tasks.
- It can do many things for users.
- This improves overall performance.

三元组检查清单

对于每个关键主张，请询问：

主语是否是清晰的实体（产品、功能、品牌）？
谓语是否具体且主动？
宾语是否具体且可衡量？

段落模式（功能 → 方式 → 结果）

每个实质性段落都应遵循此结构：

[Feature] helps [User/Role] with [Job].
It [mechanism/inputs] to [process].
Teams see [metric/result] in [timeframe/context].

Triples:
- [Subject] [verb] [object].
- [Subject] [verb] [object].

Lead Scoring helps sales teams prioritize prospects. It combines
page views, email engagement, and firmographic data to assign a
numeric score, then auto-enrolls high scorers into follow-up
sequences. Reps focus on qualified accounts and book 40% more
meetings.

- Lead Scoring assigns scores from engagement data.
- High scorers trigger automated follow-up sequences.

模板 1：类别解释页面

目标： 定义类别，将其与您的产品联系起来，获得引用。

# What is [Category]? — [1-2 line value promise]

## What is [Category]? (~80 words)
[Plain definition in everyday language. Name adjacent entities.]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## Why it matters now (~60 words)
[One paragraph. Mention shift to answers over links; tie to buyer outcomes.]

## How to apply it (3-5 bullets)
- [Action 1]
- [Action 2]
- [Action 3]

## FAQ
**Q: [Question]?**
A: [~1 sentence answer]

**Q: [Question]?**
A: [~1 sentence answer]

**Q: [Question]?**
A: [~1 sentence answer]

---
**Links:** [Category hub] | [Product/Feature] | [Credible source 1] | [Credible source 2]
**CTA:** [Demo / Template / Signup]
**Schema:** Article + FAQ. Author + last updated.

模板 2：产品与功能页面

目标： 阐明功能、适用性和后续步骤；加强类别关联。

# [Product/Feature] — [Outcome in 3-5 words]

**[Product/Feature] enables [Outcome] for [User/Role].**

## [Feature Area 1]
[2-4 sentences using Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## [Feature Area 2]
[2-4 sentences using Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## [Feature Area 3]
[2-4 sentences using Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## FAQ
**Q: [Question]?**
A: [~1 sentence]

**Q: [Question]?**
A: [~1 sentence]

**Q: [Question]?**
A: [~1 sentence]

---
**Links:** Back to [Category Explainer] | Forward to [Demo/Trial]
**Proof:** [Benchmark/Analyst/Customer proof]
**Notes:** Requirements/limits (pricing tier, integrations)
**Schema:** Article + FAQ. Author + last updated.

模板 3：对比 / 替代方案页面

目标： 用清晰的标准帮助读者决策；获得公正的引用。

# [Product] vs. [Alternative] — Which fits [Use case]?

## Comparison Table

| Criterion | [Product] | [Alt A] | [Alt B] | Source |
|-----------|-----------|---------|---------|--------|
| [Feature/Limit] | [value] | [value] | [value] | [link] |
| [Requirement] | [value] | [value] | [value] | [link] |
| [Best for] | [value] | [value] | [value] | [link] |

*Source-back all claims in the table or footnotes.*

## Fit Statements

1. **[Product]** suits [Team/Use case] when [Condition].
2. **[Alt A]** fits [Team/Use case] when [Condition].
3. **[Alt B]** works for [Team/Use case] when [Condition].

---
**Links:** [Category Explainer] | [Feature pages]
**CTA:** [Try / Demo / Talk to Sales]
**Schema:** Article. Author + last updated.

模板 4：用例 / 行业页面

目标： 在读者熟悉的场景中将产品与成果联系起来。

# [Industry/Use Case] — [Outcome KPI]

**Teams reduce [Metric] by [Y%] in [Timeframe].**

## Mini Case Study
[Company/Role] used [Product/Feature] to [Action], resulting in
[Metric improvement] within [Timeframe].

## How It Works

### [Feature 1]
[Feature → How → Outcome paragraph]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

### [Feature 2]
[Feature → How → Outcome paragraph]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## Who Uses This
**Roles:** [Role 1], [Role 2], [Role 3]
**Workflows:** [Workflow 1], [Workflow 2]
**Integrations:** [Integration 1], [Integration 2]

---
**Links:** [Product/Feature pages] | [Supporting blog]
**CTA:** [Industry template / Demo variant]
**Schema:** Article. Author + last updated.

模板 5：支持性博客文章

目标： 增加信息增益并支持您的内容集群。

# [Topic] — [Specific promise]

## Opening (~60-80 words)
[State the problem. Align terminology with Category Explainer. Preview outcome.]

## [Section 1 Heading] (~120 words max)
[Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

**Internal link:** [Related page]
**External citation:** [Credible source]

## [Section 2 Heading] (~120 words max)
[Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

**Internal link:** [Related page]
**External citation:** [Credible source]

## Key Takeaway
[1-2 lines summarizing the main point]

**CTA:** [Single primary action]

---
**Schema:** Article. Author + last updated.

元素	实现方式
Schema 标记	Article + FAQ（如果存在 FAQ）
作者署名	姓名、简介、资历、照片
最后更新日期	可见、机器可读
内部链接	每页 3-5 个（上游/下游）
外部引用	每部分 1-2 个可信来源
单一 CTA	演示、模板或注册（在末尾附近重复一次）

<!-- Article Schema -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Page Title]",
  "author": {
    "@type": "Person",
    "name": "[Author Name]",
    "url": "[Author Bio URL]"
  },
  "datePublished": "[ISO Date]",
  "dateModified": "[ISO Date]",
  "publisher": {
    "@type": "Organization",
    "name": "[Company]",
    "logo": "[Logo URL]"
  }
}
</script>

<!-- FAQ Schema (if FAQ section exists) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "[Question 1]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer 1]"
      }
    },
    {
      "@type": "Question",
      "name": "[Question 2]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer 2]"
      }
    }
  ]
}
</script>

                    ┌─────────────────────┐
                    │  Category Explainer │
                    │   "What is AEO?"    │
                    └──────────┬──────────┘
                               │
        ┌──────────────────────┼──────────────────────┐
        │                      │                      │
        ▼                      ▼                      ▼
┌───────────────┐    ┌───────────────┐    ┌───────────────┐
│ Product Page  │    │ Product Page  │    │ Product Page  │
│  "Feature A"  │    │  "Feature B"  │    │  "Feature C"  │
└───────┬───────┘    └───────┬───────┘    └───────┬───────┘
        │                    │                    │
        ▼                    ▼                    ▼
┌───────────────┐    ┌───────────────┐    ┌───────────────┐
│  Blog Post    │    │  Use Case     │    │  Comparison   │
│  (supports)   │    │  (industry)   │    │  (vs. alt)    │
└───────────────┘    └───────────────┘    └───────────────┘

类别解释页面向下链接到所有产品页面
产品页面向上链接到类别解释页面
产品页面横向链接到相关功能页面
博客文章向上链接到产品页面
对比页面链接到类别解释页面 + 相关产品页面

AEO 写作检查清单

遵循功能 → 方式 → 结果模式
包含 2-4 句话（可快速浏览）
包含 1-2 个语义三元组
命名特定实体（不使用模糊的"它"或"这个"）
使用主动语态动词

每部分检查清单

有 1 个内部链接（上游或下游）
有 1 个外部引用（可信来源）
部分标题命名了一个实体
最多约 120 个单词

H1 包含主要实体 + 价值承诺
开篇主张是一个语义三元组
总共 3-5 个内部链接
总共 1-2 个外部引用
迷你常见问题解答（如果适用）
单一主要 CTA
Schema 标记（Article + FAQ）
作者姓名 + 简介链接
最后更新日期可见

每个关键类别都有类别解释页面
产品页面链接回类别解释页面
内容集群架构已记录
存在带有资历的作者简介页面
所有页面术语一致

指标	如何跟踪
AI 引用	在 ChatGPT、Claude、Perplexity 中手动检查
AI 中的品牌提及	在 AI 引擎中搜索"[品牌] + [类别]"
答案份额	与竞争对手相比，您被引用的频率
LLM 流量	GA4 中来自 chatgpt.com、claude.ai、perplexity.ai 的引荐流量
展示次数到点击量的差距	GSC 展示次数与实际点击量对比

HubSpot AEO Grader - 评估您品牌的 AI 可见性
Google Analytics 4 - 跟踪 LLM 引荐流量
Google Search Console - 监控展示次数与点击量的差距
手动 AI 查询 - 定期在 AI 引擎中测试您的品牌

常见的 AEO 错误

错误	修复方法
模糊的语言（"它有助于处理事情"）	使用特定的实体和三元组
没有清晰的结构	使用功能 → 方式 → 结果
缺少 Schema	添加 Article + FAQ Schema
没有作者署名	添加作者姓名、简介、资历
通用内容	添加原创数据、示例、观点
孤立页面	链接到内容集群中
模棱两可（"视情况而定"）	采取明确的立场
没有外部引用	每部分添加 1-2 个可信来源

AEO 与传统 SEO 对比

方面	传统 SEO	AEO
目标	排名第一页	在 AI 答案中被引用
成功指标	点击率	答案份额
内容重点	关键词	实体 + 事实
结构	用于浏览的标题	用于提取的三元组
链接	用于权威性的反向链接	用于共识的引用
更新	定期刷新	持续保持准确性

语义三元组模式

[Entity/Product] [active verb] [concrete object/result].

[Feature] helps [User] with [Job].
It [mechanism] to [process].
Teams see [result] in [timeframe].

3-5 个内部链接
每部分 1-2 个外部引用
3 个带有 Schema 的常见问题
作者 + 最后更新日期
单一 CTA

类别解释页面（顶层）
产品/功能页面（中层）
用例 / 对比 / 博客（支持层）

🇺🇸English

AI Engine Optimization (AEO) Skill

Load with: base.md + web-content.md + site-architecture.md

Purpose: Optimize content for AI engines (ChatGPT, Claude, Perplexity, Google AI Overviews) so your brand gets cited in AI-generated answers.

Source: Based on HubSpot's AEO Guide and industry best practices.

Why AEO Matters Now

┌────────────────────────────────────────────────────────────────┐
│  THE GREAT DECOUPLING                                          │
│  ────────────────────────────────────────────────────────────  │
│  Impressions ≠ Clicks anymore.                                 │
│  AI engines compile answers from multiple sources.             │
│  More buyer journey happens inside chat experiences.           │
│  58% of Google searches = zero clicks (AI overviews).          │
├────────────────────────────────────────────────────────────────┤
│  THE OPPORTUNITY                                               │
│  ────────────────────────────────────────────────────────────  │
│  Shape what AI engines say about your category and product.    │
│  Get cited as the authoritative source.                        │
│  Best answer > Best page ranking.                              │
└────────────────────────────────────────────────────────────────┘

Key Stats:

70% of consumers use ChatGPT for searches
47% of Google queries show AI overviews
Average ChatGPT prompt: 23 words (vs 4.2 for Google)
AEO market: $886M (2024) → $7.3B (2031)

How AI Engines Choose Answers

AI engines use three main signals to select content for answers:

1. Consensus

Facts that appear across multiple credible sources get trusted and reused.

How to build consensus:

Repeat key facts consistently across your own pages
Use same terminology as industry leaders
Link to and from authoritative external sources
Create internal content clusters that reinforce each other

2. Information Gain

Net-new insight beats generic advice. AI engines prefer content that adds value.

How to add information gain:

Original research and data
Concrete examples with specifics
Clear point of view (not fence-sitting)
Expert quotes with credentials
Case studies with metrics

3. Entities & Structure

Clear entities and tidy structure reduce ambiguity and boost quotability.

How to optimize structure:

Use semantic triples (Subject → Verb → Object)
Clear headings with entity names
Schema markup (Article, FAQ, Product)
Short, scannable paragraphs (2-4 sentences)

Semantic Triples (Critical for AEO)

What they are: Compact facts that AI engines (and humans) can't misread.

Pattern: [Subject] [verb] [object].

Examples

✅ GOOD (clear triples):
- HubSpot CRM syncs contact and company data.
- Lead Scoring assigns priority based on engagement.
- Workflows trigger email sequences from events.

❌ BAD (vague, no clear entity):
- The system helps with various tasks.
- It can do many things for users.
- This improves overall performance.

Triple Checklist

For every key claim, ask:

Is the subject a clear entity (product, feature, brand)?
Is the verb specific and active?
Is the object concrete and measurable?

Paragraph Pattern (Feature → How → Outcome)

Every substantive paragraph should follow this structure:

[Feature] helps [User/Role] with [Job].
It [mechanism/inputs] to [process].
Teams see [metric/result] in [timeframe/context].

Triples:
- [Subject] [verb] [object].
- [Subject] [verb] [object].

Example

Lead Scoring helps sales teams prioritize prospects. It combines
page views, email engagement, and firmographic data to assign a
numeric score, then auto-enrolls high scorers into follow-up
sequences. Reps focus on qualified accounts and book 40% more
meetings.

- Lead Scoring assigns scores from engagement data.
- High scorers trigger automated follow-up sequences.

Page Templates

Template 1: Category Explainer

Goal: Define the category, tie it to your product, earn citations.

# What is [Category]? — [1-2 line value promise]

## What is [Category]? (~80 words)
[Plain definition in everyday language. Name adjacent entities.]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## Why it matters now (~60 words)
[One paragraph. Mention shift to answers over links; tie to buyer outcomes.]

## How to apply it (3-5 bullets)
- [Action 1]
- [Action 2]
- [Action 3]

## FAQ
**Q: [Question]?**
A: [~1 sentence answer]

**Q: [Question]?**
A: [~1 sentence answer]

**Q: [Question]?**
A: [~1 sentence answer]

---
**Links:** [Category hub] | [Product/Feature] | [Credible source 1] | [Credible source 2]
**CTA:** [Demo / Template / Signup]
**Schema:** Article + FAQ. Author + last updated.

Template 2: Product & Feature Page

Goal: Clarify capability, fit, and next step; reinforce category linkage.

# [Product/Feature] — [Outcome in 3-5 words]

**[Product/Feature] enables [Outcome] for [User/Role].**

## [Feature Area 1]
[2-4 sentences using Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## [Feature Area 2]
[2-4 sentences using Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## [Feature Area 3]
[2-4 sentences using Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## FAQ
**Q: [Question]?**
A: [~1 sentence]

**Q: [Question]?**
A: [~1 sentence]

**Q: [Question]?**
A: [~1 sentence]

---
**Links:** Back to [Category Explainer] | Forward to [Demo/Trial]
**Proof:** [Benchmark/Analyst/Customer proof]
**Notes:** Requirements/limits (pricing tier, integrations)
**Schema:** Article + FAQ. Author + last updated.

Template 3: Comparison / Alternatives Page

Goal: Help readers decide with clear criteria; earn fair citations.

# [Product] vs. [Alternative] — Which fits [Use case]?

## Comparison Table

| Criterion | [Product] | [Alt A] | [Alt B] | Source |
|-----------|-----------|---------|---------|--------|
| [Feature/Limit] | [value] | [value] | [value] | [link] |
| [Requirement] | [value] | [value] | [value] | [link] |
| [Best for] | [value] | [value] | [value] | [link] |

*Source-back all claims in the table or footnotes.*

## Fit Statements

1. **[Product]** suits [Team/Use case] when [Condition].
2. **[Alt A]** fits [Team/Use case] when [Condition].
3. **[Alt B]** works for [Team/Use case] when [Condition].

---
**Links:** [Category Explainer] | [Feature pages]
**CTA:** [Try / Demo / Talk to Sales]
**Schema:** Article. Author + last updated.

Template 4: Use Case / Industry Page

Goal: Connect product to outcomes in a context readers recognize.

# [Industry/Use Case] — [Outcome KPI]

**Teams reduce [Metric] by [Y%] in [Timeframe].**

## Mini Case Study
[Company/Role] used [Product/Feature] to [Action], resulting in
[Metric improvement] within [Timeframe].

## How It Works

### [Feature 1]
[Feature → How → Outcome paragraph]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

### [Feature 2]
[Feature → How → Outcome paragraph]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

## Who Uses This
**Roles:** [Role 1], [Role 2], [Role 3]
**Workflows:** [Workflow 1], [Workflow 2]
**Integrations:** [Integration 1], [Integration 2]

---
**Links:** [Product/Feature pages] | [Supporting blog]
**CTA:** [Industry template / Demo variant]
**Schema:** Article. Author + last updated.

Template 5: Supporting Blog Post

Goal: Add information gain and support your content cluster.

# [Topic] — [Specific promise]

## Opening (~60-80 words)
[State the problem. Align terminology with Category Explainer. Preview outcome.]

## [Section 1 Heading] (~120 words max)
[Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

**Internal link:** [Related page]
**External citation:** [Credible source]

## [Section 2 Heading] (~120 words max)
[Feature → How → Outcome]

Triples:
1. [Subject] [verb] [object].
2. [Subject] [verb] [object].

**Internal link:** [Related page]
**External citation:** [Credible source]

## Key Takeaway
[1-2 lines summarizing the main point]

**CTA:** [Single primary action]

---
**Schema:** Article. Author + last updated.

Site-Wide Trust Signals

Required on Every Page

Element	Implementation
Schema markup	Article + FAQ (if FAQ exists)
Author attribution	Name, bio, credentials, photo
Last updated date	Visible, machine-readable
Internal links	3-5 per page (upstream/downstream)
External citations	1-2 credible sources per section
Single CTA	Demo, template, or signup (repeated once near end)

Schema Implementation

<!-- Article Schema -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Page Title]",
  "author": {
    "@type": "Person",
    "name": "[Author Name]",
    "url": "[Author Bio URL]"
  },
  "datePublished": "[ISO Date]",
  "dateModified": "[ISO Date]",
  "publisher": {
    "@type": "Organization",
    "name": "[Company]",
    "logo": "[Logo URL]"
  }
}
</script>

<!-- FAQ Schema (if FAQ section exists) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "[Question 1]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer 1]"
      }
    },
    {
      "@type": "Question",
      "name": "[Question 2]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer 2]"
      }
    }
  ]
}
</script>

Content Cluster Architecture

                    ┌─────────────────────┐
                    │  Category Explainer │
                    │   "What is AEO?"    │
                    └──────────┬──────────┘
                               │
        ┌──────────────────────┼──────────────────────┐
        │                      │                      │
        ▼                      ▼                      ▼
┌───────────────┐    ┌───────────────┐    ┌───────────────┐
│ Product Page  │    │ Product Page  │    │ Product Page  │
│  "Feature A"  │    │  "Feature B"  │    │  "Feature C"  │
└───────┬───────┘    └───────┬───────┘    └───────┬───────┘
        │                    │                    │
        ▼                    ▼                    ▼
┌───────────────┐    ┌───────────────┐    ┌───────────────┐
│  Blog Post    │    │  Use Case     │    │  Comparison   │
│  (supports)   │    │  (industry)   │    │  (vs. alt)    │
└───────────────┘    └───────────────┘    └───────────────┘

Linking Rules:

Category Explainer links DOWN to all product pages
Product pages link UP to Category Explainer
Product pages link ACROSS to related features
Blog posts link UP to Product pages
Comparison pages link to Category Explainer + relevant Product pages

AEO Writing Checklist

Per-Paragraph Checklist

Follows Feature → How → Outcome pattern
Contains 2-4 sentences (scannable)
Includes 1-2 semantic triples
Names specific entities (not vague "it" or "this")
Uses active voice verbs

Per-Section Checklist

Has 1 internal link (upstream or downstream)
Has 1 external citation (credible source)
Section heading names an entity
~120 words max

Per-Page Checklist

H1 contains primary entity + value promise
Opening claim is a semantic triple
3-5 internal links total
1-2 external citations total
Mini-FAQ with 3 questions (if applicable)
Single primary CTA
Schema markup (Article + FAQ)
Author name + bio link
Last updated date visible

Site-Wide Checklist

Category Explainer exists for each key category
Product pages link back to Category Explainer
Content cluster architecture documented
Author bio pages exist with credentials
Consistent terminology across all pages

Measuring AEO Success

Key Metrics

Metric	How to Track
AI citations	Manual checks in ChatGPT, Claude, Perplexity
Brand mentions in AI	Search "[brand] + [category]" in AI engines
Share of answer	How often you're cited vs competitors
LLM traffic	GA4 referral from chatgpt.com, claude.ai, perplexity.ai
Impressions-to-clicks gap	GSC impressions vs actual clicks

Tools

HubSpot AEO Grader - Grade your brand's AI visibility
Google Analytics 4 - Track LLM referral traffic
Google Search Console - Monitor impressions vs clicks gap
Manual AI queries - Regularly test your brand in AI engines

Common AEO Mistakes

Mistake	Fix
Vague language ("it helps with things")	Use specific entities and triples
No clear structure	Use Feature → How → Outcome
Missing schema	Add Article + FAQ schema
No author attribution	Add author name, bio, credentials
Generic content	Add original data, examples, POV
Orphan pages	Link into content cluster
Fence-sitting ("it depends")	Take a clear position
No external citations	Add 1-2 credible sources per section

AEO vs Traditional SEO

Aspect	Traditional SEO	AEO
Goal	Rank on page 1	Get cited in AI answers
Success metric	Click-through rate	Share of answer
Content focus	Keywords	Entities + facts
Structure	Headers for scanning	Triples for extraction
Links	Backlinks for authority	Citations for consensus
Updates	Periodic refresh	Continuous accuracy

Quick Reference

Semantic Triple Pattern

[Entity/Product] [active verb] [concrete object/result].

Paragraph Pattern

[Feature] helps [User] with [Job].
It [mechanism] to [process].
Teams see [result] in [timeframe].

Page Minimums

3-5 internal links
1-2 external citations per section
3 FAQ questions with schema
Author + last updated
Single CTA

Content Hierarchy

Category Explainer (top)
Product/Feature pages (middle)
Use case / Comparison / Blog (supporting)

Weekly Installs

134

Repository

alinaqi/claude-bootstrap

GitHub Stars

531

First Seen

Jan 20, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

claude-code110

opencode106

gemini-cli101

codex101

cursor98

github-copilot86

超能力技能使用指南：AI助手技能调用优先级与工作流程详解

50,500 周安装