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.
Table of contents
What is Agentic Engine Optimization?How AI agents actually read your documentationThe token problem: your docs may be invisible to agentsThe AEO stack: what to actually buildAGENTS.md: the emerging defaultMonitoring AI referral trafficThe broader implications for developer experienceAEO audit checklistWhere to startWrapping up6 Comments
Sort: