aeo
Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- License 许可
- MIT
- 最近更新
- 2026-08-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- aeo
- description
- Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
02 资源文件 9
- 参考文档.claude-plugin/plugin.json1.9 KB
- 参考文档references/aeo_eeat_canon.md9.5 KB
- 参考文档references/aeo_vs_seo.md8.5 KB
- 参考文档references/bot_access_and_monitoring.md6.7 KB
- 参考文档references/extractable_content_patterns.md10.2 KB
- 参考文档references/llm_citation_patterns.md8.4 KB
- 脚本scripts/aeo_audit.py17.0 KB
- 脚本scripts/aeo_optimizer.py10.8 KB
- 脚本scripts/citation_tracker.py12.3 KB
03 SKILL.md 正文
Answer Engine Optimization (AEO)
Get your content cited by ChatGPT, Perplexity, Claude, Gemini, and Mistral as the authoritative source.
AEO is the practice of optimizing content for citation in LLM-generated responses — distinct from SEO, which optimizes for search rankings. This skill audits, optimizes, and tracks AEO performance.
Distinct From SEO
| SEO | AEO | |
|---|---|---|
| Optimizes for | Click-through rankings | Being cited as authoritative source |
| Audience | Humans browsing search results | LLMs answering questions |
| Success metric | Position 1-10, organic traffic | Citation count across LLMs |
| Key signals | Backlinks, keywords, page speed | E-E-A-T, structured data, factual density |
| Update cadence | Weeks-to-months | Days-to-weeks (LLM training cycles) |
Both can coexist — the same content can rank #1 on Google AND get cited by Perplexity. But the techniques differ: SEO rewards keyword density + backlinks; AEO rewards primary-source signals + structured facts.
When To Use
- Planning a new content piece for an AI-first audience
- Auditing existing content for E-E-A-T gaps before AI Overview rollout
- Tracking which pages get cited by which LLM (citation ledger)
- Researching what queries LLMs cite sources for (vs. what they answer from training)
- Benchmarking against competitors' citation rates
- Building a long-term AEO strategy aligned with traditional SEO
When NOT To Use
- Pure click-through SEO without LLM-citation intent — use
marketing-skill/skills/seo-auditinstead - Brand-voice content with no factual claims — citations require facts to cite
- Content for a topic where LLMs already have strong training signal (e.g., elementary math) — citation upside is minimal
- Time-sensitive content (breaking news) — LLM training lag means citations come months later
Core Capabilities
1. Content audit + E-E-A-T scoring
The auditor (aeo_audit.py) scores content across 4 dimensions:
- Experience: First-person evidence, dated examples, case studies, "We ran X in 2026" claims
- Expertise: Author bio, credentials, citations to peer-reviewed sources, technical depth
- Authoritativeness: External backlinks from authority domains, schema.org markup, structured data
- Trustworthiness: HTTPS, contact info, transparent corrections, factual density (number of verifiable claims per 1000 words)
Composite score 0-100 with per-dimension breakdown. Output: markdown report with specific fix recommendations.
2. Content optimization
The optimizer (aeo_optimizer.py) generates AEO-improved variants:
- Structure rewrite — H2/H3 hierarchy optimized for LLM parsing
- Citation density boost — adds
[1]-style references with sources - Schema injection — generates JSON-LD for FAQ, HowTo, Article schemas
- Fact-first lede — moves verifiable claims into the first 200 words
Three modes: conservative (touch <10% of words), balanced (touch <30%), aggressive (rewrite for maximum AEO).
3. Citation tracking
The tracker (citation_tracker.py) maintains a local ledger of citations:
- Manual entry: paste a citation found in ChatGPT/Perplexity/Claude/Gemini output
- Track which URL, which LLM, which query, what date
- Compute per-page citation count, citation velocity, LLM coverage
- Export to CSV for reporting
Stores in ~/.aeo-data/citations.json (local, no telemetry).
References
references/aeo_eeat_canon.md— E-E-A-T methodology, industry thresholds, anti-patternsreferences/llm_citation_patterns.md— per-LLM citation selection heuristics (Perplexity, ChatGPT, Claude, Gemini, Mistral)references/aeo_vs_seo.md— when to invest in AEO vs SEO vs bothreferences/bot_access_and_monitoring.md— AI crawler robots.txt matrix (the prerequisite check: a blocked bot zeroes that platform), Google Search Console AI Overviews monitoring, manual testing protocols, citation-drop diagnostic (merged from the formerai-seoskill)references/extractable_content_patterns.md— 7 copy-ready block templates (definition, steps, table, FAQ, attributed stat, expert quote, summary box) that answer engines reliably extract (merged from the formerai-seoskill)
Workflow
0. Pre-flight: bot access
Check robots.txt against the crawler matrix in references/bot_access_and_monitoring.md
→ a blocked GPTBot/PerplexityBot/ClaudeBot/Google-Extended is the first fix, always
1. Audit existing content
$ python3 scripts/aeo_audit.py --url https://example.com/blog/post
→ markdown report with composite score + 4-dimension breakdown
2. Apply optimization recommendations
$ python3 scripts/aeo_optimizer.py --input post.md --mode balanced --output post-aeo.md
→ optimized variant with citations + schema + structural fixes
3. Publish + monitor
$ python3 scripts/citation_tracker.py --action add --url https://example.com/blog/post \
--llm perplexity --query "what is AEO" --date 2026-05-17
→ adds entry to local citations.json ledger
4. Report
$ python3 scripts/citation_tracker.py --action report --url https://example.com/blog/post
→ per-page citation stats: count, LLMs, queries, velocity
Configuration
The skill is industry-aware via per-run --industry flag. Supported: saas, healthcare, finance, legal, ecommerce, b2b, media, education.
Industry affects:
- Authority signal requirements — healthcare/finance need stricter source citations
- Fact-checking rigor — legal/healthcare flag unverifiable claims as critical
- Citation style — academic vs. trade-journal vs. blog conventions
Example:
python3 scripts/aeo_audit.py --url <url> --industry healthcare
# → stricter E-E-A-T thresholds; flags any health claim without primary citation
Output Format
Markdown audit report (default)
# AEO Audit Report — [Page Title]
**URL:** https://example.com/blog/post
**Date:** 2026-05-17
**Industry:** saas
**Composite Score:** 72/100 (B+)
## Dimension Breakdown
| Dimension | Score | Verdict |
|---|---|---|
| Experience | 80/100 | Strong — first-person case study present |
| Expertise | 65/100 | Author bio missing credentials |
| Authoritativeness | 75/100 | 4 backlinks from authority domains |
| Trustworthiness | 68/100 | No corrections policy linked |
## Top 3 Fixes
1. Add author bio with credentials (Expertise +15)
2. Link to corrections policy from footer (Trustworthiness +12)
3. Inject FAQ schema for the 5 questions implicit in H2s (Authoritativeness +8)
## All Recommendations
[...]
## Audit Trail
[3-count of analysis steps, sources cited, time taken]
JSON for pipelines
python3 scripts/aeo_audit.py --url <url> --output json
Returns full structured data for integration with content management workflows.
Industry-Specific E-E-A-T Thresholds
| Industry | Min Composite | Critical Signals |
|---|---|---|
| Healthcare | 85 | Medical reviewer byline, peer-reviewed citations, FDA disclosure |
| Finance | 85 | Author CFA/CPA credentials, "not investment advice" disclaimer, dated examples |
| Legal | 85 | Jurisdiction disclosed, attorney bio, "not legal advice" disclaimer |
| SaaS | 70 | Product manager byline, case study with metrics, ROI calculator |
| E-commerce | 65 | Product reviews aggregated, return policy, schema.org Product |
| B2B | 70 | Industry analyst quotes, customer logos, ROI data |
| Media | 70 | Editorial policy, fact-check link, original reporting |
| Education | 75 | Instructor bio, learning outcomes, accreditation if applicable |
Anti-Patterns Rejected
- Keyword stuffing for AI — LLMs already extract topic from semantics; keyword density doesn't boost citation likelihood
- Pure AI-generated content with no human review — generic LLM output gets de-prioritized by RAG retrieval algorithms looking for distinctive signal
- Citation farms / link wheels — modern LLM RAG penalizes low-authority linked networks
- Schema spam — false or unverifiable schema.org claims get filtered; only mark up real, verifiable claims
- Optimizing for one LLM at expense of others — citation distributions are highly correlated across major LLMs because they share training data sources; optimize for the shared signals (E-E-A-T) not per-LLM hacks
- Ignoring SEO entirely — AEO citations often originate from sources that already rank well organically; AEO and SEO are complements, not substitutes
Dependencies
- stdlib-only for all 3 scripts — no
pip installrequired - Optional:
requests+beautifulsoup4if--urlmode used (otherwise pass markdown via--inputfor file-based audits) - Optional: any LLM API key for
query_researchmode (currently scaffold-only — full LLM-driven query research is roadmap)
Storage
All data is local-first:
~/.aeo-data/citations.json— citation ledger~/.aeo-data/patterns.json— success patterns library~/.aeo-data/audits/<hash>.md— saved audit reports
No telemetry. No cloud sync. Export to CSV anytime via citation_tracker.py --action export.
Trigger Phrases
- "AEO audit", "AEO check"
- "optimize for ChatGPT / Perplexity / Claude / Gemini"
- "get cited by [LLM]"
- "LLM citation strategy"
- "answer engine optimization"
- "content for AI search"
- "E-E-A-T audit"
- "track AI citations"
- "schema for AI"
Related Skills
marketing-skill/skills/seo-audit— traditional click-through SEOmarketing-skill/skills/programmatic-seo— template-driven SEO at scalemarketing-skill/skills/content-strategy— broader content planningmarketing-skill/skills/copywriting— voice + tonemarketing-skill/skills/schema-markup— structured data implementation
Version: 2.7.3
Source: Ported from alirezarezvani/aeo-box (answer-engine-optimization/ skill, 2,464 LOC across 9 modules). This port distills the 9-module Python toolkit into 3 stdlib CLI tools per the claude-skills convention; preserves the E-E-A-T scoring methodology, citation-tracking schema, and industry-aware thresholds verbatim.
License: MIT (matches upstream + this repo).
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.