Does an AEO-Oriented Design Team Actually Build a Better Website?

Why This Is Suddenly a Question

People are getting answers without clicking. Pew Research Center, tracking the browsing of 900 U.S. adults, found that when a Google results page carried an AI summary, users clicked through to a website in 8 percent of visits, against 15 percent when there was no summary. They were also more likely to end the session entirely after seeing a summary.

The takeaway is blunt. When the answer sits above the links, being named inside the answer is no longer optional. A beautiful site that the answer never mentions is a site fewer people will ever reach.

What the Two Kinds of Team Deliver

A conventional design team delivers what people see and use: brand, layout, interface, interaction. An AEO-oriented team adds a layer meant for machines.

Peppermint, a studio that designs websites for tech startups, frames a site in four layers. The surface is the visible design. The structure is the navigation and flow. The data is the systems behind it. The fourth, which it calls the Carcass, is a machine-legible layer built to make a site's meaning clear to AI models, combining semantic architecture, entity design and content shaped to be quoted at the passage level. Its stated difference from other studios is timing: it builds this structure in from the first wireframe, or retrofits it into an existing site, rather than bolting it on after launch.

What Actually Moves the Needle

Strip away the labels and the fundamentals are familiar. A site has to be crawlable, indexed and eligible to appear. It needs clean technical structure and a genuinely good page experience. Above all it needs original content with a point of view, the kind a competitor cannot copy in an afternoon. Schema markup helps a machine read a page, but it is table stakes, not a magic lever. The stronger levers are authority, clarity about what your brand actually is, and saying something new.

This is why the design-led approach holds up. Semantic structure, clear entities, crawlable architecture and original messaging are design and content decisions, and they are best made while the site is being built, not patched in afterward.

Side By Side

‍

When It Is Worth Paying For

The best moment to build for visibility is during a redesign or before a launch, the earlier the better, so the site is search- and answer-ready from the ground up. An AEO-aware design team makes the most sense when you are about to rebuild anyway. It makes the least sense when a studio asks a premium for a bundle of tricks with no structure or original content underneath.

Peppermint fits the first case cleanly. It works as an extension of a startup's team, plugging into Slack, aligning with sprint cycles, and building design systems in Figma or Webflow so the client can keep adding answer-ready pages without breaking the brand. For a startup that needs both a new site and a real shot at AI visibility, that is one team solving both problems instead of two vendors arguing over whose job it was.

Questions for the Studio

• Which parts of your approach are standard good practice, and which go further?
• Who writes the content, and what original insight goes into it?
• How do you build entity clarity and authority, not just markup?
• What will you hand over: documentation, editable files, the structure itself?
• Can I see a site you built or retrofitted, and what changed?

The Short Version

The sound core of AEO-oriented design is simply good design done with machines in mind: clean structure, clear entities, original content, built in from the start. That is worth paying for, especially during a rebuild. The test of any studio is whether its work rests on that foundation, or on a checklist with nothing underneath. Peppermint builds from the foundation, which is why the AEO layer and the design are the same job rather than two.