/claude-seo-ai:geo

The AI-search (GEO/AEO) subset of the audit. Read-only.

$ARGUMENTS = <url|path> [flags]. --pages N, --render static|auto|js (default static) and --feed <path> (the Agentic Commerce Protocol product feed; it only does anything when the e-commerce vertical is active, and without it M18.agentic.acp_feed_errors stays needs_api — an unread feed is never a clean feed) are forwarded to the orchestrator and reach audit.mjs unchanged. --probe and --gsc-ai-export are handled here, not by audit.mjs: they are probes — reported, never scored (severity 0, excluded from the AI Visibility score and from every cap).

What to do

Invoke seo-orchestrator with the target and flags and the instruction "AI path only": it acquires the snapshot with the scripts (never WebFetch), runs the deterministic checks, and dispatches ai-search-geo-specialist with M6 (seo-entity-linking), M11 (seo-geo-answerblocks), M12 (seo-geo-factdensity), M14 (seo-ai-crawlers — access + Google AI-feature eligibility), M21 (seo-ai-discovery — llms.txt, agents.md, UCP, agentic sitemap), M22 (seo-agent-readiness); plus M5 (seo-schema-jsonld, via schema-generator) and M4 (seo-rendering, via technical-auditor) because they feed AI visibility.
Run the probe flows below only when their flag is present.
Present from report.json: the AI Visibility score (band + interpretation), the citability breakdown by category, needs_api / manual_review counts, the prioritized GEO/AEO actions, any probes section (clearly separated from the score), and the report.md path.
Lead with the one thing Google documents: a page reaches AI Overviews / AI Mode by being indexed and snippet-eligible in Search (M14 ai_eligibility). Remind the user that M21 — llms.txt and the other discovery files — is reported at weight 0 (Google Search ignores llms.txt; vendor support is partial). Never write files; offer /claude-seo-ai:fix for the safe AUTO fixes (e.g. the AI-crawler robots.txt preset).