Separate reader traffic
Structured commerce fields make recommendation chains concrete, especially for multilingual buying paths.
AI shopping needs price, stock, tax, delivery, and return information to make good recommendations.
Requests are not readers
The useful question is not whether traffic looks busy; it is which activity represents readers, monitoring, crawlers, retries, or system errors.
Check the logs first
- Run a monthly audit on Product, Offer, shippingDetails, and returnPolicy fields for top SKUs
- Keep the test narrow: one priority product or checkout flow before expanding recommendation, authorization, payment, and support work
What still needs proof
Missing fields lead to brittle recommendations and low conversion quality. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.