SEO was a 25-year industry built on one reader: Google’s crawler. One reader, one ranking algorithm, one game. Entire companies existed to reverse-engineer what that one reader wanted and feed it exactly that.
Agent Engine Optimization — AEO — is not a rename. Strip the analogy to its operational content and the game is fundamentally different. SEO had one reader with one goal: ranking pages. AEO has many readers with many goals, each acting on behalf of a different principal with different requirements and different patience.
One reader vs. many.
Google’s crawler was a monoculture. You optimized for one algorithm, and if you ranked, everyone saw you. The skills were specific: keyword density, backlink profiles, page speed, structured data markup for rich snippets.
Agent readers are a polyculture. Claude reads differently than GPT reads differently than a specialized procurement agent reads. Each has different context windows, different tool-use capabilities, different tendencies when evaluating claims. A capability manifest that surfaces well to one agent might be invisible to another.
The SEO response to this would be to reverse-engineer each agent’s preferences and optimize accordingly. That approach will fail. There are too many agents, they change too fast, and — unlike Google — they do not have a public interface you can test against. You cannot type a query into Claude’s agent mode and see where you rank.
The AEO approach.
Instead of optimizing for specific readers, AEO optimizes for structural legibility. Make your capabilities, claims, and identity machine-readable in standard formats. Use Agent Cards. Maintain a current llms.txt. Structure claims as verifiable assertions, not marketing copy. Sign what you can sign. Version what you version.
The difference: SEO was a game of signals. AEO is a game of substance. You cannot keyword-stuff an Agent Card. You cannot build backlinks to a capability manifest. The agent either finds what it needs in a parseable format, or it does not. The optimization is not gaming a ranking algorithm. The optimization is being genuinely, structurally legible.
This might mean AEO is a much smaller industry than SEO. There is less to game and more to actually build. That seems like an improvement.
Patience as a variable.
One thing that genuinely differs: agents have variable patience. Google’s crawler would read your entire site given time. A user agent with a budget constraint might read your llms.txt and Agent Card and nothing else. A thorough agent might crawl every page, read every claim, verify every attestation.
This means the hierarchy of your machine-readable content matters. The most important claims need to be in the files that every agent reads — the llms.txt, the Agent Card. Supporting evidence can live deeper. The information architecture for machines is not the same as for humans, and it might be more important.
Nobody is doing this well yet. Probably because nobody has had to. That seems like it is about to change.