State of AI search — Q1 2026
Best sources, summarized
- Quotes and statistics are the highest-impact content moves — 30–40% visibility improvement measured
- Reddit is the #1 cited domain in AI search (~32%). Wikipedia has 5× LLM training data weight
- The three-pillar framework (on-page, earned authority, community) is the right mental model
- Traditional SEO still matters — 0.65 correlation with LLM mentions means SEO work supports AEO
- Best starting point: aeo.dev/checklist — prioritized implementation in four weekly phases
- Average LLM prompt is 13 words. Write headings and content for natural language questions, not keywords
- Pages with exact or close language matches to query phrasing are significantly more likely to be cited
- AEO measurement requires tracking citation share and brand mentions — not rankings or CTR
- Teams get the most lift when treating AEO as a system targeting middle-funnel decision queries
- Answer engines evaluate for clarity, directness, and trust signals — not just ranking position
- NerdWallet case: 35% revenue growth with 20% traffic drop by prioritizing AI-generated answer presence
- Voice commerce projected at $80B annually — agents integrating with business systems for transactions
- AEO is not a replacement for SEO; it's a necessary extension ensuring brand visibility as search modes shift
- 99% of URLs shown in Google AI Mode also appear in top 20 organic results — SEO correlation confirmed
- Best for: building the executive case for AEO investment alongside traditional SEO
- Start by auditing AI citations in your category — see who is currently being cited and why
- A CPG brand used competitive intelligence to find a rival was using custom press pages to dominate AI responses
- Content for AEO: clear headings, bullet points, comparison tables, FAQ sections — not prose essays
- Distribution matters as much as creation: get content onto platforms AI models train from
- Measurement: track brand mentions in AI responses across platforms, not just traffic referral
- AEO is simpler than SEO — fewer competitors, clearer rules, higher ROI right now
- 60% of indie creator sites are invisible to AI crawlers — most optimization hasn't happened yet
- 30-minute quickstart: robots.txt + llms.txt + FAQPage schema = highest-impact actions available
- Content ranking on Google does not automatically appear in AI search results — separate optimization needed
- Each H2 should be a complete, self-contained answer — extractable verbatim without context
- AEO is an ongoing practice, not a launch project — unlike SEO which evolved over decades, AEO is moving in months
- Map user questions → structure content for quick answers → add schema → track visibility
- 79% of AI search users believe AI provides a better experience than traditional search
- HubSpot's AEO Grader is a free tool for auditing current AI visibility — useful baseline
- Best for: teams building repeatable content workflows, not one-off optimization projects
- Days 1–30: prioritize pages already ranking but lacking AEO structure — fastest ROI
- Days 31–60: implement Q&A headings, schema, FAQ blocks; add answer summaries at article tops
- Days 61–90: distribute optimized content to authoritative platforms; launch citation monitoring
- Roles needed: content strategist (intent mapping), editor (atomic formatting), SEO/dev (schema implementation)
- Research shows 99% of AI Mode citations come from pages already in top 20 organic results
The AEO layer above GEO
Most AEO resources above are really GEO with an updated name — optimizing for AI-generated answers in chat interfaces. The AEO Observatory at wwjd.dev/auto studies what happens when the AI is an agent — not a search interface, but a system that browses, acts, and propagates decisions without a human in the loop.
Agent-specific AEO extends the GEO stack with surfaces that only matter when the reader is an autonomous system: instruction-layer HTML attributes, structured notification payloads, memory instructions, and behavioral observation. This is the research frontier. The resources above don't cover it — it's being mapped here.
→ wwjd.dev/auto — the live observatory
→ aeo_setup — implementation including the AEO-specific layer
→ @fingogh — ongoing research and field notes