AEO for e-commerce · catalogue-scale

Be one of the three products it recommends.

Shopping assistants don’t return a results page — they return a shortlist. If your price, stock and returns policy aren’t machine-readable, you are not on it, however good the product is.

Shopping-answer inspector Sample · illustrative only
See whether a shopping assistant can price, stock and recommend this product.
The engagement

Audit, fix at template level, track orders.

One change, forty thousand products.

01
Feed audit
Every product template checked as a shopping assistant reads it: price, stock, variants, returns, reviews, identifiers.
02
Fix the catalogue
Offer schema completed at scale, variants given their own URLs, policies moved out of PDFs.
03
Win the buying questions
Comparison, sizing and “which should I get” pages for the prompts your category actually gets.
04
Track what moved
Mention share per collection and where your products now appear across the assistants.
What we fix

Six gaps that keep good products off the shortlist.

All catalogue-wide, all fixable at template level.

Complete Offer data

Price, currency, availability, shipping and returns as data — the fields assistants compare on first.

Variants with their own URLs

Size and colour hidden behind query parameters are invisible. Each buyable variant gets a crawlable page.

Reviews as evidence

Price, stock and product specs published as structured data, straight from your feed.

Product identity

GTIN, MPN and brand set consistently so your listing matches the right product across sources.

Comparison content

The “X vs Y” and “best under £80” pages assistants quote when a buyer is deciding.

Referral attribution

How often your products get named versus rivals — per collection, across every engine.

Before / after

What changes in the markup.

A typical product template on a JavaScript-rendered store.

Typical product page
{"@type":"Product",
 "name":"Merino Base Layer"}

// price rendered by JS
// no availability
// variants behind ?colour=
After
{"@type":"Product",
 "name":"Merino Base Layer",
 "gtin13":"5060123456789",
 "offers":{"@type":"Offer",
   "price":"74.00","priceCurrency":"GBP",
   "availability":"InStock",
   "hasMerchantReturnPolicy":{"returnDays":60}},
 "aggregateRating":{"ratingValue":"4.7",
   "reviewCount":"812"}}
Platforms

Works with what you already run.

Template-level fixes, deployed to your stack.

Shopify
App or theme-level schema injection, variant URL handling
WooCommerce
Plugin deployment, template hooks
Magento
Layout XML and template-level markup
BigCommerce
Stencil template integration
Shopware
Twig template integration
Custom / headless
A patch-level spec your developers can action
Questions

Before you commit.

No checkout changes. Most work is schema and template-level markup, delivered as a patch your team reviews before it ships.

Fixes are made at template level, so one change covers the catalogue. Feed validation then runs continuously per product.

We track mention share per prompt and exactly where you appear across the assistants, month over month. It is visibility you can follow — we do not claim to attribute individual orders.

No, it complements them. Assistants read your site directly as well as merchant feeds, and most stores fail on the site side.

Feed fixes are picked up within days. Comparison content typically shifts answers in four to six weeks.

Start with one product page.

We audit a single template free and show you exactly why the shortlist skipped it.

Get a free feed audit