Detail from Martin Waldseemüller's 1507 world map, showing the South American coastline with the word "America" printed on the continent for the first time.

AEO and GEO aren’t a tactics problem. They’re a platform problem.

Everyone has wanted to talk about SEO for years, even though it wasn’t the actual thing they needed to solve. Now the conversation has shifted to AEO and GEO. Same ideas, but anyone selling you a quick fix to any of it is selling you snake oil.

They say the same things, again:

  • Add Q&A formatting
  • Add FAQs (the bane of actual informative content)
  • Apply schema markup (without underlying taxonomy)
  • Claim your entity in the knowledge graph.

Do these things and get cited by AI.

Absolute bollocks.

Every one of those tactics is downstream of a decision nobody’s making.

The structure behind it all

The thing is, structured data improves how often AI systems cite a page. The margin is measurable and huge. And it may get expensive if you ignore it.

But schema markup doesn’t create structure. It reports it. You can’t tag an entity that was never defined consistently in the first place. You can’t mark up a Q&A pattern in content that was never organized around the questions buyers actually ask. The tag is downstream of a decision that was never made.

That decision is the content model, which most organizations still let their CMS make by default. And then they double down on it and publish whatever miscellaneous content that has accumulated rather than deciding what the model should be.

Without a model, you don’t have a platform, you have a repository with ambitions—a problem I’ve written about before. AEO and GEO didn’t create the problem. They just made it visible, expensive, and impossible to ignore any longer.

And SEO?

This really isn’t new. It’s ground well trod.

Google and other search engines have prioritized structured and organized content for over a decade. Organizations that took SEO seriously (past keyword stuffing, which sadly never died) built something else in the process. They built consistent taxonomies, clean information architectures, and internal linking structures that reflected how concepts were related. They chased ranking, but they built a foundation along the way—even if by accident. The content got easier to find, maintain, and trust.

That’s the whole story of SEO for most of the last decade: chase the signal and maybe get to the substance.

AI retrieval made the accident the point. Ranking well used to be a reasonable proxy for getting cited by an AI answer. No more—a shrinking share of AI citations now come from what ranks on page one. Showing up in search and getting chosen by an AI system have become two separate problems. Most brands are optimizing for the wrong one out of institutional inertia.

This isn’t a new lesson. It’s the same one, with the shortcut finally closed.

Content entity clarity (i.e, being recognized by an AI system as a coherent, consistent, well-defined thing rather than a scattered pile of pages using your name five different ways) is a governance function. It’s the same discipline I’ve posted about. Now, it has a new enforcement mechanism. The organizations that succeed right now aren’t the ones who read a listicle. They have a voice system, an information model, and an editorial process—and had it before anyone was talking about AI. Even if that’s not what they initially set out to build.

The honest version of this advice isn’t “add schema.” If you don’t already have a governed content model and taxonomy, schema markup is decoration on a building with no foundation.

It’ll read fine to a person skimming the page, if they find it. But, it will not read as coherent to a system trying to determine whether you’re a real, trustworthy entity worth citing.

Coherence was the thing you never built on purpose.

Everything old is new again

None of this is new. It’s the same argument the whole platform series has been making, with a new judge.

A style guide couldn’t make voice real.

A CMS couldn’t make a content model exist by default.

And a schema tag can’t make structure out of content that was never structured to begin with.

AI retrieval didn’t create the gap between organizations that treat content as infrastructure and organizations that treat it as output.

Now it’s sending the bills.

Want to learn more and decide if this is the right path for your organization, schedule a free consultation.

Scroll to Top