12 AEO Best Practices for docs

Description and use

<p>If you've watched a coding agent quietly read your documentation, run a command based on what it found there, and never once render the page in a browser, you've seen the audience this post is about. Nobody clicked a link. Nobody looked at your carefully designed nav bar. An agent fetched a URL, parsed it, and acted.</p> <p>In January 2025, we made a small change to <a href="https://docs.expo.dev/" rel="noopener noreferrer">Expo documentation</a> that turned out to matter more than we expected at the time: we added support for a curated text file served publicly, called <code>llms.txt</code

Problem

<p>If you've watched a coding agent quietly read your documentation, run a command based on what it found there, and never once render the page in a browser, you've seen the audience this post is about. Nobody clicked a link. Nobody looked at your carefully designed nav bar. An agent fetched a URL, parsed it, and acted.</p> <p>In January 2025, we made a small change to <a href="https://docs.expo.dev/" rel="noopener noreferrer">Expo documentation</a> that turned out to matter more than we expected at the time: we added support for a curated text file served publicly, called <code>llms.txt</code

Outcome

<p>If you've watched a coding agent quietly read your documentation, run a command based on what it found there, and never once render the page in a browser, you've seen the audience this post is about. Nobody clicked a link. Nobody looked at your carefully designed nav bar. An agent fetched a URL, parsed it, and acted.</p> <p>In January 2025, we made a small change to <a href="https://docs.expo.dev/" rel="noopener noreferrer">Expo documentation</a> that turned out to matter more than we expected at the time: we added support for a curated text file served publicly, called <code>llms.txt</code

Evidence

12 AEO Best Practices for docs

Source