Distribution
- GitHub repository: Canonry/aeo-audit
- npm package: @ainyc/aeo-audit
- License: MIT
Public Toolkit
A public audit engine for the technical side of Answer Engine Optimization.
A public CLI and JavaScript library that audits 16 technical on-site factors we believe correlate with AI citation readiness. The tool scores only the on-site technical layer of AEO. Holistic AEO also depends on traditional SEO, content, and external linking. This tool represents our best working model for the on-site layer, not a guaranteed formula.
What Is Public Today
How To Use It
npx @ainyc/aeo-audit https://example.comnpx @ainyc/aeo-audit https://example.com --format jsonimport { runAeoAudit } from '@ainyc/aeo-audit'const report = await runAeoAudit('https://example.com', { includeGeo: false })16-Factor On-Site Technical Scope
Presence of LocalBusiness, FAQPage, Service, and HowTo schemas.
Word count, heading hierarchy, paragraph structure, and list usage.
Author meta, trust pages, credentials, and review-oriented trust signals.
FAQPage schema, question headings, and direct-answer formatting.
External references, authoritative links, and sameAs-style corroboration.
Property depth and richness across the structured data stack.
Naming consistency across schema, title tags, and on-page identity.
dateModified, Last-Modified, sitemap dates, and current copyright signals.
How easy the content is for answer engines to parse and cite.
llms.txt, llms-full.txt, robots.txt, and sitemap.xml availability.
Syntactic and semantic correctness of JSON-LD: required properties, valid types, and zero parse errors.
Direct definitions, step lists, and HowTo-style explanation blocks.
Brand mentions, founder references, and proper-noun density.
Canonical tags, meta descriptions, heading structure, image alt text, and core indexability signals.
Direct-answer formatting, lists, tables, and concise blocks that AI engines lift as inline citations.
robots.txt rules for GPTBot, ClaudeBot, PerplexityBot, and peers.
Project Links
Source code, issues, and project history.
Open repositoryInstall and run the package through npx or your own Node workflow.
Open npm packageSee how the project is evolving without mistaking roadmap items for shipped features.
What's Next
Directions we're exploring, not shipped features yet.
From Our Blog
Why Canonry published @ainyc/aeo-audit, what the 13-factor model measures, and what teams can learn from it.
Read the article