Answer Engine Optimisation: how to make your page quotable by AI
Search used to end with a list of blue links. Increasingly it ends with an answer. ChatGPT, Perplexity, Google AI Overviews and Microsoft Copilot read pages, decide what they mean, and hand the user a summary — often quoting a handful of sources directly. Answer Engine Optimisation (AEO) is the practice of making your pages easy for those systems to read, understand and cite. It sits alongside traditional SEO rather than replacing it: SEO helps you rank, AEO helps you get quoted.
Why AEO is not the same as SEO
Classic SEO optimises for a ranking position in a list. AEO optimises for something different: being the source an AI model paraphrases or names when it answers a question. An answer engine does not need your page to win a keyword race. It needs to parse your page confidently, extract a clear answer, and trust the source enough to repeat it. Pages that are cleanly structured, factually specific and unambiguous tend to be favoured because they are cheaper for a model to interpret correctly.
What makes a page quotable
Three things do most of the work. First, AI crawler access: if GPTBot, ClaudeBot or PerplexityBot is blocked by your robots.txt, the page is far less likely to be surfaced regardless of its quality. Second, structured data: JSON-LD schema gives an engine machine-readable clues about what a page is — an FAQ, a how-to, a local business — instead of leaving it to guess from raw HTML. Third, answer-first writing: lead each section with a direct, self-contained answer of roughly 40 to 60 words, then expand. Models extract those leading statements well.
The role of schema and AI discovery files
Schema markup removes ambiguity. Without it, an engine infers meaning from headings, layout and text, and it can get that wrong. With valid JSON-LD in place, the page states its own type and key facts — who published it, what it covers, what questions it answers. That makes accurate schema a potentially high-leverage improvement, particularly where the page represents a well-defined entity or content type. Alongside schema, an llms.txt file at your domain root can give AI crawlers a plain-text index of your site and its most important pages. Related files such as ai.txt and identity.json declare usage preferences and identity. Publish them accurately and keep them current — the AEO Checker verifies all of them in a single run.
A practical AEO checklist
- Confirm AI crawlers can reach your pages — check robots.txt allows OAI-SearchBot (ChatGPT search), PerplexityBot, ClaudeBot and Bingbot.
- Add valid JSON-LD schema for the real type of each page, and keep it matched to visible content.
- Lead sections with a direct answer, then provide detail and cite named sources.
- Show authorship, publication and updated dates, and keep content current.
- Publish an llms.txt at your root and keep it in step with your site as it changes.
Done together, these steps make a page that an answer engine can read without effort, trust without hesitation, and cite by name. That is the whole goal of AEO: not simply to appear in results, but to become the answer.