ai-search-readinesslisted

# AI Search Readiness Audit Run a technical audit of how ready a site is to be crawled, understood, and cited by AI crawlers and answer engines — as opposed to traditional search engine crawlers, which `/seo-audit` already covers. ## When to use this vs. /seo-audit - `/seo-audit` — titles, meta descriptions, canonicals, sitemaps, PageSpeed/Core Web Vitals. - `/ai-search-readiness` (this skill) — AI-bot-specific robots.txt rules, llms.txt, structured data as an AI-citation signal, and JS-rendering dependency (many AI crawlers do not execute JavaScript). They're complementary — run both for a full picture. If the user asks for "AI readiness," "AI SEO," "AI search," or similar, use this skill. If they cross-reference Google Analytics, also check for an "AI Assistant" / AI-referral channel in GA4 (via `/ga-report`) as a real-world signal that AI tools are already sending traffic. ## Steps ### 1. Identify URL and pages Use the URL from the invocation argument. Default to the homepage; add up to 5 project-specific pages if the user names them or if the project's CLAUDE.md identifies key content pages (evergreen educational/guide content is the highest-value target — that's what AI answer engines cite most). ### 2. Determine output path Save alongside other audits for this engagement — typically `context/ai-search/ai-search-readiness-{YYYY-MM-DD}.md` in the current project directory, or the equivalent working folder if this is prospecting/portfolio research rather than