AI coding agents consume documentation fundamentally differently from humans. If you're still optimizing only for human readers, you're leaving a growing sha...

Addy's platform is a resource for web developers and performance enthusiasts, offering insights into web performance optimization, browser rendering, and front-end development techniques. Through articles, tools, and case studies, Addy offers insights into measuring and improving web page speed and user experience. Developers can learn about performance budgets, lazy loading, and optimizing web assets to create fast and responsive websites.

Addy Osmani

Agentic Engine Optimization (AEO) is a new discipline for structuring technical documentation so AI coding agents can effectively discover, parse, and use it. Unlike human readers, agents like Claude Code, Cursor, and Cline compress multi-page navigation into single HTTP requests, bypass all client-side analytics, and silently discard content that exceeds their context windows. Key AEO practices include: auditing robots.txt to allow AI agent traffic, adding an llms.txt sitemap for agent discovery, writing skill.md files that declaratively describe API capabilities, keeping documentation pages under token limits (15K–25K tokens for most pages), serving clean Markdown alongside HTML, surfacing token counts as metadata, adding 'Copy for AI' buttons, and creating AGENTS.md files in repositories. A companion open-source audit tool called agentic-seo automates checking for these signals.

Agentic Engine Optimization (AEO)

How AI agents actually read your documentation

The token problem: your docs may be invisible to agents

The broader implications for developer experience

<p>**No major LLM provider has formally adopted llms.txt **as part of their crawler protocol. And Google has clearly stated that they aren’t going to use it. Despite the marketing hype, it has zero effect in the real world.</p>
