E-commerce: product architecture for search and AI

Structuring a product-led website for three readers at once: the shopper, the search engine and the answer engine that has to describe a product it cannot see.

Categories restructured
Product pages given structured information
Length of engagement

Scope of work as delivered.

01

Problem

Product sites fail in AI search for a specific reason: the facts a machine needs are in the photograph, in the variant selector or in a PDF, and never in text that can be extracted.

  • Category and product pages competing for the same queries.
  • Product attributes present visually but absent from readable content.
  • Buying questions answered in reviews and chat, not on the page.
  • Weak internal connections between a category, its products and related content.
02

Diagnosis

The site was mapped as a chain rather than a list of pages. Every gap in the chain is a point where an assistant loses the thread and recommends something else.

Category>Product>Attributes>FAQ>Related content

Each link was checked for three things: does the page exist, does it state the fact in text, and does it point to the next step.

03

Implementation

  • Category architecture with one clear purpose per category page.
  • Product page template carrying composition, use, size and suitability as readable text.
  • FAQ content built from real buying questions and attached to the product it belongs to.
  • Structured product information, including reviews where they exist.
  • Internal linking between category, product and supporting content.
  • Metadata and headings rewritten so each page states what it is on the first line.
04

Measurement

Search Console query and page coverage for category and product URLs, plus citation checks on product style questions of the form "which product for X" in ChatGPT with search, Perplexity, Google AI Overview and Gemini.

05

Result

{{RESULT_SENTENCE_OR_DELETE}}

Delivered: a product structure in which every commercially important attribute exists as text, every category has one job, and the path from a general question to a specific product is explicit rather than implied.

Why this case matters for online retail: an assistant recommending a product repeats what it can read. Attributes that live only in the design are, for that purpose, not on the page at all.

Check your product pages

Send a category URL and I will show what an assistant can and cannot read from it.

Request a quick check
Scroll to Top