Evidence sources
Public product pages and collection pages
Used to compare shopper-visible claims, product copy, price, availability, and merchandising context.
Structured data, including JSON-LD Product and Offer markup
Used to compare machine-readable product and offer facts against the visible storefront.
Policy pages for shipping, returns, warranty, privacy, and terms
Used to check whether AI or channel answers misstate shipping, returns, warranty, privacy, or terms.
Sitemap, robots.txt, redirects, canonical tags, and crawler-access signals
Used to test whether crawlers can discover and retrieve the commerce surface consistently.
AI answer or shopping-channel observations captured during the scan
Used to compare what a system said with the merchant evidence StoreSteady can cite.
Checkout, offer, price, and availability probes where the scan tier supports them
Used when the scan tier supports direct offer, price, availability, or checkout-path validation.
Optional merchant-connected catalog or channel data when the merchant grants access
Used only when the merchant grants access and the finding needs non-public context.
Lifecycle
The lifecycle is observation -> claim -> conflict -> severity -> fix -> validation. Each stage narrows what StoreSteady can responsibly say.
Confidence labels
Confirmed
The public evidence and observed AI or channel response directly support the finding, and the validation path is known.
Likely
The evidence strongly points to the issue, but the finding should be retested after the merchant changes the source surface.
Needs merchant confirmation
Public evidence is incomplete, private system access may be needed, or the merchant must confirm intent before acting.
Inconclusive
The scan captured a signal, but StoreSteady should not convert it into a firm recommendation without more evidence.
Retest paths
Re-crawl the merchant source
Use when the fix changes a product page, collection, policy page, sitemap, canonical tag, or robots rule.
Re-read structured data
Use when the fix changes Product, Offer, Organization, breadcrumb, or policy-linked markup.
Repeat the AI or channel observation
Use when the issue was that an answer, channel, or crawler-visible interpretation misstated the merchant surface.
Reconnect merchant evidence
Use when the public finding needs feed, catalog, or channel account context before it can be closed.