aeolisted

# AEO Audit the **named site** for Answer/Agent Engine Optimization: can AI crawlers reach it, can they read it without executing JavaScript, does its content chunk into citable answers, and do its signals support being resolved as a known entity. **Write no code, change no config.** The deliverable is findings plus a plan. **Use when:** you want to know why AI assistants don't cite the site, or whether a site is ready for AI search before launch. **NOT for:** classic SEO (rankings, backlinks, Core Web Vitals), auditing code quality (`/inspect`), or applying the fixes this audit proposes (`/build`, from the plan doc). State the target in one line so the user can interrupt: the URL, the repo (if the site's source is local), or both. ## Scope The named site, nothing else. No target → ask for the URL or the site's source directory; never guess. Two modes, used together when both are available: - **Live mode** — the deployed URL. Fetch it the way an AI crawler does. This is the only mode that catches WAF blocks, CDN bot rules, and rendering reality. - **Repo mode** — the site's source is the current repo. Read the framework config to determine the rendering mode, and the templates to check structure at the source. Repo mode alone cannot prove reachability — say so in the report if live mode was unavailable. Reading and fetching are unrestricted. **Editing is zero** — `/aeo` never modifies a file, a robots.txt, or a deployment. The user decides whether any of it gets