7b57b2e091
Before: SEO.md, GEO.md, HARDEN.md, VALIDATE.md, BUGS-FOUND.md landed
at project root. After: all five go to .claude/audits/. Covers both
dispatcher write paths and the dispatcher bash commands that parse
each report (test -s, grep score, wc) — otherwise the dispatcher
would look for the file at the old location.
- skills/seo,geo,harden,validate,code-clean — write paths + console
summaries ("Report: .claude/audits/X.md")
- skills/harden,validate — bash parsing commands (test/grep/wc) aligned
- agents/seo-analyzer,validator-analyzer,code-cleaner — agent-side refs
- agents/validator-analyzer frontmatter description updated
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.7 KiB
1.7 KiB
| name | description | argument-hint | allowed-tools | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| geo | Standalone GEO (Generative Engine Optimization) audit for AI search engines: ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, Microsoft Copilot, Brave AI, DuckAssist, You.com, Apple Intelligence. Audits AI crawler directives, llms.txt / llms-full.txt, Schema.org types optimised for AI extraction (QAPage, Speakable, Person+Article, HowTo, Organization graph), entity SEO (Wikidata, sameAs, @id, Knowledge Panel), content shape for LLM extraction (Definition Lead, TL;DR, Q→A structure, citable stats, freshness), and live AI visibility monitoring. For full SEO + GEO combined audit → use /seo (runs seo + geo in parallel). For classical SEO only → use /seo and skip the GEO section. Trigger: "geo", "AI search", "ChatGPT visibility", "Perplexity optimisation", "llms.txt", "AI crawlers", "Google AI Overview", "entity SEO", "Wikidata", "generative engine optimization", "référencement IA", "optimisation IA". | optional keywords/scope, e.g. "SaaS B2B content GEO" or "audit llms.txt et entity SEO" |
|
Load and follow strictly:
- $HOME/.claude/agents/geo-analyzer.md
Execute the GEO-ANALYZER agent on the following target:
$ARGUMENTS
Note on integration
If .claude/audits/SEO.md already exists, the geo-analyzer will
merge its findings into that file's §7 — Optimisation GEO / IA
section (rather than writing a separate GEO.md). This keeps a
single consolidated report when both /seo and /geo have been run.
If no .claude/audits/SEO.md exists, the agent writes .claude/audits/GEO.md (run mkdir -p .claude/audits first).