aeo-audit

# AEO

Website: [ainyc.ai](https://ainyc.ai)

Audit and improve how AI systems understand, extract, and cite a website.

## What It Covers

- Full AEO audits and score reviews
- Code fixes for weak or missing AEO signals
- JSON-LD and schema validation
- `llms.txt` and `llms-full.txt` generation
- Before-vs-after tracking and competitor comparisons

## Common Requests

- `Audit https://example.com`
- `Fix AEO issues for https://example.com in this repo`
- `Validate schema for https://example.com`
- `Generate llms.txt for this project`
- `Compare https://site-a.com --compare https://site-b.com`

## Mode Selection

- Use `Audit` for grading, diagnosis, and benchmarking.
- Use `Fix` when the user wants code changes.
- Use `Schema` for JSON-LD, missing properties, or entity consistency.
- Use `llms.txt` when the user wants AI-readable markdown files.
- Use `Monitor` for progress tracking or competitor comparisons.

## Audit

Use for broad requests such as "audit this site" or "why am I not being cited?"

1. Run:
   ```bash
   npx @ainyc/aeo-audit@latest $ARGUMENTS --format json
   ```
2. Return:
   - Overall grade and score
   - Short summary
   - Factor breakdown
   - Top strengths
   - Top fixes
   - Metadata such as fetch time and auxiliary file availability

## Fix

Use when the user wants code changes applied after the audit.

1. Run:
   ```bash
   npx @ainyc/aeo-audit@latest $ARGUMENTS --format json
   ```
2. Find factors with status `partial` or `fail`.
3. Apply targeted fixes in the current codebase.
4. Prioritize:
   - Structured data and schema completeness
   - `llms.txt` and `llms-full.txt`
   - `robots.txt` crawler access
   - E-E-A-T signals
   - FAQ markup
   - freshness metadata
5. Re-run the audit and report the score delta.

Rules:
- Do not remove existing schema or content unless the user asks.
- Preserve existing code style and patterns.
- If a fix is ambiguous or high-risk, explain the tradeoff before editing.

## Schema

Use when the request is spe...