Separate reader traffic
WooCommerce REST API product endpoints expose product records that many indie stores and service providers depend on.
AI commerce tools that only support one platform miss stores where product pages, REST endpoints, and feed exports all need the same facts.
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 endpoint output against the public page for title, description, image, price, stock status, and categories
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Long-tail stores with stale endpoint data can feed wrong facts into search, assistants, and comparison pages. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.