auditlisted

# Audit Score a site across four layers — SEO, AEO, GEO, and crawl hygiene — and produce a prioritised, actionable fix list. ## When to use Anything shaped like "is this site discoverable?" Ranking complaints, schema questions, pre-deploy verification, or "why doesn't ChatGPT cite us?" ## When NOT to use - Generating `llms.txt` / `facts.json` — that is `geo-artifacts`. - Writing schema or AnswerBlocks — that is `aeo-onpage` *(planned, not in v0.1.0)*. - Submitting URLs for indexing — that is `indexing` *(planned, not in v0.1.0)*. - Off-site, backlink, or entity work — that is `offsite-entity` *(planned, not in v0.1.0)*. Audit only diagnoses. It never edits the site. `omnirank fix` shows the diff it would apply for the four `mechanical` findings and writes nothing — there is no `--write` flag. Run it to answer "which file is wrong?", then hand the diff to a human. ## How to run it ```bash # Zero-config, any live site python3 -m omnirank.cli audit https://example.com # Configured repo, CI-ready python3 -m omnirank.cli audit --config omnirank.config.json --fail-on h1 canonical schema ``` Exit codes: `0` clean, `1` a configured gate failed, `2` usage or config error. The JSON report lands in `.omnirank/reports/<date>-audit.json`. `--fail-on` takes **gate names** (`h1`, `canonical`, `title-length`, `llms-txt`, `facts-json`, `schema`, ...), not finding ids — see `references/gates.md` for the full name list and how ids relate to them. ## Reading the output Work finding