Start with a real buying decision
A shopper comparing products needs their differences: dimensions, compatibility, care, price and return conditions. Build product pages and buying guides around those decisions. Use a table when its criteria help someone choose, and a FAQ when customers actually ask those questions.
For a coffee maker, for example, document usable capacity, materials and washable parts from manufacturer information. Identify missing details. Do not turn an unverified certification, test result or customer review into a selling point.
Keep SEO foundations and distinguish services
Google’s guidance for its AI features retains core SEO practices. Check page access, indexability, internal links and the main content in the HTML. Passing these checks makes content accessible; it does not establish that an answer engine will select it.
Google Search, ChatGPT and Perplexity are separate services. Identify your intended service and read its documentation before choosing a merchant feed or integration. Visibility in one service is not evidence of equivalent coverage in another.
Publish consistent product information
Google’s Product structured data documentation describes eligibility for product search presentations. Match prices, currencies and availability to the visible page. Include applicable, verifiable properties; never manufacture ratings or reviews to complete a schema.
Reflect stock changes in the sources you control. Change an update date when the underlying content changes. Measure synchronization delays between the store and its feeds before describing the information as real time.
Evaluate llms.txt for a specific use
llms.txt is a proposal for agent-oriented content and links. Its value depends on which systems consume it. Google Search says it does not use these files for its results. Publishing one therefore does not guarantee rankings or citations.
If a tool documents that use, keep the file concise, maintain its links and observe access. Otherwise, prioritize the information and pages your customers already need.
Separate visibility from UCP transactions
A UCP profile describes a business’s exposed capabilities. It is not a product ranking rule. A compatible agent can use negotiated capabilities; a brand mention alone does not show that it queries your endpoint or can complete an order.
Measure repeatable observations
- Define a stable set of buying questions and the relevant products.
- Record the service, displayed version, country, language, date and signed-in state.
- Repeat observations and retain answers, cited sources and product links.
- Separate a mention, a linked citation, an attributed visit and a measured order.
- Compare equivalent conditions and periods after a documented change.
Analytics captures visits only within the limits of its configuration. An answer without a click is not a session. An increase after an edit is an observation; isolating the edit’s effect requires an appropriate comparison design.