Your website looks good. You've put real work into it. The copy is clear, the design is clean, and you know that what you do is valuable.
And yet when someone asks ChatGPT who to hire for what you do—or asks Perplexity for the best answer to a problem you solve—your name doesn't come up. Your competitors are cited. Sites you know are worse than yours are too. But where are you?
This isn't a content problem. It isn't a design problem. It's an infrastructure problem. And answer engine optimisation—AEO—is the discipline that fixes it.
What AEO actually means
Answer engine optimisation (also written answer engine optimization—AEO) is the practice of structuring a website so that AI-powered answer engines—ChatGPT, Perplexity, Claude, Google's AI Overviews—can extract its content, understand who the business is, and cite it in their answers.
What is AEO in plain terms? It's the difference between a website that AI engines can read and a website that AI engines can understand. Reading is easy—most crawlers can fetch your HTML. Understanding is harder: it requires structured data, consistent entity signals, and content formatted in a way that allows precise extraction.
Most websites are readable. Very few are understandable.
Why is AEO important now
For two decades, search meant Google. You optimised for the algorithm, ranked in a list of ten links, and hoped someone would click yours.
That model is fracturing. Even owners of large sites with hundreds of thousands of backlinks and decades of authority are losing traction and traffic rapidly. But most people don't even know why.
In May 2026, Google announced what it described as the biggest change to Search in over 25 years—a shift toward AI-powered answer experiences that synthesise responses rather than return links. Google's AI Overviews already reach more than 2.5 billion monthly users. ChatGPT's search mode reaches hundreds of millions more. Perplexity and Claude handle millions of queries daily that previously would have gone to Google.
The result is that a growing proportion of the searches that matter to your business now end with a single synthesised answer and a citation—or no citation at all. Not a list of ten links to choose from. And the more people get used to searching this way, the less traffic will come your way.
If you're not the citation, you're absent from the answer entirely. There's no page two. There's no "also considered." You either appear or you don't.
AEO vs SEO vs GEO—what's actually different
These three terms are related but distinct, and the distinction matters for what you actually need to do.
SEO (Search Engine Optimization)—optimising to rank in traditional search engine results, primarily Google. The currency is position: aim for page one, ideally top three. The signals are backlinks, keyword relevance, authority, and technical health.
AEO (Answer Engine Optimization)—optimising to be cited in AI-generated answers. The currency is citation: being the source an AI engine selects when synthesising a response. The signals are schema markup, entity confidence, answer-first content structure, and crawlability.
GEO (Generative Engine Optimization)—a closely related term, often used interchangeably with AEO, sometimes used to describe the broader discipline of optimising for generative AI outputs. For practical purposes, AEO vs SEO vs GEO breaks down like this: SEO is for search rankings, AEO/GEO is for AI citation. They share some foundations and diverge at the technical level.
The important thing: a site can rank well on Google and be completely invisible to AI engines. They are separate technical problems with separate solutions. Most sites that have done SEO work have done almost nothing for AEO—because the discipline barely existed two years ago.
Why your beautiful website is invisible to ChatGPT
The honest answer is that most websites were built by and for humans, not for AI engines. And those two audiences have different needs.
A human visitor reads prose, follows visual hierarchy, and understands context from design and layout. An AI crawler reads raw HTML, looks for structured signals, and extracts content from the initial server response—it doesn't execute JavaScript, doesn't render visual design, and doesn't infer meaning from layout.
The specific reasons sites fail AEO—and why your site might be invisible to ChatGPT right now:
No schema markup. Without JSON-LD structured data, an AI engine reading your homepage sees words. It can't confidently identify you as a person, your business as a service provider, or your content as answering a specific question. Schema is how you tell the engine what your content means, not just what it says.
No entity signals. AI engines build confidence in a source by recognising it consistently across multiple signals—the same name, title, location, and description appearing in your schema, your content, your about page, and external references. Inconsistency or absence means the engine can't form a confident entity model for your business. Sources without confident entity models don't get cited.
JavaScript-dependent content. If your site's core content is rendered by JavaScript rather than delivered in the initial HTML response, AI crawlers can't see it. GPTBot, ClaudeBot, and PerplexityBot do not execute JavaScript. Your beautifully animated homepage may be technically empty to the crawlers that matter most.
Wrong content structure. AI engines extract and cite content that leads with a direct answer. They don't extract a flowing narrative the same way. A site full of thoughtful, well-written content structured for human reading will consistently lose citations to thinner content structured for machine extraction—because the machine can identify and extract a precise answer from the latter and can't from the former.
Blocked crawlers. Roughly a quarter of websites are accidentally blocking AI crawlers via their robots.txt configuration—often because a developer set a restrictive default and nobody checked. If your robots.txt blocks GPTBot, ClaudeBot, PerplexityBot, or Google-Extended, you are invisible to those engines regardless of everything else.
What AEO infrastructure actually involves
AEO consulting and AEO benefits are terms that are rising fast—because more founders are encountering this problem and looking for someone to fix it. Here's what fixing it actually involves.
Schema and entity graph. Implementing JSON-LD structured data across your site: a Person entity for the business owner, a ProfessionalService or Organisation entity for the practice, Service entities for each offer, Article entities for content, FAQPage entities on relevant pages. Each entity is linked internally via @id references, so the engine sees a coherent, connected picture of who you are.
Crawl configuration. Auditing and correcting robots.txt to explicitly allow AI crawlers. Adding a sitemap.xml if absent and maintaining an up-to-date allow/disallow list. Adding llms.txt—an emerging standard that allows you to specify how AI systems should interpret and use your content.
Answer-first content restructuring. Rewriting or restructuring key pages so each section opens with a direct, self-contained answer in the first 40–60 words. Adding FAQ blocks with FAQPage schema to pages where buyers ask questions. This is the content layer that gets extracted and cited.
Discoverability audit. A complete review of the technical substrate—schema validity, entity consistency, crawler access, Core Web Vitals, JavaScript dependency—producing a prioritised picture of what's wrong and what to fix first. This is what the Infrastructure Audit covers.
The result of getting this right: your site becomes understandable, not just readable. AI engines can extract precise answers from it, attribute them to a confident entity, and cite them in response to the questions your buyers are asking. And yes—before you ask—it can still be pretty.
How to know if you have an AEO problem
The fastest check: open ChatGPT or Perplexity and ask the questions your ideal clients ask. "Who is a good [your role] for [your audience]?" "What is [the thing you do]?" "How do I fix [the problem you solve]?"
If your competitors appear and you don't—the gap is almost certainly infrastructure, not content quality.
Other signals: your site looks good but gets no traffic, or traffic but not enquiries; you've done SEO work, but rankings haven't improved; you redesigned the site, and nothing changed; your content is good, but you're not getting found.
All of these point to the same place: the invisible layer underneath the site that determines whether AI engines can find you, understand you, and cite you.
The Infrastructure Audit is where that diagnosis begins.
What is AEO?
AEO stands for Answer Engine Optimisation — the practice of structuring a website so AI-powered answer engines like ChatGPT, Perplexity, and Claude can extract its content, understand the business, and cite it in their answers. It's the infrastructure discipline that determines whether your site is cited or invisible when someone asks an AI tool a question you should answer.
What is the difference between AEO and SEO?
SEO optimises a website to rank in traditional search engine results, primarily Google. AEO optimises a website to be cited in AI-generated answers. A site can rank well on Google and be completely invisible to AI engines — they are separate technical problems with different solutions. AEO requires schema markup, entity signals, answer-first content structure, and correct crawler configuration that standard SEO work doesn't address.
What is AEO vs SEO vs GEO?
SEO (Search Engine Optimisation) is for traditional search rankings. AEO (Answer Engine Optimisation) is for AI citation. GEO (Generative Engine Optimisation) is a closely related term often used interchangeably with AEO. For practical purposes: SEO gets you ranked in a list of links; AEO/GEO gets you cited in a synthesised answer. The technical requirements diverge significantly at the infrastructure level.
Why is my website invisible to ChatGPT?
Most commonly because of one or more of: missing schema markup (no JSON-LD structured data), absent or inconsistent entity signals, JavaScript-dependent content that AI crawlers can't read, content structured for human reading rather than machine extraction, or a robots.txt configuration that accidentally blocks AI crawlers (GPTBot, ClaudeBot, PerplexityBot). A site infrastructure audit is the only reliable way to identify which combination applies.
What are the benefits of AEO?
AEO makes a website visible and citable to the AI engines that are increasingly where buyers research, compare, and make decisions. The specific benefits: appearing in AI-generated answers to questions your ideal clients ask; being cited as an authoritative source rather than absent from the answer; converting higher-intent visitors (LLM-referred visitors convert at significantly higher rates than organic search traffic); and building entity recognition that compounds over time as AI engines see consistent signals across multiple sources.
What does AEO consulting involve?
AEO consulting covers the technical infrastructure that makes a site citable by AI engines: schema markup implementation, entity graph construction, crawl configuration (robots.txt, llms.txt, sitemap), content restructuring to answer-first format, and FAQ schema on relevant pages. It starts with a diagnostic audit of what's currently wrong, produces a prioritised fix list, and involves either designing the specification for a developer to implement or building it directly.