Which signals decide whether you appear
Structured, machine-readable product data
Agents prefer data they can parse without guessing. Availability, price, variants, shipping and return terms should exist as explicit fields, not only as text inside a description. Google’s own guidance for its Universal Commerce Protocol (UCP) is a good example of where this is going: the Merchant Center UCP guide explains that you update your product feed to signal eligibility and supply compliance data, using attributes such as native_commerce for checkout eligibility, consumer_notice for regulatory warnings and merchant_item_id, so agents can decide whether a product is eligible and calculate accurate totals.
If you want a broader primer on the data side, this overview of AI examples in ecommerce and machine-readable product information is a useful companion read.
Freshness
An item that shows “in stock” in your feed and “sold out” on the page is a trust problem. The fix is boring and effective: one source of truth for inventory, synced often, with the page, the feed and the structured data all reading from it.
Crawl access
A common and costly mistake: your CDN or bot-management rules block the crawlers AI systems use. StoreFleet’s review of Perplexity and Google AI Mode for Shopify flags exactly this, naming PerplexityBot and Google-Extended, and recommends explicitly allowing them in robots.txt so your catalog stays visible. Check your firewall logs before you touch a single product description.
Product content that answers comparison questions
Availability gets you into the shortlist. Content decides whether you win it. Specs, materials, sizing, compatibility and honest use-case language let an agent match your product to a specific request. Our guides on optimizing product listings for AI shopping agents and on product knowledge graphs for Shopify and WooCommerce go deeper.