A growing number of organisations are arriving at a familiar conversation. Their website ranks well on Google, traffic is steady, and yet something has changed. Fewer of the people who matter are arriving through the traditional path.

A prospect quotes back something they read about the company, and the source turns out to be an AI assistant rather than a search result. A buyer mentions a competitor by name and credits ChatGPT, not a top-ten link, for putting that competitor in the consideration set.

That is the shift the term AEO names. SEO is about ranking. AEO is about being cited. They are related, but they are not the same thing, and treating them as the same thing is one of the more expensive misreadings of the current moment.

This article walks through what each one actually does, why both matter, and what changes about how a digital product is built and written when AEO is taken seriously.

What SEO is

SEO, search engine optimisation, is the discipline of making a website discoverable by traditional search engines, primarily Google. The goal is to rank well on a search engine results page so that a person typing a query clicks through to the website. The mechanics are well understood after twenty years of practice: relevant keywords, well-structured pages, backlinks from trusted sources, technical performance, crawlability, page authority.

SEO has not gone away. Websites still need to be crawled, indexed, and ranked. The traditional ten blue links are still how most people start a serious research session. A digital product whose SEO fundamentals are weak will struggle to be found at all, regardless of what else it does well.

What has changed is that ranking is no longer enough. Even a website that ranks first for its target keyword now competes with the AI summary that appears above the ranking, the People Also Ask box that intercepts the click, and the answer engine the user consulted before opening a browser at all.

What AEO is

AEO, answer engine optimisation, is the discipline of making a website's content easy for answer engines to understand, extract, cite, and trust. The answer engines in question are ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and the next ones to arrive. The goal is no longer just to rank. It is to be the source the answer engine quotes when a user asks a question that the website is qualified to answer.

The mechanics are different from SEO. AEO favours direct answers to specific questions, structured early in a page so the answer engine can find them quickly. It favours clean information architecture, schema markup, and writing that does not bury the point. It favours topic clusters where a service or industry page is the pillar and supporting articles answer the specific questions a reader might arrive with.

The measurement is different too. SEO is tracked through rankings, organic traffic, and click-through rates. AEO is tracked through citations in AI overviews, mentions in answer engine responses, and brand presence in AI-generated comparisons. A page that ranks fourth on Google but is consistently cited by ChatGPT as the authoritative answer to a relevant question is doing better commercial work than a page ranking first that nobody cites.

Why they are not in competition

It is tempting to read AEO as the replacement for SEO, the next thing that makes the previous thing obsolete. That reading is wrong. Answer engines learn from the same web SEO has been shaping for decades. A page that is well-structured, well-linked, and trusted is more likely to be cited by an AI system, not less. Strong SEO is part of what makes a page legible to answer engines in the first place.

The right mental model is layered. SEO is the infrastructure. It makes the website discoverable, crawlable, and trusted. AEO sits on top of that infrastructure and adapts the content itself to be cited, not just ranked. A digital product whose SEO is weak will see its AEO performance be weak too. A digital product whose SEO is strong but whose content is structured for ranking alone will leave AEO performance on the table.

The studios and teams winning right now are doing both, deliberately, with the understanding that the goals overlap but the techniques differ.

What changes about how a digital product is built when AEO is taken seriously

This is the part of the conversation that gets practical. AEO is not just a content strategy. It is a set of decisions about how the digital product is built and written.

A few of those decisions, in plain terms.

Pages are structured around questions, not keywords. Each page should answer a specific question a real person would ask. The question should appear in the title or the first heading. The direct answer should appear within the first 150 words. Everything that follows is the supporting argument and the context. This is the structure answer engines expect to find when they extract a citation.

Schema markup is foundational, not optional. FAQ schema, How-To schema, Article schema, and Organisation schema make explicit to an answer engine what kind of content a page is, who is responsible for it, and how its claims are structured. Without schema, an answer engine has to guess. With it, the page is legible at a glance.

Topic clusters carry more weight than isolated articles. A service page that links to ten supporting articles, each answering a related question, builds a coherent web of authority on a topic. A single article on the same topic, however well written, looks shallower to an answer engine than a cluster does.

The writing style itself changes. Burying the answer in paragraph six is now expensive in a way it was not five years ago. Direct, specific, scannable prose is rewarded. Vague marketing language is increasingly invisible to the systems that decide what to cite.

Measurement infrastructure has to follow. Tracking citations across ChatGPT, Perplexity, Claude, and Google AI Overviews is not yet as mature as Google Search Console, but the disciplines of building a monitoring routine, defining the queries the brand should be cited for, and checking those queries on a cadence are already well established for teams that take AEO seriously.

What this looks like in practice

The studio treats AEO as a foundational discipline within Product Growth rather than as a tactic bolted onto a finished site. The studio's own website is built to AEO standards, with pages structured around the specific questions decision-makers arrive with, direct answers within the first 150 words of each page, schema markup applied across services, industries, and impact stories, and a topic cluster model linking pillar service pages to supporting Insights articles.

This is not a coincidence. A studio that argues for AEO as a foundational strategy and then publishes a website that ignores its own argument is not credible. The website is part of the argument.

The most useful question for an organisation thinking about its own digital product is not "do we need AEO." The answer to that question is yes, and is going to be more obviously yes every year. The more useful question is "what is the next decision we have to make to be cited rather than just ranked." That question is what a Product Growth engagement is shaped around.

SEO is still the infrastructure. AEO is the layer that adapts the infrastructure for a world where ranking is no longer the only measure of being found. The websites that understand this will be the ones that get cited. The ones that do not will keep ranking, briefly, for queries that no longer get typed.