--- type: Article name: "What a product feed needs that a product page doesn't." id: "https://selfe.ai/insights/ecommerce-and-product-discovery/what-a-product-feed-needs-that-a-product-page-doesnt" url: "https://selfe.ai/insights/ecommerce-and-product-discovery/what-a-product-feed-needs-that-a-product-page-doesnt" publisher: "did:web:selfe.ai" description: "A product page is written for a person looking at one item. A product feed is what an AI agent reads to compare many at once, and it needs a different kind of precision: structured, decision-relevant fields, not the same copy reflowed into a spreadsheet." datePublished: "2026-09-15T11:56:07.124Z" author: The Selfe team --- # What a product feed needs that a product page doesn't. > A product page is written for a person looking at one item. A product feed is what an AI agent reads to compare many at once, and it needs a different kind of precision: structured, decision-relevant fields, not the same copy reflowed into a spreadsheet. ## In short - A product page is written for a browsing human; a feed is what an agent reads to compare many products. - A feed needs structured, per-variant fields, not the same copy reflowed into a spreadsheet. - Colour and variant naming drift between page and feed just as easily as sizing does. - Keeping a feed accurate is closer to inventory management than to content or SEO work. - Selfe generates the feed from a retailer's live systems rather than a one-off export. The page nobody edits directly is often the one an agent actually reads. A feed that quietly drifts out of date does more damage than a dated photo ever could. ## A page is written for one person looking at one thing A retailer's product feed lists a jumper as "One Size." Its own website shows the same jumper in four numbered sizes, each with different stock levels. Nobody edited the feed to be wrong, it just stopped being kept as granular as the actual product line, because the page was always the thing anyone checked, and the feed was quietly generated once and left. Product pages are built to be read, scrolled, persuaded by. That's the right design for a browsing human. A feed serves a different reader entirely: a system comparing hundreds or thousands of items at once, which needs each field to be specific and structured rather than folded into prose. "Available in various sizes" is fine on a page. In a feed, it's a fact an agent can't use. The same drift shows up in colour naming. A page might describe a sofa in a rich, specific tone, "storm grey with a hint of blue," while the feed behind it just says "grey," collapsing three genuinely different products in the range into one indistinguishable entry. A buyer matching to an existing room gets nothing useful from either version alone. ## What a feed needs that a page can get away without A feed needs the exact variant, size, colour, material, as separate structured fields, not a sentence describing them. It needs a current price and a current stock count per variant, not per product. It needs a real delivery estimate, not a shipping policy link. None of that is optional the way it can be on a page, because a feed is the thing an agent is reading when it compares one listing against another. ## Feed accuracy is closer to inventory work than content work Keeping a feed accurate isn't the same discipline as writing pages that rank well or read persuasively. A perfectly optimised, beautifully written product page can still sit behind a feed that's stale, under-specified, or generated once and never touched again. The feed is closer to the retailer's actual inventory system than it is to its marketing content, and it needs to be treated that way. ## Where this shows up for a business A feed stops drifting the day it stops being a separate export and starts reading from the same source as the website's own stock numbers, variant by variant, live. That's the connection Selfe generates a retailer's feed from, rather than a one-off file somebody remembers to regenerate. ## We already have a product feed for ads and marketplaces. Isn't that enough? Often not, an ads feed is built for its own platform's rules and can be less granular than what an agent needs to resolve a specific request. ## How often does a feed need to update? As often as the underlying stock and price do. A feed that regenerates once a week is a week behind the page it's meant to represent. ## Act on this - [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan. - [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry. - [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size. - [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`. - [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.