squirrelscan
GitHub

Commerce readiness: can a shopping agent buy from this shop

Checks that product pages declare the offer fields a shopping agent needs: price, currency, availability, shipping, returns and an identifier. Runs only on detected shops.

What commerce readiness is

A shopping agent compares products and, increasingly, buys them for a person. It cannot do that from a photo and a paragraph. It needs the offer declared in structured data: what the product costs and in which currency, whether it is in stock, what shipping and returns look like, and an identifier (GTIN, MPN or SKU) that lets it match the product across shops.

What squirrel checks

The rule runs on each crawled page of a site detected as ecommerce or marketplace. It reads the page’s own structured data (JSON-LD, microdata and RDFa, the same markup schema/product reads) and emits up to three kinds of check.

  • offer-completeness: on a page with Product or ProductGroup markup, looks for six fields on the offer: price, priceCurrency, availability, shippingDetails, a return policy (hasMerchantReturnPolicy on the offer, the product or an organization node, or a MerchantReturnPolicy node) and an identifier (gtin, gtin8, gtin12, gtin13, gtin14, mpn, sku or productID). It passes when all six are declared. It warns with Offer is missing N of 6 fields a shopping agent needs and lists each missing field as an item. When the page was not read completely (a truncated response, or microdata the reader does not follow), a missing field is not proven, so the check reports at info status instead and a finding from an earlier audit stays open. A page read whole with no Product markup reports at info status and is not judged. A page read in part with no Product markup found is reported the same way, and a finding from an earlier audit stays open, since the markup may sit past the cut.
  • commerce-feed: info only. Reported when the page links to what looks like a product feed (a merchant, product-feed or google-shopping style path, or products.xml, products.json or products.csv).
  • commerce-manifest: info only. Reported when the page links to an agent checkout manifest under /.well-known/ (ucp, acp.json or agentic-commerce). The manifest is detected, not fetched or validated: the standards are still competing.

Feed and manifest checks never warn and never lower the score. Only a proven missing offer field does.

squirrel does not probe for feeds or manifests and does not compare a feed with what the pages say. It reports what the crawled pages link to.

When it runs

The rule declares that it applies to ecommerce and marketplace sites. On any other detected site type, squirrel emits one skipped check (Not applicable: site type is "<type>") and does not run it. Site type comes from the cloud site profile, so a signed-out local audit has no site type and runs the rule on every page; pages without Product markup report at info status.

Detection can be wrong. Override it per site with the applies option, which takes auto (the default), on or off:

[rule_options."ax/commerce-readiness"]
applies = "on"

off emits one skipped check and does not run the rule. The audit_website MCP tool takes the same switch as its commerce argument (auto, on or off), which wins over the config for that call.

How to fix it

Add the missing fields to the Product’s offers:

{
  "@type": "Product",
  "name": "Widget",
  "sku": "W-1",
  "offers": {
    "@type": "Offer",
    "price": "19.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "shippingDetails": { "@type": "OfferShippingDetails" },
    "hasMerchantReturnPolicy": { "@type": "MerchantReturnPolicy" }
  }
}

Fill the shipping and return policy nodes with their real properties; an empty typed node does not count as declared.

Rule IDax/commerce-readiness
CategoryAgent Experience
ScopePer-page
Severitywarning
Weight3/10

Enable / disable

Disable this rule

[rules]
disable = ["ax/commerce-readiness"]

Disable all Agent Experience rules

[rules]
disable = ["ax/*"]

Check names by outcome

Each check name this rule can emit, by what it means to a tool comparing two audits. A problem check is a finding. A clean check says the rule ran over what it covers and found nothing; it clears the problem checks listed beside it, so a finding is fixed when the rule ran over the same scope and a clean check took its place. A not checked check says the rule did not evaluate, and never clears a finding.

Check nameOutcomeClears
offer-completenessProblem
offer-completenessCleanoffer-completeness
offer-completenessNot checked
commerce-feedProblem
commerce-manifestProblem
ax/commerce-readinessNot checked

Check your site

Run squirrel audit https://example.com and open the Agent Experience section of the report. Signed-out local audits need no account and cost nothing.

Type to search…

↑↓ navigate↵ openesc close