Separate reader traffic
Google Merchant product data specification organizes ID, title, description, link, image, price, availability, and brand into submit-ready attributes.
Teams can reverse the product-feed spec into a content QA checklist so page titles, images, prices, availability, and brand facts match across search, shopping surfaces, and the site catalog.
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
- Audit product ID, title, price, availability, image, brand, shipping, and policy fields for priority products
- Keep the test narrow: one priority page with clear topic, source links, internal links, and a conversion action
What still needs proof
Missing catalog fields make high-intent product pages harder to trust and compare. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.