bmad-plus 0.4.1 → 0.4.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +11 -0
- package/README.md +3 -2
- package/package.json +1 -1
- package/readme-international/README.de.md +1 -1
- package/readme-international/README.es.md +1 -1
- package/readme-international/README.fr.md +1 -1
- package/src/bmad-plus/agents/pack-animated/animated-website-agent.md +325 -0
- package/src/bmad-plus/agents/pack-animated/templates/animated-website-workflow.md +55 -0
- package/src/bmad-plus/agents/pack-backup/backup-agent.md +71 -0
- package/src/bmad-plus/agents/pack-backup/templates/backup-workflow.md +51 -0
- package/src/bmad-plus/agents/pack-seo/SKILL.md +171 -0
- package/src/bmad-plus/agents/pack-seo/checklist.md +140 -0
- package/src/bmad-plus/agents/pack-seo/pagespeed-playbook.md +320 -0
- package/src/bmad-plus/agents/pack-seo/ref/audit-schema.json +187 -0
- package/src/bmad-plus/agents/pack-seo/ref/cwv-thresholds.md +87 -0
- package/src/bmad-plus/agents/pack-seo/ref/eeat-criteria.md +123 -0
- package/src/bmad-plus/agents/pack-seo/ref/geo-signals.md +167 -0
- package/src/bmad-plus/agents/pack-seo/ref/hreflang-rules.md +153 -0
- package/src/bmad-plus/agents/pack-seo/ref/quality-gates.md +133 -0
- package/src/bmad-plus/agents/pack-seo/ref/schema-catalog.md +91 -0
- package/src/bmad-plus/agents/pack-seo/ref/schema-templates.json +356 -0
- package/src/bmad-plus/agents/pack-seo/seo-chief.md +294 -0
- package/src/bmad-plus/agents/pack-seo/seo-judge.md +241 -0
- package/src/bmad-plus/agents/pack-seo/seo-scout.md +171 -0
- package/src/bmad-plus/agents/pack-seo/templates/seo-audit-workflow.md +241 -0
- package/tools/cli/commands/install.js +15 -14
- package/tools/cli/i18n.js +10 -10
|
@@ -0,0 +1,187 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "http://json-schema.org/draft-07/schema#",
|
|
3
|
+
"title": "BMAD+ SEO Audit Result",
|
|
4
|
+
"description": "Standardized JSON format for SEO audit results. Compatible with dashboards, MCP Server, and external tools.",
|
|
5
|
+
"version": "1.0.0",
|
|
6
|
+
"author": "Laurent Rochetta",
|
|
7
|
+
"type": "object",
|
|
8
|
+
"required": ["engine", "version", "domain", "timestamp", "score", "issues"],
|
|
9
|
+
"properties": {
|
|
10
|
+
"engine": {
|
|
11
|
+
"type": "string",
|
|
12
|
+
"const": "bmad-seo-engine",
|
|
13
|
+
"description": "Engine identifier"
|
|
14
|
+
},
|
|
15
|
+
"version": {
|
|
16
|
+
"type": "string",
|
|
17
|
+
"description": "Engine version",
|
|
18
|
+
"examples": ["2.1.0"]
|
|
19
|
+
},
|
|
20
|
+
"domain": {
|
|
21
|
+
"type": "string",
|
|
22
|
+
"description": "Audited domain (without protocol)",
|
|
23
|
+
"examples": ["example.com"]
|
|
24
|
+
},
|
|
25
|
+
"url": {
|
|
26
|
+
"type": "string",
|
|
27
|
+
"format": "uri",
|
|
28
|
+
"description": "Full URL audited"
|
|
29
|
+
},
|
|
30
|
+
"timestamp": {
|
|
31
|
+
"type": "string",
|
|
32
|
+
"format": "date-time",
|
|
33
|
+
"description": "ISO 8601 timestamp of audit completion"
|
|
34
|
+
},
|
|
35
|
+
"business_type": {
|
|
36
|
+
"type": "string",
|
|
37
|
+
"enum": ["saas", "ecommerce", "local", "publisher", "agency", "other"],
|
|
38
|
+
"description": "Detected business type"
|
|
39
|
+
},
|
|
40
|
+
"pages_analyzed": {
|
|
41
|
+
"type": "integer",
|
|
42
|
+
"minimum": 1,
|
|
43
|
+
"description": "Number of pages analyzed"
|
|
44
|
+
},
|
|
45
|
+
"score": {
|
|
46
|
+
"type": "object",
|
|
47
|
+
"required": ["total", "categories"],
|
|
48
|
+
"properties": {
|
|
49
|
+
"total": {
|
|
50
|
+
"type": "integer",
|
|
51
|
+
"minimum": 0,
|
|
52
|
+
"maximum": 100,
|
|
53
|
+
"description": "Weighted SEO Health Score"
|
|
54
|
+
},
|
|
55
|
+
"rating": {
|
|
56
|
+
"type": "string",
|
|
57
|
+
"enum": ["excellent", "good", "needs_work", "poor", "critical"],
|
|
58
|
+
"description": "Score interpretation"
|
|
59
|
+
},
|
|
60
|
+
"categories": {
|
|
61
|
+
"type": "object",
|
|
62
|
+
"properties": {
|
|
63
|
+
"technical": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
64
|
+
"content_eeat": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
65
|
+
"on_page": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
66
|
+
"schema": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
67
|
+
"performance": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
68
|
+
"ai_readiness": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
69
|
+
"images": { "type": "integer", "minimum": 0, "maximum": 100 }
|
|
70
|
+
},
|
|
71
|
+
"description": "Score per category (0-100)"
|
|
72
|
+
}
|
|
73
|
+
}
|
|
74
|
+
},
|
|
75
|
+
"issues": {
|
|
76
|
+
"type": "array",
|
|
77
|
+
"items": {
|
|
78
|
+
"type": "object",
|
|
79
|
+
"required": ["id", "severity", "category", "title"],
|
|
80
|
+
"properties": {
|
|
81
|
+
"id": {
|
|
82
|
+
"type": "string",
|
|
83
|
+
"description": "Unique issue identifier",
|
|
84
|
+
"examples": ["missing-meta-description", "multiple-h1"]
|
|
85
|
+
},
|
|
86
|
+
"severity": {
|
|
87
|
+
"type": "string",
|
|
88
|
+
"enum": ["critical", "high", "medium", "low"]
|
|
89
|
+
},
|
|
90
|
+
"category": {
|
|
91
|
+
"type": "string",
|
|
92
|
+
"enum": ["technical", "content", "on_page", "schema", "performance", "geo", "images"]
|
|
93
|
+
},
|
|
94
|
+
"title": {
|
|
95
|
+
"type": "string",
|
|
96
|
+
"description": "Human-readable issue title"
|
|
97
|
+
},
|
|
98
|
+
"description": {
|
|
99
|
+
"type": "string",
|
|
100
|
+
"description": "Detailed explanation"
|
|
101
|
+
},
|
|
102
|
+
"affected_urls": {
|
|
103
|
+
"type": "array",
|
|
104
|
+
"items": { "type": "string", "format": "uri" },
|
|
105
|
+
"description": "Pages affected by this issue"
|
|
106
|
+
},
|
|
107
|
+
"fix": {
|
|
108
|
+
"type": "string",
|
|
109
|
+
"description": "Auto-generated fix code (HTML, JSON-LD, etc.)"
|
|
110
|
+
},
|
|
111
|
+
"quick_win": {
|
|
112
|
+
"type": "boolean",
|
|
113
|
+
"description": "True if high impact / low effort"
|
|
114
|
+
},
|
|
115
|
+
"impact": {
|
|
116
|
+
"type": "string",
|
|
117
|
+
"enum": ["high", "medium", "low"]
|
|
118
|
+
},
|
|
119
|
+
"effort": {
|
|
120
|
+
"type": "string",
|
|
121
|
+
"enum": ["high", "medium", "low"]
|
|
122
|
+
}
|
|
123
|
+
}
|
|
124
|
+
}
|
|
125
|
+
},
|
|
126
|
+
"pages": {
|
|
127
|
+
"type": "array",
|
|
128
|
+
"items": {
|
|
129
|
+
"type": "object",
|
|
130
|
+
"properties": {
|
|
131
|
+
"url": { "type": "string", "format": "uri" },
|
|
132
|
+
"status": { "type": "integer" },
|
|
133
|
+
"title": { "type": "string" },
|
|
134
|
+
"word_count": { "type": "integer" },
|
|
135
|
+
"schema_types": { "type": "array", "items": { "type": "string" } },
|
|
136
|
+
"eeat_score": { "type": "integer", "minimum": 0, "maximum": 100 }
|
|
137
|
+
}
|
|
138
|
+
},
|
|
139
|
+
"description": "Per-page analysis data"
|
|
140
|
+
},
|
|
141
|
+
"geo": {
|
|
142
|
+
"type": "object",
|
|
143
|
+
"properties": {
|
|
144
|
+
"ai_readiness_score": { "type": "integer", "minimum": 0, "maximum": 100 },
|
|
145
|
+
"ai_crawlers_allowed": { "type": "array", "items": { "type": "string" } },
|
|
146
|
+
"has_llms_txt": { "type": "boolean" },
|
|
147
|
+
"citability_score": { "type": "integer", "minimum": 0, "maximum": 100 }
|
|
148
|
+
},
|
|
149
|
+
"description": "GEO / AI search readiness metrics"
|
|
150
|
+
},
|
|
151
|
+
"pagespeed": {
|
|
152
|
+
"type": "object",
|
|
153
|
+
"properties": {
|
|
154
|
+
"mobile": {
|
|
155
|
+
"type": "object",
|
|
156
|
+
"properties": {
|
|
157
|
+
"performance": { "type": "integer" },
|
|
158
|
+
"accessibility": { "type": "integer" },
|
|
159
|
+
"best_practices": { "type": "integer" },
|
|
160
|
+
"seo": { "type": "integer" }
|
|
161
|
+
}
|
|
162
|
+
},
|
|
163
|
+
"desktop": {
|
|
164
|
+
"type": "object",
|
|
165
|
+
"properties": {
|
|
166
|
+
"performance": { "type": "integer" },
|
|
167
|
+
"accessibility": { "type": "integer" },
|
|
168
|
+
"best_practices": { "type": "integer" },
|
|
169
|
+
"seo": { "type": "integer" }
|
|
170
|
+
}
|
|
171
|
+
}
|
|
172
|
+
},
|
|
173
|
+
"description": "PageSpeed Insights scores"
|
|
174
|
+
},
|
|
175
|
+
"monitoring": {
|
|
176
|
+
"type": "object",
|
|
177
|
+
"properties": {
|
|
178
|
+
"previous_score": { "type": "integer" },
|
|
179
|
+
"previous_date": { "type": "string", "format": "date" },
|
|
180
|
+
"delta": { "type": "integer" },
|
|
181
|
+
"issues_resolved": { "type": "integer" },
|
|
182
|
+
"issues_new": { "type": "integer" }
|
|
183
|
+
},
|
|
184
|
+
"description": "Comparison with previous audit (if available)"
|
|
185
|
+
}
|
|
186
|
+
}
|
|
187
|
+
}
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
# Core Web Vitals — Thresholds & Optimization Guide (March 2026)
|
|
2
|
+
|
|
3
|
+
> Author: Laurent Rochetta | BMAD+ SEO Engine v2.0
|
|
4
|
+
|
|
5
|
+
## Current Metrics
|
|
6
|
+
|
|
7
|
+
| Metric | Good | Needs Improvement | Poor |
|
|
8
|
+
|--------|------|-------------------|------|
|
|
9
|
+
| **LCP** (Largest Contentful Paint) | ≤2.5s | 2.5–4.0s | >4.0s |
|
|
10
|
+
| **INP** (Interaction to Next Paint) | ≤200ms | 200–500ms | >500ms |
|
|
11
|
+
| **CLS** (Cumulative Layout Shift) | ≤0.1 | 0.1–0.25 | >0.25 |
|
|
12
|
+
|
|
13
|
+
> **INP replaced FID on March 12, 2024.** FID was fully removed from all Chrome tools on September 9, 2024. Never reference FID.
|
|
14
|
+
|
|
15
|
+
## Key Facts
|
|
16
|
+
- Evaluation uses the **75th percentile** of real user data (CrUX field data)
|
|
17
|
+
- Assessment at **page level** AND **origin level**
|
|
18
|
+
- CWV is a **tiebreaker** signal — matters most when content quality is similar
|
|
19
|
+
- Thresholds **unchanged since original definitions**
|
|
20
|
+
- December 2025 core update appeared to weight **mobile CWV more heavily**
|
|
21
|
+
- As of October 2025: 57.1% desktop, 49.7% mobile sites pass all three CWV
|
|
22
|
+
- **Mobile-first indexing 100% complete** since July 5, 2024
|
|
23
|
+
|
|
24
|
+
## LCP Diagnostic Subparts (Feb 2025 CrUX)
|
|
25
|
+
|
|
26
|
+
| Subpart | Description | Target |
|
|
27
|
+
|---------|-------------|--------|
|
|
28
|
+
| TTFB | Server response time | <800ms |
|
|
29
|
+
| Resource Load Delay | TTFB to resource request | Minimize |
|
|
30
|
+
| Resource Load Time | LCP resource download | Size-dependent |
|
|
31
|
+
| Element Render Delay | Loaded to painted | Minimize |
|
|
32
|
+
|
|
33
|
+
**Total LCP = TTFB + Load Delay + Load Time + Render Delay**
|
|
34
|
+
|
|
35
|
+
## Common Bottlenecks
|
|
36
|
+
|
|
37
|
+
### LCP
|
|
38
|
+
- Unoptimized hero images → use WebP/AVIF, add `<link rel="preload">`
|
|
39
|
+
- Render-blocking CSS/JS → defer, async, critical CSS inline
|
|
40
|
+
- Slow TTFB (>200ms) → CDN, caching, edge compute
|
|
41
|
+
- Third-party blocking → defer analytics, chat widgets
|
|
42
|
+
- Font delay → `font-display: swap` + preload
|
|
43
|
+
|
|
44
|
+
### INP
|
|
45
|
+
- Long JS tasks on main thread → break tasks <50ms, use `scheduler.yield()`
|
|
46
|
+
- Heavy event handlers → debounce, requestAnimationFrame
|
|
47
|
+
- Excessive DOM (>1,500 elements)
|
|
48
|
+
- Third-party scripts hijacking main thread
|
|
49
|
+
- Layout thrashing (forced reflows)
|
|
50
|
+
|
|
51
|
+
### CLS
|
|
52
|
+
- Images/iframes without width/height dimensions
|
|
53
|
+
- Dynamic content injected above existing content
|
|
54
|
+
- Font swap causing layout shift → preload + font-display
|
|
55
|
+
- Ads/embeds without reserved space
|
|
56
|
+
|
|
57
|
+
## Measurement Sources
|
|
58
|
+
|
|
59
|
+
### Field Data (used for ranking)
|
|
60
|
+
- Chrome User Experience Report (CrUX)
|
|
61
|
+
- PageSpeed Insights (uses CrUX)
|
|
62
|
+
- Search Console Core Web Vitals report
|
|
63
|
+
|
|
64
|
+
### Lab Data (for debugging)
|
|
65
|
+
- Lighthouse 13.0 (Oct 2025, restructured audits)
|
|
66
|
+
- WebPageTest
|
|
67
|
+
- Chrome DevTools
|
|
68
|
+
|
|
69
|
+
## Optimization Priority
|
|
70
|
+
1. **LCP** — Most impactful for perceived performance
|
|
71
|
+
2. **CLS** — Most common UX issue
|
|
72
|
+
3. **INP** — Critical for interactive applications
|
|
73
|
+
|
|
74
|
+
## API Tools
|
|
75
|
+
```bash
|
|
76
|
+
# PageSpeed Insights API
|
|
77
|
+
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=URL&key=API_KEY"
|
|
78
|
+
|
|
79
|
+
# Lighthouse CLI
|
|
80
|
+
npx lighthouse URL --output json --output-path report.json
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
## 2025–2026 Updates
|
|
84
|
+
- **Lighthouse 13.0** (Oct 2025): reorganized performance categories
|
|
85
|
+
- **CrUX Vis** replaced CrUX Dashboard (Nov 2025) → cruxvis.withgoogle.com
|
|
86
|
+
- **LCP subparts** in CrUX (Feb 2025)
|
|
87
|
+
- **Soft Navigations API** (Chrome 139+, July 2025): experimental SPA CWV measurement — no ranking impact yet
|
|
@@ -0,0 +1,123 @@
|
|
|
1
|
+
# E-E-A-T Evaluation Criteria (March 2026)
|
|
2
|
+
|
|
3
|
+
> Author: Laurent Rochetta | BMAD+ SEO Engine v2.0
|
|
4
|
+
> Based on: Google Quality Rater Guidelines (September 2025 update)
|
|
5
|
+
|
|
6
|
+
## Overview
|
|
7
|
+
|
|
8
|
+
E-E-A-T = **Experience, Expertise, Authoritativeness, Trustworthiness**
|
|
9
|
+
|
|
10
|
+
Google's quality raters evaluate pages on these four dimensions. While not a direct ranking factor, E-E-A-T signals influence how Google's algorithms assess content quality and YMYL (Your Money or Your Life) pages.
|
|
11
|
+
|
|
12
|
+
> Since March 2024, the Helpful Content System is merged into Google's core algorithm. Enforcement is continuous, not via separate HCU updates.
|
|
13
|
+
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
## Experience (25 points)
|
|
17
|
+
|
|
18
|
+
First-hand, real-world experience with the topic.
|
|
19
|
+
|
|
20
|
+
| Signal | Points | How to Detect |
|
|
21
|
+
|--------|--------|---------------|
|
|
22
|
+
| Original research or case studies | 8 | Unique data, before/after results, proprietary findings |
|
|
23
|
+
| First-hand process documentation | 6 | Step-by-step from personal experience, production screenshots |
|
|
24
|
+
| Unique media from direct experience | 6 | Original photos, self-recorded videos, personal screenshots |
|
|
25
|
+
| Specific examples and anecdotes | 5 | Named examples, concrete details, real scenarios |
|
|
26
|
+
|
|
27
|
+
**Red flags**: Generic advice that could come from any source, stock photos only, no personal perspective.
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## Expertise (25 points)
|
|
32
|
+
|
|
33
|
+
Demonstrable knowledge and skill in the subject area.
|
|
34
|
+
|
|
35
|
+
| Signal | Points | How to Detect |
|
|
36
|
+
|--------|--------|---------------|
|
|
37
|
+
| Author credentials visible | 7 | Bio with qualifications, certifications, professional background |
|
|
38
|
+
| Technical depth appropriate | 7 | Correct terminology, nuanced explanations, awareness of edge cases |
|
|
39
|
+
| Well-sourced claims | 6 | Citations to studies, official documentation, linked sources |
|
|
40
|
+
| Comprehensive topic coverage | 5 | Covers subtopics, addresses counterarguments, FAQ sections |
|
|
41
|
+
|
|
42
|
+
**Red flags**: No author identified, surface-level coverage, factual errors, outdated information.
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
## Authoritativeness (25 points)
|
|
47
|
+
|
|
48
|
+
Recognition as a trusted source by peers and industry.
|
|
49
|
+
|
|
50
|
+
| Signal | Points | How to Detect |
|
|
51
|
+
|--------|--------|---------------|
|
|
52
|
+
| External citations / references | 7 | Backlinks from authoritative sites, cited in industry publications |
|
|
53
|
+
| Brand recognition signals | 7 | Awards, partnerships, media mentions, client logos |
|
|
54
|
+
| Author published elsewhere | 6 | Guest posts, conference talks, books, academic papers |
|
|
55
|
+
| Expert endorsements | 5 | Testimonials from peers, quoted by other experts |
|
|
56
|
+
|
|
57
|
+
**Red flags**: Brand-new domain with no web presence, no external references, no social proof.
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## Trustworthiness (25 points)
|
|
62
|
+
|
|
63
|
+
Transparency, accuracy, and confidence in the source.
|
|
64
|
+
|
|
65
|
+
| Signal | Points | How to Detect |
|
|
66
|
+
|--------|--------|---------------|
|
|
67
|
+
| Contact info and physical address | 7 | Phone, email, postal address, About page |
|
|
68
|
+
| Privacy policy and terms | 5 | Legal pages present, accessible, and up-to-date |
|
|
69
|
+
| HTTPS and security signals | 5 | Valid SSL, HSTS, security headers present |
|
|
70
|
+
| Transparent authorship and dates | 5 | Author byline, publication date, last updated date |
|
|
71
|
+
| Customer proof | 3 | Verified reviews, testimonials, case studies |
|
|
72
|
+
|
|
73
|
+
**Red flags**: No contact information, anonymous content, no dates, misleading claims, HTTP only.
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
## YMYL Pages — Higher Standards
|
|
78
|
+
|
|
79
|
+
YMYL (Your Money or Your Life) topics require **elevated E-E-A-T**:
|
|
80
|
+
|
|
81
|
+
| YMYL Category | Examples | E-E-A-T Bar |
|
|
82
|
+
|---------------|----------|-------------|
|
|
83
|
+
| Health | Medical advice, symptoms, treatments | Very High — requires medical expertise |
|
|
84
|
+
| Finance | Investment, tax, insurance, banking | Very High — requires financial credentials |
|
|
85
|
+
| Safety | Product safety, emergency info | Very High |
|
|
86
|
+
| Legal | Legal rights, contracts, regulations | Very High — requires legal expertise |
|
|
87
|
+
| News | Current events, political coverage | High — requires journalistic standards |
|
|
88
|
+
| Shopping | Product reviews, comparisons | Moderate-High |
|
|
89
|
+
|
|
90
|
+
---
|
|
91
|
+
|
|
92
|
+
## AI Content Assessment (Sept 2025 QRG Addition)
|
|
93
|
+
|
|
94
|
+
Google raters now formally assess AI-generated content.
|
|
95
|
+
|
|
96
|
+
### Acceptable AI Content
|
|
97
|
+
- Demonstrates genuine E-E-A-T despite AI assistance
|
|
98
|
+
- Provides unique value (not just rephrased existing content)
|
|
99
|
+
- Has clear human oversight and editing
|
|
100
|
+
- Contains original analysis, insights, or perspective
|
|
101
|
+
- Includes first-party data or real-world evidence
|
|
102
|
+
|
|
103
|
+
### Low-Quality AI Content Markers
|
|
104
|
+
- Generic phrasing with no specificity
|
|
105
|
+
- Repetitive structure across multiple pages (cookie-cutter)
|
|
106
|
+
- No original insights or unique data
|
|
107
|
+
- Missing author attribution entirely
|
|
108
|
+
- Factual inaccuracies or hallucinated statistics
|
|
109
|
+
- Excessive use of filler words and hedging language
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## Scoring Methodology
|
|
114
|
+
|
|
115
|
+
**Total E-E-A-T Score = Experience + Expertise + Authoritativeness + Trustworthiness (out of 100)**
|
|
116
|
+
|
|
117
|
+
| Range | Rating | Interpretation |
|
|
118
|
+
|-------|--------|---------------|
|
|
119
|
+
| 80–100 | Excellent | Strong signals across all dimensions |
|
|
120
|
+
| 60–79 | Good | Solid foundation with room to improve |
|
|
121
|
+
| 40–59 | Needs Work | Significant gaps in one or more areas |
|
|
122
|
+
| 20–39 | Poor | Major deficiencies undermining credibility |
|
|
123
|
+
| 0–19 | Critical | Lacking basic trust and expertise signals |
|
|
@@ -0,0 +1,167 @@
|
|
|
1
|
+
# GEO Signals — AI Search Optimization Guide (March 2026)
|
|
2
|
+
|
|
3
|
+
> Author: Laurent Rochetta | BMAD+ SEO Engine v2.0
|
|
4
|
+
|
|
5
|
+
## What is GEO?
|
|
6
|
+
|
|
7
|
+
**Generative Engine Optimization (GEO)** is the discipline of optimizing content for AI-generated answers across Google AI Overviews, ChatGPT, Perplexity, Bing Copilot, and other AI-powered search experiences.
|
|
8
|
+
|
|
9
|
+
## AI Search Landscape
|
|
10
|
+
|
|
11
|
+
| Platform | Reach | Key Citation Sources |
|
|
12
|
+
|----------|-------|---------------------|
|
|
13
|
+
| Google AI Overviews | 1.5B users/month, 200+ countries, 50%+ query coverage | Top-10 ranking pages (92%) |
|
|
14
|
+
| Google AI Mode | Full conversational search (May 2025), zero organic links | Citation is the only visibility mechanism |
|
|
15
|
+
| ChatGPT Search | 900M weekly active users | Wikipedia (47.9%), Reddit (11.3%) |
|
|
16
|
+
| Perplexity | 500M+ monthly queries | Reddit (46.7%), Wikipedia |
|
|
17
|
+
| Bing Copilot | Integrated in Edge/Windows | Bing index, authoritative sites |
|
|
18
|
+
|
|
19
|
+
> AI-referred sessions grew **527%** between January and May 2025 (SparkToro).
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## The Brand Mention Revolution
|
|
24
|
+
|
|
25
|
+
**Brand mentions correlate 3× more strongly with AI visibility than backlinks.**
|
|
26
|
+
(Ahrefs December 2025 study, 75,000 brands)
|
|
27
|
+
|
|
28
|
+
| Signal | Correlation with AI Citations |
|
|
29
|
+
|--------|-------------------------------|
|
|
30
|
+
| YouTube mentions | ~0.737 (strongest) |
|
|
31
|
+
| Reddit mentions | High |
|
|
32
|
+
| Wikipedia presence | High |
|
|
33
|
+
| LinkedIn presence | Moderate |
|
|
34
|
+
| Domain Rating (backlinks) | ~0.266 (weak) |
|
|
35
|
+
|
|
36
|
+
> Only **11%** of domains are cited by both ChatGPT and Google AI Overviews for the same query — platform-specific optimization is essential.
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## GEO Scoring Criteria
|
|
41
|
+
|
|
42
|
+
### 1. Citability (25%)
|
|
43
|
+
|
|
44
|
+
**Optimal passage length: 134–167 words** for AI citation.
|
|
45
|
+
|
|
46
|
+
| Signal | Strong | Weak |
|
|
47
|
+
|--------|--------|------|
|
|
48
|
+
| Quotable statements with facts/stats | ✅ | Vague generic statements |
|
|
49
|
+
| Self-contained answer blocks | ✅ | Requires surrounding context |
|
|
50
|
+
| Direct answer in first 40–60 words | ✅ | Buried conclusions |
|
|
51
|
+
| "X is..." / "X refers to..." patterns | ✅ | No definitions |
|
|
52
|
+
| Unique data not found elsewhere | ✅ | Commonly available info |
|
|
53
|
+
|
|
54
|
+
### 2. Structural Readability (20%)
|
|
55
|
+
|
|
56
|
+
92% of AI Overview citations come from top-10 pages, but 47% come from pages below position 5 — demonstrating different selection logic.
|
|
57
|
+
|
|
58
|
+
| Signal | Strong | Weak |
|
|
59
|
+
|--------|--------|------|
|
|
60
|
+
| Clean H1→H2→H3 hierarchy | ✅ | Wall of text |
|
|
61
|
+
| Question-based headings | ✅ | Vague headings |
|
|
62
|
+
| Short paragraphs (2-4 sentences) | ✅ | Long unbroken paragraphs |
|
|
63
|
+
| Tables for comparative data | ✅ | No structured data display |
|
|
64
|
+
| Lists for multi-item content | ✅ | Inline lists in sentences |
|
|
65
|
+
|
|
66
|
+
### 3. Multi-Modal Content (15%)
|
|
67
|
+
|
|
68
|
+
Content with multi-modal elements sees **156% higher selection rates**.
|
|
69
|
+
|
|
70
|
+
- Text + relevant images
|
|
71
|
+
- Video content (embedded or linked)
|
|
72
|
+
- Infographics and charts
|
|
73
|
+
- Interactive tools (calculators, assessments)
|
|
74
|
+
- Structured data supporting media
|
|
75
|
+
|
|
76
|
+
### 4. Authority & Brand Signals (20%)
|
|
77
|
+
|
|
78
|
+
- Author byline with credentials
|
|
79
|
+
- Publication and last-updated dates
|
|
80
|
+
- Citations to primary sources
|
|
81
|
+
- Organization credentials
|
|
82
|
+
- Entity presence in Wikipedia, Wikidata
|
|
83
|
+
- Active presence on Reddit, YouTube, LinkedIn
|
|
84
|
+
|
|
85
|
+
### 5. Technical Accessibility (20%)
|
|
86
|
+
|
|
87
|
+
**AI crawlers do NOT execute JavaScript** — SSR is critical.
|
|
88
|
+
|
|
89
|
+
- Server-side rendering for core content
|
|
90
|
+
- AI crawler access in robots.txt
|
|
91
|
+
- llms.txt file presence
|
|
92
|
+
- RSL 1.0 licensing terms
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
## AI Crawler Registry
|
|
97
|
+
|
|
98
|
+
| Crawler | Owner | Purpose | Recommend |
|
|
99
|
+
|---------|-------|---------|-----------|
|
|
100
|
+
| GPTBot | OpenAI | ChatGPT web search + training | Allow |
|
|
101
|
+
| OAI-SearchBot | OpenAI | OpenAI search features | Allow |
|
|
102
|
+
| ChatGPT-User | OpenAI | ChatGPT browsing | Allow |
|
|
103
|
+
| ClaudeBot | Anthropic | Claude web features | Allow |
|
|
104
|
+
| PerplexityBot | Perplexity | Perplexity search | Allow |
|
|
105
|
+
| Applebot-Extended | Apple | Apple Intelligence features | Allow |
|
|
106
|
+
| Google-Extended | Google | Gemini training (NOT Search) | Optional |
|
|
107
|
+
| CCBot | Common Crawl | Open dataset training | Optional/Block |
|
|
108
|
+
| Bytespider | ByteDance | TikTok/Douyin AI training | Block |
|
|
109
|
+
| anthropic-ai | Anthropic | Claude training | Optional |
|
|
110
|
+
| cohere-ai | Cohere | Cohere models | Optional |
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
## llms.txt Standard
|
|
115
|
+
|
|
116
|
+
File at `/llms.txt` (domain root). Provides structured guidance to AI crawlers.
|
|
117
|
+
|
|
118
|
+
```
|
|
119
|
+
# Site Name
|
|
120
|
+
> One-line description
|
|
121
|
+
|
|
122
|
+
## Main Sections
|
|
123
|
+
- [Page Title](url): Description
|
|
124
|
+
- [Another Page](url): Description
|
|
125
|
+
|
|
126
|
+
## Key Facts
|
|
127
|
+
- Important fact 1
|
|
128
|
+
- Important fact 2
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
Also check for `/llms-full.txt` (expanded version).
|
|
132
|
+
|
|
133
|
+
---
|
|
134
|
+
|
|
135
|
+
## RSL 1.0 (Really Simple Licensing)
|
|
136
|
+
|
|
137
|
+
Machine-readable AI licensing standard (December 2025).
|
|
138
|
+
Backed by: Reddit, Yahoo, Medium, Quora, Cloudflare, Akamai, Creative Commons.
|
|
139
|
+
|
|
140
|
+
Check for RSL implementation and appropriate licensing terms.
|
|
141
|
+
|
|
142
|
+
---
|
|
143
|
+
|
|
144
|
+
## Quick Wins for AI Visibility
|
|
145
|
+
|
|
146
|
+
### Immediate (1 day)
|
|
147
|
+
1. Add "What is [topic]?" definition in first 60 words of key pages
|
|
148
|
+
2. Create 134–167 word self-contained answer blocks
|
|
149
|
+
3. Add question-based H2/H3 headings
|
|
150
|
+
4. Include specific statistics with source attribution
|
|
151
|
+
5. Add publication and update dates
|
|
152
|
+
6. Allow key AI crawlers in robots.txt (GPTBot, ClaudeBot, PerplexityBot)
|
|
153
|
+
|
|
154
|
+
### Short-term (1 week)
|
|
155
|
+
1. Create `/llms.txt` file
|
|
156
|
+
2. Add author bios with credentials + Wikipedia/LinkedIn links
|
|
157
|
+
3. Implement Person and Organization schema
|
|
158
|
+
4. Add comparison tables with structured data
|
|
159
|
+
5. Ensure SSR for all critical content
|
|
160
|
+
|
|
161
|
+
### Strategic (1-3 months)
|
|
162
|
+
1. Build Wikipedia presence for brand and key people
|
|
163
|
+
2. Create original research or surveys (unique citability)
|
|
164
|
+
3. Establish active YouTube channel
|
|
165
|
+
4. Build Reddit community presence
|
|
166
|
+
5. Implement comprehensive entity linking (sameAs across platforms)
|
|
167
|
+
6. Develop unique tools, calculators, or interactive content
|