AEO: No One Has the Answer Key

Does anyone know how AI answer engines choose who to cite? No. Not you, not me, and not the vendor selling you an AEO retainer.

No major answer engine publishes its citation selection or weighting logic. Every framework in circulation, including the one below, is reverse-engineered from watching outputs.

That is worth saying out loud before anyone spends a budget on it.

AEO is not a playbook. It is a bet with unusually good odds, and it should be run like one.

Why does nobody actually know how AEO works?

Because the mechanism is deliberately closed, and the people describing it are mostly selling something.

Three numbers circulate through nearly every AEO article. That 44 percent of ChatGPT citations come from the first third of a page. That 80 percent of cited sources do not rank in Google's top 100. That around half of buyers now begin research in a chatbot.

Each one appears across multiple vendor blogs with near-identical framing and thin sourcing. That could mean the finding is real and widely replicated. It could equally mean one study got copied around until repetition started to look like consensus.

I use the directional claim. I do not use the decimal.

The directional claim is sturdy: AI-mediated research is growing, and structured, well-sourced, answer-dense content does better inside it than marketing prose. That much is observable without trusting anyone's percentage.

What do you do when the ground truth is hidden?

You instrument before you scale. The same thing you would do with any system whose internals you cannot inspect.

Most teams do the reverse. They rewrite fifty pages on a vendor's advice, then have no way to tell whether it worked, because they never measured the starting state.

Pick ten real buyer questions. Run them against ChatGPT, Perplexity, Gemini, and Claude today. Write down who gets named and what gets cited alongside them. That is your baseline, and it costs an afternoon.

Now you can actually attribute a change to a cause. Without it you are redecorating.

Which AEO practices survive any ranking change?

Start from the buyer's question tree, not a keyword list. People do not type fragments into an assistant. They ask whole comparative questions: what is this category, how does this compare to that, should we build this or buy it. Map the real questions your two or three buyer types ask, then answer them directly. Comparison and definitional content is where these engines lean hardest.

Write to be quoted, not to be read. Lead with the answer in the first sentence or two. Burying it under three paragraphs of setup was merely bad writing under SEO. It is now a structural cost, because the part of the page a model is most likely to lift is the part you filled with throat-clearing. Pair that with FAQ blocks, comparison tables, and FAQPage and Product schema so the structure is machine-legible and not just visually implied.

Keep your facts identical everywhere. The same figure, phrased the same way, on the site, in the docs, in the newsroom, in your llms.txt. Contradicting yourself across surfaces you fully control is the cheapest trust failure available to you.

Show up where the models pull from, not only where you publish. For a technical product that means documentation quality, working code examples, review sites, comparison and alternatives pages, and video walkthroughs. Your marketing site is one input among many, and often not the most cited one.

Publish data nobody else has. This is the strongest asset in the list and the least used. Prose can be regenerated by anyone. A number only you can produce becomes the thing other sites cite back to you, and those citations compound into exactly the authority signal these systems appear to weight.

Three of those survive any conceivable change to ranking logic: proprietary data, factual consistency, and machine legibility. If your budget is limited, spend it there and let the formatting tactics follow.

How do you make a product legible to an agent?

You stop writing for the crawler and start building for the client. This is where I think most AEO advice stops one layer too early.

Every tactic above still assumes a model is reading a page built for a human. That assumption has an expiration date. The more useful question is whether an agent can use your product at all, not whether it can summarize your homepage.

On Orbyt, the AI-native job platform I built solo in 32 days and now run at over 425,000 lines with 11,372 tests, I built for that directly in two ways.

The first is a programmatic content architecture spanning hundreds of thousands of pages, generated from structured data rather than hand-written. Every one carries consistent schema, a real answer in the opening lines, and internal links that reflect actual relationships instead of a navigation guess.

The second matters more. Orbyt exposes an MCP-native API, so an agent can query the product directly through the Model Context Protocol instead of scraping HTML written for a person. An assistant does not have to infer what the product does from a landing page. It can call it.

That is a bet, and I will name it as one. The bet is that the endpoint of this shift is not better prose for crawlers. It is products agents can operate. Content optimization gets you cited. Machine legibility gets you used, and being used is a considerably better position than being mentioned.

How should you measure this?

Citations, not rankings. Rank tracking does not map to a surface with no ranks.

Run the same fixed question set on a schedule. Log four things: whether you were named, where in the answer, which sources were cited beside you, and which competitor was named when you were not. That last column is the most useful and the one everyone omits.

Then cross-reference against qualified pipeline. Citation share with no attributable pipeline is a vanity metric, and it is an easy one to hide behind because the chart only goes up.

Be honest about the lag. Anyone promising results in a fixed number of weeks is quoting a brochure. You will know it worked when the question set says so.

What should you do this week?

Pick your ten real buyer questions and run the baseline. One afternoon.

Then fix the highest-intent pages first, which are almost always the comparison and the build-versus-buy pages, not the homepage.

Then find the one number only you can publish, and publish it.

Everything else in AEO is a hypothesis. Those three are just good business that happens to also work on machines.

---

Related reading

• Selling to AI Agents
• AEO, GEO, and llms.txt: The New SEO
• I Built a Production SaaS in 32 Days
• I Built the Scoreboard. It Says Zero. what happened when I actually instrumented citations and reported the reading

---

Originally published on justinbartak.ai on Aug 6, 2026.