惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - Franky
N
Netflix TechBlog - Medium
宝玉的分享
宝玉的分享
Google DeepMind News
Google DeepMind News
腾讯CDC
G
Google Developers Blog
Martin Fowler
Martin Fowler
Microsoft Security Blog
Microsoft Security Blog
Recent Announcements
Recent Announcements
爱范儿
爱范儿
Engineering at Meta
Engineering at Meta
Microsoft Azure Blog
Microsoft Azure Blog
A
About on SuperTechFans
aimingoo的专栏
aimingoo的专栏
有赞技术团队
有赞技术团队
Jina AI
Jina AI
人人都是产品经理
人人都是产品经理
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
M
MIT News - Artificial intelligence
罗磊的独立博客
博客园 - 三生石上(FineUI控件)
美团技术团队
WordPress大学
WordPress大学
阮一峰的网络日志
阮一峰的网络日志

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
What is AEO (Answer Engine Optimisation) and Why Should D...
Francis Chelladurai · 2026-06-02 · via DEV Community
Cover image for What is AEO (Answer Engine Optimisation) and Why Should Developers Care?

Francis Chelladurai

I asked ChatGPT "What's the best accessibility testing tool?" last week. It cited three products. Mine wasn't one of them. My site ranks on page 1 of Google for that exact query.

That's the problem. Google rankings don't guarantee AI citations. ChatGPT, Perplexity, and Google AI Overviews decide what to cite using different signals than traditional search. This shift has created a new discipline: Answer Engine Optimisation (AEO).

AEO is the practice of structuring web content so that AI-powered search engines can extract, understand, and cite it.

How answer engines differ from search engines

Search engines reward relevance. Answer engines reward extractability.

An answer engine ingests your content, extracts factual claims, evaluates authority via structured metadata and external corroboration, synthesises an answer from multiple sources, and cites only the pages that directly contributed. If your content isn't structured for extraction, it gets skipped — regardless of your Google ranking.

What AI systems actually look for

Here's what matters for AEO, broken into three categories:

Category Key Signals
Structural JSON-LD schema (Article, Product, FAQPage), meta descriptions under 160 chars, clean heading hierarchy, llms.txt file, AI crawler permissions in robots.txt, datePublished/dateModified freshness signals
Content Q&A headings with concise answers, definition sentences ("X is..."), lists and tables, specific numbers over vague marketing copy, outbound links to authoritative sources (W3C, OpenAI GPTBot docs), author attribution
Answerability Self-contained answers extractable without context, one clear topic per page, claims backed by visible evidence

Before and after

Low AEO score:

We offer flexible pricing plans designed to scale with your business. Contact us to learn more.

High AEO score:

Our Professional plan costs $99/month and includes 100 pages per scan, 100 AI tokens, and API access. Annual billing saves 20%. A free Starter plan supports 10 pages per scan with no time limit.

The second version has specific numbers, answers "how much does it cost?" directly, and stands alone — an AI can extract and cite it without surrounding context.

Five mistakes developers make

1. Client-side only rendering. AI crawlers fetch HTML and don't always execute JavaScript. Use SSR or SSG for content pages. In Next.js, keep content in server components.

2. Content hidden in tabs/accordions. Collapsed UI content may not get indexed. Render critical content (FAQs, pricing) as visible HTML.

3. Missing JSON-LD. No structured data means AI systems have to guess what your page is about. Add Article, Product, or FAQPage schema and validate with Google's Rich Results Test.

4. No llms.txt. This newer standard gives AI crawlers a structured summary of your site. Most sites don't have one — add it in 10 minutes:

# Your Product
> One-line description.

## Key Pages
- [Home](https://example.com): Overview
- [Pricing](https://example.com/pricing): Plans and pricing
- [Docs](https://example.com/docs): Documentation

5. AI crawlers blocked in robots.txt. Explicitly allow them:

User-agent: GPTBot
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: PerplexityBot
Allow: /

How to test your AEO right now

  1. Pick a question your page should answer
  2. Ask ChatGPT or Perplexity that exact question
  3. Check if your site is cited
  4. If not, compare your page to the cited sources — they'll almost always have structured data, specific numbers, and self-contained answers that yours is missing

Tools like Blyxo can automate this across your whole site, but the manual test above takes 30 seconds and is usually eye-opening.

TL;DR

SEO optimises for ranking. AEO optimises for citation. You need both. Start with these five actions:

  1. Add JSON-LD to every page
  2. Create /llms.txt
  3. Allow AI crawlers in robots.txt
  4. Add FAQ sections with self-contained answers
  5. Replace vague copy with specific facts

Have you checked whether ChatGPT cites your site? Try it and let me know what you find in the comments.