AEO vs SEO in 2026: which one actually drives traffic now
AEO (Answer Engine Optimization) is the discipline of structuring web content so generative AI engines — ChatGPT, Perplexity, Google AI Overview, Copilot — cite it inside the answer instead of (or alongside) returning it as a ranked link.
AEO targets being lifted into the AI answer; SEO targets being a ranked link. Both still matter in 2026 — Google AI Overview now appears for ~60% of queries, but classic blue links still drive transactional traffic. The fix is do both: schema, llms.txt, FAQPage markup, 40-60 word direct-answer blocks, and statistical anchors lift AEO; entity clarity, page speed, and backlinks lift SEO. They share more than 70% of the underlying levers.
Key facts
- Google AI Overview appears on ~60% of search queries as of April 2026.
- Pages with FAQPage JSON-LD see a 1.8x higher Copilot citation rate.
- 3+ statistical anchors per 300 words yield a 2.1x lift in Perplexity citations.
- llms.txt adoption grew from 0.4% to 11% of the top 10K websites in 12 months.
- A 40-60 word direct-answer block placed after the first H2 is cited verbatim 4.6x more often than long-form intros.
In 2024, "do SEO" meant rank for keywords. In 2026, "do SEO" means also be cited by ChatGPT, Perplexity, Google AI Overview, and Copilot — because for a growing share of searches, the user never sees the blue links at all.
The mechanical difference
SEO optimises for selection: out of ten blue links, does yours get clicked. AEO optimises for inclusion: out of everything the engine retrieved, does your text end up inside the generated answer.
That sounds like a small distinction and it changes almost every tactic downstream, because the unit of competition moves. In classic search the unit is the page — it ranks, or it does not. In an answer engine the unit is the passage. The engine retrieves chunks, assembles an answer from several of them, and attributes each to a source. A page can be retrieved and still contribute nothing, because none of its paragraphs said anything liftable.
This is why a well-ranked page can be invisible in AI answers while a worse-ranked one gets cited constantly. The second one had a paragraph that answered the question on its own.
How the retrieval actually works
Roughly the same shape across engines, and knowing it explains most of the advice:
- The query is rewritten — often into several sub-queries. A single question becomes three or four retrievals.
- Candidates are retrieved, usually from a live search index plus the model's own store, and chunked.
- Chunks are ranked for relevance to the rewritten query, not to the original phrasing.
- The answer is generated from the top chunks, with citations attached to the passages actually used.
Two consequences follow directly.
Your competition is per-passage. You are not competing with the other nine results. You are competing with every paragraph the engine retrieved, including several from the same page.
Context is not carried. A chunk arrives without the heading three sections up that defined the term. A paragraph that reads perfectly in place and means nothing in isolation will lose to a clumsier one that stands alone.
What actually changed
Three things, in order of impact:
- Google AI Overview hit ~60% of queries (April 2026 measurement, Sistrix). The first thing the user sees is a generated answer with citations — usually 3-5 sources lifted from the SERP.
- Perplexity passed 30M monthly active users and quietly became the default search for builders. Citations there compound — being cited once means you keep getting cited because the engine prefers sources it has already deemed authoritative.
- llms.txt jumped from 0.4% to 11% of top-10K sites in 12 months. The de-facto standard for "tell AI what your site is about" is no longer optional in competitive niches.
What to actually do this quarter
Five concrete moves, in order of ROI:
- Add a 40-60 word direct-answer block after your first H2. Cited verbatim 4.6x more than long-form intros.
- Add FAQPage JSON-LD to your top 10 pages. 1.8x lift in Copilot citations alone.
- Drop a
/llms.txtdescribing what your site is, who runs it, and where the canonical content lives. Picked up on next crawl. - Embed 3+ statistical anchors per 300 words. "60% of queries", "2.1x lift", "11% adoption" — concrete numbers are what AI engines copy.
- Use definition-lead sentences. "[X] is a [category] that [diff]." Picked up as the entity definition for that page.
Writing a passage that survives extraction
The five moves above are the checklist. The underlying rule is one sentence: every paragraph should make sense to someone who read only that paragraph.
In practice that means four habits.
Resolve pronouns and demonstratives. "This makes it faster" is meaningless out of context. "Caching the access token makes each request faster" survives the trip.
Put the claim first, the qualification second. An engine truncating a chunk keeps the beginning. A paragraph that spends two sentences building to its point often gets cut before reaching it.
Attach the number to the claim. "Adoption grew sharply" is unusable. "Adoption grew from 0.4% to 11% of the top 10,000 sites in twelve months" is a quotable sentence, and it carries its own evidence.
Answer the question in its own words. If the query is "how do you calculate CAC payback", a heading that says "The payback question" is worse than one that says "How to calculate CAC payback" — not for keyword reasons, but because the chunk ranker is matching against a rewritten query that looks like the question.
The identity surface
Beyond the prose, a small set of files tells an agent what your site is. All of them sit at fixed paths, all are cheap to produce, and most sites ship none:
| File | What it says |
|---|---|
/llms.txt | A curated index: what this site is, who runs it, where the canonical content lives |
/llms-full.txt | The full text of that content in one fetch, so an agent needs no crawl |
/ai.txt | Citation profile — how to attribute you, what the entity is called |
/robots-ai.txt | Per-bot allow and deny, separate from the crawl-budget concerns of robots.txt |
/identity.json | Machine-readable organisation identity, for disambiguation |
llms-full.txt is the one most worth the effort and the one most often skipped. A crawler that has to render fifteen HTML pages to find your definitions will usually not bother; one plain-text fetch that contains every definition, every direct answer and every FAQ makes citing you nearly free. If your articles already carry structured front-matter — a definition sentence, a direct answer, statistical anchors, FAQ pairs — generating it is mechanical.
The per-bot policy deserves a real decision rather than a default. The bots that drive cited-answer traffic (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, Google-Extended) are not the same population as the bots that scrape for training with no attribution path. Allowing the first set and denying the second is a coherent position; blanket-allowing everything or blanket-denying everything usually is not.
Where SEO and AEO diverge
Backlinks still help SEO; they barely help AEO. The new currency is entity clarity — does the engine understand what you are, who you serve, and what you say with certainty? FAQ schema, llms.txt, and statistical anchors all push that signal up.
Three more divergences worth knowing:
Freshness reads differently. A dated blog post loses to an updated reference page on the same topic, because the engine is choosing a source to trust rather than a result to show. Evergreen pages with a visible dateModified and no datePublished sidestep the "this is from last year" read entirely.
Position matters less, presence matters more. Ranking fourth instead of first costs a lot of clicks and almost no citations. Being on page two costs everything in both.
Ambiguity is fatal in a way it never was for SEO. Google will happily rank a page whose subject it half-understands. An answer engine that cannot tell what entity your page is about will not cite it, because a citation is an assertion it has to stand behind.
The measurement problem, stated honestly
The uncomfortable part: you largely cannot measure this yet.
Search Console reports impressions and clicks from Google search, and an AI Overview citation that produced no click is not a row you can isolate. Perplexity and ChatGPT report nothing to you at all. Referral traffic from answer engines exists but undercounts badly, because the most valuable outcome — the user got their answer and saw your name — generates no referral.
Three partial substitutes, in increasing order of effort:
- Ask the engines directly. Query the terms you care about in ChatGPT, Perplexity and Google, and record who gets cited. Manual, but it is ground truth, and a monthly snapshot beats a dashboard nobody can build.
- Watch branded search volume. If citations are working, people who saw your name go on to search it. Branded volume is a lagging proxy but a real one.
- Track non-brand impressions on the pages you optimised. Not the same as citations, but AI Overview inclusion and organic impressions correlate, since both draw from the same retrieval.
Anyone selling you a precise AEO attribution number is selling you a model, not a measurement. That does not make the work not worth doing; it makes the case for doing the cheap parts first, since you cannot yet A/B your way to the answer.
The cost either way
The cost of the shift is close to zero new tools: front-matter fields, a plain-text file or two, some discipline about paragraph structure. Most of it is writing habits, not infrastructure.
The cost of not shifting is your competitor's direct-answer block appearing inside the AI answer while your better-researched page sits on page two of the blue links nobody scrolls to.
Want a worked example? See what-is-mcp-server — definition lead, direct-answer block right after the first H2, statistical anchors, FAQPage schema. The full AEO surface in one post. The guides are the same structure applied to evergreen reference pages rather than dated ones.
FAQ
Frequently asked questions
Is SEO dead in 2026?
No. AI Overview surfaces an answer block above the blue links, but the blue links still drive ~70% of click-through traffic for transactional queries (search-for-vendor, search-for-pricing). SEO is shifting, not dying — schema and entity clarity now serve both AEO and SEO, so the work overlaps.Which AI engines actually cite sources?
Perplexity and Google AI Overview cite by default. ChatGPT (with browsing), Microsoft Copilot, and Brave Leo cite for fact-heavy queries. Gemini cites selectively. Claude cites only when given retrieval tools. Optimising for Perplexity and Google AI Overview covers ~85% of cited-answer traffic in 2026.Do I need llms.txt?
Yes — adoption is up to 11% of the top 10K sites and rising fast. It is one markdown file at /llms.txt, picked up by Anthropic, OpenAI, Perplexity, and Google indexers. Cost: minutes. Upside: be machine-readable, increase the chance of being cited verbatim.How long until AEO shows results?
Faster than SEO. Direct-answer blocks and FAQPage schema typically lift citation frequency within 2-4 weeks (vs 3-6 months for backlink-driven SEO). Schema, llms.txt, and statistical anchoring are picked up on the next crawl by GPTBot, Google-Extended, ClaudeBot, and PerplexityBot.
