What AI search needs from a Shopify Plus catalog

People already ask ChatGPT, Copilot, and Google AI Mode what to buy. They ask the same way they ask a salesperson: by the name of a conductor, a size chart, a compatibility question, or a product that fits a specific use.

If your Shopify Plus catalog cannot answer with structure, those assistants have nothing solid to cite. You are still selling. You are just harder to find in the channel that is growing around search.

This is not a pitch for a first store. It is for brands that already sell on Plus and are deciding how the next theme or rebuild should treat product truth.

What AEO means here

AEO is answer engine optimization. In practice it means three things on a storefront:

1. Product facts live in structured fields, not only in prose.
2. Pages render that truth on the server, so a crawler does not have to run your JavaScript to see it.
3. Named entities (people, places, product attributes) are linked in a way an assistant can recognize and reuse.

Search engines have cared about structure for a long time. Assistants care even more, because they answer in sentences and need clean inputs.

Where Plus catalogs usually break for AI

Most Plus stores were built for humans clicking through a theme. That still matters. It is not enough for an agent.

What usually goes wrong:

• The facts that matter (composer, voltage, fabric, fit, who is on the recording) sit inside a long description paragraph.
• FAQs and size charts are images, PDFs, or one-off HTML that never becomes data.
• Apps and theme scripts put key product information only in the browser. AI crawlers do not execute JavaScript the way a shopper's browser does. If the data only exists client-side, it does not exist to them.

At DotDev this year Shopify made the direction clear: agentic commerce is on the roadmap, and agents buy from stores they can read. Structured product data and server-rendered pages are practical requirements, not nice-to-haves.

What we built for The Symphony Store

The Symphony Store is the Chicago Symphony Orchestra's shop: recordings, apparel, and gifts. In spring 2026 they asked us to get the catalog ready for AI search ahead of a summer rebrand. We built a new theme structured for answer engines, published it live on June 29, 2026, and handed it to their developers.

A symphony catalog is not a normal DTC assortment. Shoppers and agents search by conductor, composer, soloist, ensemble, and recording, not only by product title. Those names were buried in descriptions. FAQs were hard to use. Size charts were not structured. Press quotes lived inside product copy.

If AI cannot name the people on a recording, the store does not show up when someone asks for Solti, Muti, or a specific CSO Resound album.

What we shipped:

• Catalog and metafield structure for AI discovery across a uniform product template
• Linked, reusable profiles for every recording's conductors, composers, soloists, and ensembles, each tied to authoritative sources so AI can recognize them by name
• Product-level FAQ fields the store team can fill without a developer
• Accessible, on-page apparel size charts built on metaobjects
• A dedicated press-quote block, then a cleanup pass so quotes were not duplicated in descriptions
• Keyboard and screen-reader fixes on the existing FAQ page
• Developer handoff: how the theme works, what the team can change without code, and how to validate updates

Those FAQ answers and press quotes are not buried in a description blob. They sit in fields the theme can render, and assistants can read the same truth a shopper sees.

This was a build case, not a conversion case. The work is the architecture. The case study is here: https://braundesign.co/blogs/case-studies/symphony-store-aeo

CSO's developers used that AEO theme as the starting point for their July merchandise refresh. We stayed on for description cleanup and a later custom-fields pass. Search and traffic results will go on the case study once the catalog has had more time live.

If a redesign is on your roadmap

You do not need a rebrand to start. You do need a clear rule for where product truth lives.

Put the facts assistants need into metafields and metaobjects the whole platform can read, not only into theme settings locked to one skin. Theme settings die with a theme swap. Metaobject-driven configuration can follow you into checkout, apps, and Flow.

When you rebuild, make the new theme server-render that structure from day one. Do not leave the important answers in a client-side widget and hope a crawler finds them.

That is the same lesson as DotDev, applied to a catalog: less glue in the browser, more judgment about how the store is built.

Braun Design Co is a boutique Shopify Plus partner in Austin. Custom themes, migrations, and AI search for brands that already sell.

If you want to talk through what this would look like on your catalog, my calendar is at https://braundesign.co/meet30.