How AEOForged re-measured its own agent readiness

Ryan KingsFounder & CTO

Published June 2026 · 6 min read

Corrected 2026-11-04: earlier versions quoted Cloudflare, Lighthouse and FORKOFF scores that came from our own approximation of those tools, not from the tools themselves.

How AEOForged re-measured its own agent readiness

AEOForged used its own agent readiness check on its own site. The June 2026 write-up stated a before figure from an earlier version of these checks. That version is what this correction replaced. The before state cannot be re-measured, so this page does not repeat it.

What does the repaired check say?

On 2026-11-04 the repaired check of aeoforged.com reported:

• Protocols found: 19 of 27 that apply to this site.
• Read score 100. 5/5 agent probes reached the homepage; discovery 4/4 (robots access, sitemap, machine-readable content, structured data).

This page does not quote a Cloudflare, Lighthouse, or FORKOFF score. Those earlier percentages were our approximation. We did not run those tools for this correction.

What was deployed?

The sprint added discovery files and middleware on the live site. The current paths are:

1. robots.txt with a wildcard User-agent: * group and a Content-Signal line. A named group is only for a bot that should be treated differently.
2. Auto-discovery links for llms.txt, /.well-known/agents.json, and the sitemap.
3. Content negotiation middleware that can return text/markdown when the request asks for it.
4. agents.json and agent-permissions.json under /.well-known/.
5. An A2A Agent Card at /.well-known/agent-card.json that declares supportedInterfaces.
6. OAuth discovery for authenticated API endpoints.

agent-instructions.md has no published spec and is not a scored file. /.well-known/agent.json is not the A2A 1.0 card.

The sprint took about 6 hours. AEOForge's generator produced the manifest files. The figure above is the 2026-11-04 re-check, not a claim that every generated file was already live in June.

What should you learn from this case study?

1. Content readiness and agent readiness are different checks. A content score does not say whether agents can fetch the site.
2. Earlier published percentages for Cloudflare, Lighthouse, and FORKOFF on this page were not those tools' results.
3. A protocol counts only when it applies to the site and the probe finds it. On 2026-11-04 that was 19 of 27 for aeoforged.com.

Key takeaways

• The before figure from the June 2026 write-up came from the earlier version of these checks. It is not repeated here.
• On 2026-11-04, aeoforged.com: Protocols found: 19 of 27 that apply to this site. Read score 100.
• Re-run aeo_agent_ready on aeoforged.com to see the current check. This page does not report another tool's score.