What SkuWatch AI Visibility monitors
Monitoring begins with Shopify product identity: product, variant, SKU, legitimate GTIN or MPN, market, price, inventory, selling plan, metafields, publication state, and connected channel.
The storefront agent follows that identity into the public page:
- response and final URL
- canonical
- visible product facts
- semantic HTML
- Product and Offer JSON-LD
- variant selection
- policies and supporting documents
- sitemap and crawler directives
The platform-observation agent records fixed buyer questions separately:
- exact prompt and test ID
- provider and visible mode
- country, language, and time
- completed, failed, or unavailable state
- brand and product mentions
- cited source URLs
- named competitors
- price, stock, or compatibility errors
Why this is different from uptime monitoring
A page can return 200 while showing the wrong market, a security challenge, a generic shell, stale stock, or the wrong variant. SkuWatch AI Visibility retains body-level and product-level evidence rather than treating the status code as the result.
A synthetic request using a crawler name is recorded as a synthetic request. It is not relabeled as verified OpenAI, Anthropic, Google, or Perplexity traffic.
The output
The merchant receives an evidence timeline tied to a stable commerce entity:
Product: DockPro 12-in-1
Variant: DP12-R2 / Canada
Storefront change: compatibility text changed
Feed state: accepted
Prompt observation: canonical source absent
Provider state: completed
Competitor observed: yes
That timeline becomes the input to Explain, not another disconnected dashboard.