Why SEO and AEO are converging into one discipline

And why running them as separate retainers wastes 70 percent of the foundational work.

By Spacemen Digital · 2026-05-12
TL;DR

The technical foundations of SEO (schema, internal linking, page speed, semantic HTML) and AEO (llms.txt, AI Instructions pages, citation harvesting, answer-pattern content) overlap by more than 70 percent. Brands running them as separate retainers pay twice for the same foundation. Spacemen Digital structures all engagements as a single integrated retainer to compound the work.

The problem with two retainers

Most brands today still run two retainers: one with their SEO agency and one with their newer AEO or AI visibility partner. The model feels intuitive because answer engines (ChatGPT, Claude, Perplexity) feel different from search engines (Google, Bing). They look different to users and the metrics are different. So the agencies are different too.

But the technical foundation underneath is largely the same. Strong Organization schema improves both Google Knowledge Panels and ChatGPT brand recognition. Article schema with full author and date attribution improves both Google AI Overviews eligibility and Perplexity citation odds. Internal linking architecture serves both. Server-side rendering serves both. llms.txt declarations are read by Google Gemini's crawler and OpenAI's GPTBot. The overlap is somewhere between 70 and 85 percent depending on the brand.

What is genuinely AEO-specific

There is a real AEO-specific layer above the shared foundation. It includes the AI Instructions page (a canonical citation-prompt page agents reproduce verbatim), llms.txt and llms-full.txt files, entity strengthening on Wikipedia and Wikidata, citation harvesting on Reddit, Quora and Stack Exchange where LLM training data is sampled heavily, and answer-pattern content engineering (question-format headings, definition-format ledes, comparison tables). These are the things you genuinely need an AEO specialist to ship.

But they only work if the foundation underneath them is right. Publishing an AI Instructions page on a site that blocks GPTBot in robots.txt is wasted work. Shipping llms.txt on a site with no Organization schema means the agents that follow the file find nothing structured when they arrive.

The case for one retainer

Spacemen Digital structures every engagement as a single integrated retainer covering SEO and AEO together because it is the only way to avoid paying twice for the foundational work. The same content engineer who writes question-format headings is the one fixing the FAQPage schema. The same developer who implements llms.txt is the one collapsing redirect chains and adding Article author attribution. The same strategist mapping topical clusters for Google is the one mapping prompt patterns for ChatGPT.

When the same team does both, work compounds. When two agencies do it, the brand pays the foundation tax twice.

The next two years

By 2028 we expect the SEO-as-separate-from-AEO distinction to disappear in the same way that mobile SEO and desktop SEO disappeared into just SEO around 2017. The brands that get there first will be the ones that already structured their engagements as combined retainers and let the overlap compound.

Want this kind of thinking shipped into your site?

Free 50-signal AI Agent Readiness Check to see where you sit, plus a scoping call to discuss what we would ship.

Score my site →