/seo-geo
Use when optimizing for AI search engines (GEO) — AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot readiness.
$ npx -y skills add fusengine/agents --skill seo-geo --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/seo-geo
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when optimizing for AI search engines (GEO) — AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot readiness.
SKILL.md
seo-geo.SKILL.mdname: seo-geo
description: Use when optimizing for AI search engines (GEO) — AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot readiness.
user-invocable: false
related-skills: seo, seo-content, seo-featured-snippets, seo-schema
<objective> Covers Generative Engine Optimization (GEO) 2026 for the six target AI engines (Google AI Overviews, ChatGPT with web search, Perplexity, Claude with web search, Gemini, Bing Copilot). Documents the `scripts/geo-score.ts` LLM-readiness scoring (0-100 across 10 weighted signals), quantified impact data (statistics/authoritative citations/expert quotes boost AI visibility up to +40%; keyword stuffing costs -10%), the recommended content structure for LLM extraction, and llms.txt placement (ignored by Google's crawlers, useful for other LLMs). Distinct from seo-featured-snippets (position-0 HTML recipes) and seo-entity (the schema/salience signals that feed AI citations). </objective>
GEO — Generative Engine Optimization 2026
Target Engines
- **Google AI Overviews** (formerly SGE)
- **ChatGPT** with web search
- **Perplexity**
- **Claude** with web search
- **Gemini**
- **Bing Copilot**
LLM-Readiness Score (0-100)
`scripts/geo-score.ts` checks:
| Signal | Points | |--------|--------| | Quick answer in first 100 words | 15 | | Direct H2 questions ("What is X?") | 10 | | Tables/lists for comparable data | 10 | | Citations with dates + sources | 15 | | Statistics with attribution | 10 | | Author bio with credentials | 10 | | Schema.org markup | 10 | | Updated date < 12 months | 10 | | llms.txt present | 5 | | No JS-only content (SSR) | 5 |
Quantified Impact (Princeton / 2026 studies)
GEO techniques boost AI visibility by up to **+40%**. Ranked by impact:
| Technique | Visibility | |-----------|-----------| | Adding statistics | +40% | | Citing authoritative sources | +40% | | Quoting experts | +28% | | Improving text fluency | +15–30% | | Keyword stuffing | **-10%** (worse than baseline) |
AI Overviews cite **~13 sources on average** per answer (2026); 59.6% of citations come from URLs outside the top-20 organic results.
Content Structure for LLMs
# <Topic>
**Quick answer** (40-60 words, factual, no fluff)
## What is <topic>?
Definition paragraph...
## Why does it matter?
Stats with sources...
## How to <task>?
Numbered steps...
## Comparison
| X | Y |
|---|---|
## FAQ
- Q: ...
- A: ...
llms.txt
**Not required by Google** (its crawlers ignore it) — useful for other LLMs, where early adopters report improved citation accuracy. Place at site root: `https://example.com/llms.txt`
# Site Name
> One-line description
## Pages
- [Homepage](https://example.com/): description
- [Docs](https://example.com/docs/): description
References
- `seo-entity` — entity signals + schema that drive AI citations
- `skills/seo/04-geo-2026/` (ai-platforms, citation-strategies, content-structure, llm-crawlability, zero-click-optimization)
- `skills/seo/08-measurement/share-of-model.md`
Read more
name: seo-geo description: Use when optimizing for AI search engines (GEO) — AI Overviews, ChatGPT, Perplexity, Claude, Gemini, Copilot readiness. user-invocable: false related-skills: seo, seo-content, seo-featured-snippets, seo-schema
<objective> Covers Generative Engine Optimization (GEO) 2026 for the six target AI engines (Google AI Overviews, ChatGPT with web search, Perplexity, Claude with web search, Gemini, Bing Copilot). Documents the `scripts/geo-score.ts` LLM-readiness scoring (0-100 across 10 weighted signals), quantified impact data (statistics/authoritative citations/expert quotes boost AI visibility up to +40%; keyword stuffing costs -10%), the recommended content structure for LLM extraction, and llms.txt placement (ignored by Google's crawlers, useful for other LLMs). Distinct from seo-featured-snippets (position-0 HTML recipes) and seo-entity (the schema/salience signals that feed AI citations). </objective>
GEO — Generative Engine Optimization 2026
Target Engines
- **Google AI Overviews** (formerly SGE)
- **ChatGPT** with web search
- **Perplexity**
- **Claude** with web search
- **Gemini**
- **Bing Copilot**
LLM-Readiness Score (0-100)
`scripts/geo-score.ts` checks:
| Signal | Points | |--------|--------| | Quick answer in first 100 words | 15 | | Direct H2 questions ("What is X?") | 10 | | Tables/lists for comparable data | 10 | | Citations with dates + sources | 15 | | Statistics with attribution | 10 | | Author bio with credentials | 10 | | Schema.org markup | 10 | | Updated date < 12 months | 10 | | llms.txt present | 5 | | No JS-only content (SSR) | 5 |
Quantified Impact (Princeton / 2026 studies)
GEO techniques boost AI visibility by up to **+40%**. Ranked by impact:
| Technique | Visibility | |-----------|-----------| | Adding statistics | +40% | | Citing authoritative sources | +40% | | Quoting experts | +28% | | Improving text fluency | +15–30% | | Keyword stuffing | **-10%** (worse than baseline) |
AI Overviews cite **~13 sources on average** per answer (2026); 59.6% of citations come from URLs outside the top-20 organic results.
Content Structure for LLMs
# <Topic> **Quick answer** (40-60 words, factual, no fluff) ## What is <topic>? Definition paragraph... ## Why does it matter? Stats with sources... ## How to <task>? Numbered steps... ## Comparison | X | Y | |---|---| ## FAQ - Q: ... - A: ...
llms.txt
**Not required by Google** (its crawlers ignore it) — useful for other LLMs, where early adopters report improved citation accuracy. Place at site root: `https://example.com/llms.txt`
# Site Name > One-line description ## Pages - [Homepage](https://example.com/): description - [Docs](https://example.com/docs/): description
References
- `seo-entity` — entity signals + schema that drive AI citations
- `skills/seo/04-geo-2026/` (ai-platforms, citation-strategies, content-structure, llm-crawlability, zero-click-optimization)
- `skills/seo/08-measurement/share-of-model.md`
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

