If an AI agent can access a feed containing a product’s price, stock status, brand and specifications, it may seem that the visible content in an online store has become less important. But a feed describes data; it does not replace the commercial, informative and persuasive role of a well-designed product page.

In e-commerce, information is accessed in different ways. People browse pages, search engines crawl content and code, shopping platforms process product feeds, and some AI agents consult structured sources or external services. Preparing a store for only one of these channels leaves gaps in the others.

The question, therefore, is not whether to choose visible content, structured data or feeds. It is about deciding which information belongs in each layer and making sure they all describe the same product consistently.

If AI agents read feeds, why do we still need product pages?

Because structured data is good at answering factual questions, but it does not always address the concerns that influence a purchase. A system may identify that a product costs a certain amount, is in stock and belongs to a particular category. A person also needs to know whether it is suitable for their needs, how it differs from an alternative and what using it involves.

The visible product page is where this information can be organised around the buyer’s actual needs. This includes content hierarchy, photographs, variants, instructions, purchase conditions and anything else that reduces uncertainty. User-centred web design is not simply about presenting a product well: it helps people understand it, compare it and make a decision.

The page also provides context for search engines and AI systems that analyse publicly available content. Not every agent has access to the same feeds or uses the same sources. Assuming that every external system will read one specific channel is not a sound approach.

What are the three layers used to describe the same product?

A useful content architecture distinguishes between three connected layers, each with a different purpose.

1. Visible content

This is the information people see when browsing the store. It should explain what the product is, who it is for, how it is used and which conditions may affect the purchase. It should also be easy to scan, using headings, attributes, tables or information blocks where appropriate.

2. Structured data for e-commerce

Structured data embedded in the code helps machines identify entities and attributes explicitly. Depending on the product page, it may describe the name, image, brand, SKU, commercial identifiers, offers, price, currency or availability.

It is not a second, hidden SEO description or a place to add claims that do not appear on the page. It should accurately represent the visible product and remain up to date. Implementing it is part of technical SEO and may require changes to templates, fields and business logic within the e-commerce platform development.

3. Product feeds

Product feeds distribute the catalogue to search engines, marketplaces, advertising platforms, comparison websites and other services. They usually rely on standardised fields and may need to meet different requirements for each channel. They are particularly useful for sharing information that changes frequently, such as price, availability or variant attributes.

A feed should not be maintained manually and separately from the main catalogue. Wherever possible, it should be generated from a shared data source, with the necessary transformations applied for each destination.

What visible content does a good product page need?

The answer depends on the product and the buying process. An industrial component does not require the same information as a cosmetic product, a piece of furniture or a digital subscription. Writing long descriptions by default does not necessarily improve e-commerce SEO or the user experience.

A useful product page will usually answer the following questions, with the right level of detail for the purchase:

• Identification: what exactly is the product, and which variant is the user viewing?
• Suitability: which uses, needs or customer profiles is it designed for?
• Differentiation: what sets it apart from similar options?
• Specifications: what are its dimensions, materials, compatibility requirements, ingredients or other relevant details?
• Conditions: what should the buyer know about availability, delivery, returns or usage requirements?
• Resolving doubts: which information can prevent predictable purchasing mistakes?

This structure also helps automated systems interpret the product by reducing ambiguity. AI agents for e-commerce may combine data from several sources, but the quality of their answers will still depend on the quality, accuracy and consistency of the source information.

How can contradictions between the website, data and feeds be avoided?

The most common problem is not the absence of another technology layer. It is that each channel uses different information. An outdated price in a feed, incorrect availability in the structured markup or a description that does not match the selected variant can confuse both people and systems.

The starting point is to define a primary source for each piece of data. Depending on the project architecture, this may be the e-commerce platform, an ERP, a product information management system (PIM) or another management tool. From there, the flow of information needs to be established:

1. Which system creates or updates each data point.
2. How often it needs to be updated.
3. Which rules transform the information for each channel.
4. How errors, incomplete fields and failed synchronisations are detected.
5. Who validates editorial content and commercial attributes.

This can be handled through conventional programming, APIs, webhooks and validation processes. It does not necessarily require artificial intelligence. AI can assist with specific tasks, such as suggesting classifications or preparing drafts, but it still requires reliable data and human oversight. As with efficiency in AI-assisted marketing, automating a poor foundation only allows errors to spread faster.

What should be audited in an e-commerce store?

A useful review should go beyond checking whether product markup exists. The visible experience, technical architecture and data distribution should be assessed together.

• Check that each URL clearly represents a product or a specific variant.
• Review whether the content answers the questions customers have before buying.
• Compare prices, stock levels, identifiers and attributes across the page, structured data and feeds.
• Identify duplicate, generic or automatically generated descriptions that have not been reviewed.
• Confirm that catalogue changes are correctly propagated to the relevant channels.
• Analyse how options, filters, comparisons and related products are presented.

Preparing an online store for search engines and AI agents is not about hiding more metadata in the code. It means building a well-modelled catalogue, maintaining consistent data and presenting information in a way people can understand. Product page content still matters because it gives data context and helps someone make a decision. Feeds and structured data do not replace it; they allow the same commercial information to circulate and be interpreted by other systems.

We like to discuss these questions before they become a fixed project brief. Tell us about your case.