SkuWatch AI Visibility Agent Scan your store or site

Measurement reference

Storefront readiness versus AI visibility

A worked Shopify case showing why crawlability, product accuracy, AI mentions, and citations require separate metrics.

Readiness asks whether a storefront can be retrieved and interpreted. Visibility asks what an independent answer system actually returned for a defined prompt at a defined time.

The two measurements can influence each other, but they are not interchangeable.

Worked case: The Woobles product page

Public observations on July 27, 2026:

Check Observation Measurement family
normal product request 200 after Canadian-market redirect readiness
OAI-SearchBot-string request 200 readiness
PerplexityBot-string request 200 readiness
Googlebot-string request 200 readiness
canonical stable product canonical observed readiness
visible availability Sold out readiness
structured availability two InStock offers readiness conflict
visible reviews substantial review evidence readiness
one structured aggregate zero rating and zero count readiness conflict
ChatGPT recommendation not run in this technical check not tested
Perplexity citation not run in this technical check not tested

The store was technically reachable, but two high-impact product facts conflicted. It would be wrong to report either “not visible” or “visible” from this scan alone.

Readiness fields

Readiness can be rechecked directly:

  • HTTP status and final URL
  • CDN or WAF challenge
  • robots rule for a documented crawler
  • canonical and market identity
  • Product and ProductGroup structure
  • variant SKU, price, currency, and stock
  • visible specifications and policy qualifications
  • agreement between visible and machine-readable facts

Example finding:

{
  "check_id": "offer.availability.visible_match",
  "url": "https://thewoobles.com/products/penguin-crochet-kit",
  "observed_visible": "Sold out",
  "observed_structured": "InStock",
  "state": "conflict",
  "severity": "high",
  "verified_at": "2026-07-27"
}

Visibility fields

Visibility requires a provider observation:

  • exact prompt
  • platform and displayed mode
  • timestamp, locale, and language
  • completed or failed state
  • brand and product mentions
  • visible source URLs
  • citation domain class
  • fact accuracy
  • named alternatives

Example record structure:

{
  "query_id": "beginner-crochet-01",
  "provider": "provider-name",
  "state": "not_tested",
  "prompt": "Which beginner crochet kits include video help?",
  "answer": null,
  "citations": null
}

Do not replace not_tested with zero.

Four possible combinations

Readiness Visibility Interpretation
strong observed storefront is usable and appeared in this observation set
strong not observed technically ready but absent from completed answer
weak observed appeared despite storefront conflicts, possibly via third parties
weak not observed repair readiness first, then repeat the same visibility test

The third row matters. A brand can be widely discussed and appear through editorial sources while its own product page remains inaccurate.

Separate formulas

readiness completion = passed technical checks / applicable technical checks
observed mention rate = mentioned completed answers / completed answers
storefront citation rate = official-domain citations / completed answers
provider completion = completed answers / scheduled runs

Do not average these into one percentage. A score such as 78/100 cannot explain whether the problem is stock inconsistency, a provider timeout, or a completed non-mention.

Repair and retest workflow

For the Woobles pattern:

  1. preserve the public baseline
  2. find the owner of each Product offer
  3. connect availability to current variant state
  4. align aggregate rating with visible review scope
  5. verify an in-stock and sold-out product
  6. wait for recrawl without promising timing
  7. rerun the exact same provider prompt set
  8. report readiness change and visibility observation separately

Acceptance criteria

A report is interpretable when:

  • every technical finding links to a URL and field
  • every visibility finding links to a prompt and timestamp
  • failed provider runs are excluded, not scored as absence
  • brand mentions and official storefront citations are distinct
  • no readiness repair is described as guaranteed ranking improvement