1. The unit of retrieval is the chunk, not the page
Google ranks pages. Answer engines retrieve passages, typically a heading and the text beneath it, then assemble an answer from several of them, often from different sites.
The practical consequence: a page that only makes sense read top to bottom performs badly, because the engine never reads it top to bottom. Every section has to stand alone.
The short versionWrite sections that survive being read in isolation, because they will be.
2. Most AI crawlers cannot run JavaScript
Googlebot renders JavaScript. GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot and PerplexityBot do not.
A client-side rendered React or Vue application that ranks perfectly well in Google can be completely invisible to every AI assistant, and nothing in your analytics will tell you. This is an engineering problem, not a content one, and it is the single most common cause of an otherwise good site being absent from AI answers. See the full crawler reference.
The short versionServer-render, statically generate or prerender. There is no content fix for this.
3. Evidence outperforms keywords, and it is measurable
The foundational peer-reviewed work in this field (the GEO paper presented at KDD 2024 by researchers from Princeton and Georgia Tech) tested which page changes lift visibility in generative engines.
Three tactics each produced gains of roughly 30 to 40%: adding citations to sources, adding quotations from credible sources, and adding statistics. Keyword stuffing performed at or below baseline.
The short versionCite, quote and quantify. The things that feel like academic habits are the ranking factors here.
4. Being smaller is an advantage, for once
The same research found the gains were largest for lower-ranked sites. Generative engines disproportionately reward smaller players who structure content well.
In classic SEO a larger competitor's decade of backlinks is a wall you cannot climb quickly. In AI search, a precise, well-evidenced answer from a small site can be cited ahead of a vague page from a large one.
The short versionThis is the rare channel where structure beats budget.
5. Headings are questions, not keywords
An SEO heading targets a phrase. An AEO heading matches the shape of what a person actually asked an assistant, because the retrieval step is comparing the question to your headings.
"Pricing" is an SEO heading. "How much does an AI answering service cost?" is an AEO heading. The second one gets retrieved.
The short versionPhrase headings as the question a buyer would type into an assistant.
6. Structured data is for parsing, not for rich results
Google removed FAQ rich results from Search in May 2026, so FAQ markup no longer earns the expandable snippet it once did. A lot of agencies quietly stopped implementing it.
That is the wrong conclusion. In an AEO context, structured data's job is telling a machine unambiguously which text is a question and which is its answer, and that is precisely the format answer engines retrieve.
The short versionKeep implementing schema. The audience changed; the value did not.
7. Google is still the gatekeeper for its own AI
AI Overviews and AI Mode are controlled by ordinary Googlebot crawling. There is no separate bot to allow, and Google-Extended governs only Gemini training.
So classic SEO is not a competing investment. It is the entry ticket to Google's AI surfaces, and Google remains the largest of them.
The short versionAEO does not replace SEO. It runs on top of it.
8. You measure citations, not positions
Rank tracking does not answer the question "are we in the answer?". Measuring AEO means re-asking a fixed set of buyer questions across ChatGPT, Perplexity, Claude and AI Overviews on a schedule, and recording where you were and were not cited.
It is a noisier signal than rank tracking and it moves for reasons outside anyone's control, which is exactly why an honest agency reports it against a dated baseline rather than promising a number.
The short versionBaseline your target questions before changing anything, or you cannot prove the work did.