95347d2e47
Refactor the monolithic seo-analyzer into two specialist agents orchestrated in parallel by the /seo skill, plus a standalone /geo skill for AI-only audits. Changes - agents/seo-analyzer.md: refocused on classical engines (Google, Bing, DuckDuckGo). Adds Core Web Vitals 2.0 (LCP/INP/CLS + VSI), CSP + full security headers, hreflang audit, video SEO (transcripts), accessibility as ranking signal, image/video sitemaps. - agents/geo-analyzer.md: new agent for AI engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews, Copilot). Covers AI crawler policy, llms.txt/llms-full.txt, Schema.org for AI extraction (QAPage, Speakable, Person+Article, Organization graph), entity SEO (Wikidata, sameAs, Knowledge Panel), content shape (Definition Lead, TL;DR, Q->A, citable stats, freshness), AI visibility testing. - agents/resources/: shared knowledge base referenced by both agents — ai-crawlers-2026.md (25+ bots, training vs retrieval categories, permissive/restrictive templates), llms-txt-template.md, geo-schemas.md (incl. deprecated list: ClaimReview, CourseInfo, etc. removed June 2025), entity-seo.md, content-shape-for-ai.md, ai-visibility-tools.md, automation-catalog.md. - skills/seo/SKILL.md: becomes parallel dispatcher. Collects context once (depth + business), spawns both agents in a single message for concurrent execution, merges envelopes into unified SEO.md. Includes authoritative file-ownership matrix to prevent parallel-edit races. - skills/geo/SKILL.md: new standalone wrapper for GEO-only audits. Scoring - Combined score: GLOBAL = 0.80 * SEO + 0.20 * GEO (local B2C), 0.75 * SEO + 0.25 * GEO (SaaS/national/content). - GEO axis weight raised from 5% (old) to first-class dimension. Policy - AI crawlers: permissive default (maximise AI citations). Restrictive template available for premium/regulated content. - Every user action in SEO.md section 11 must cite automation options from automation-catalog.md. Tools - WebFetch + WebSearch added to allowed-tools of both skills and both agents (needed for live CWV via PageSpeed API, AI visibility testing, Wikidata/Knowledge Panel lookups, competitor analysis). Research basis (2026 state of the art validated via WebSearch): - Core Web Vitals 2.0 (VSI signal, Google core update March 2026) - AI Overviews trigger on ~48% of Google searches - ClaimReview + 6 other schema types deprecated June 2025 - Definition Lead Architecture (CMU KDD 2024, +impression score) - Citations + stats add up to 40% AI visibility (Aggarwal 2024) - Wikidata grounds every major LLM (ChatGPT, Claude, Gemini, Perplexity) Backup - agents/seo-analyzer.md.bak kept for rollback reference. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1.6 KiB
1.6 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 SEO.md already exists at project root, 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 SEO.md exists, the agent writes GEO.md at project root.