Price not observed
The baseline profile does not run JavaScript. The initial response does not contain a price.
Sample report · Static evidence for interface review · No live scan ran
shop.northtrailgear.comShopify · sample detection
Scan overviewAgent-Ready Content · Sample report
Shopping agents can find the products, but an HTTP-only agent cannot read the prices and stops before the cart.
The sample store is reachable and the catalog is discoverable. The portable HTTP baseline cannot observe the price because the page adds the price after JavaScript runs. The browser profile can observe the price.
Buyer-agent journey · HTTP baseline
- ✓Reachable
- ✓Product discovery
- ✓Product and variant
- ×Price and termsAgent stopped here
- –Cart to checkout
Do this first
Render price and priceCurrency in the server response and in the JSON-LD Offer object. Rescan after the change to measure the result.
Profile comparison
Price observed
The enhanced browser profile runs JavaScript and observes the price. This supplemental result does not raise the core score.
Raw area evidence
Where the baseline earned points
Total 68 / 100 before the task cap
Product discovery23 / 25
high confidence
Product and offer clarity16 / 30
high confidence
Commercial policy clarity11 / 20
high confidence
Cart interaction10 / 15
high confidence
Checkout handoff8 / 10
high confidence
Repair plan
Findings
Owner view explains the commercial effect and journey impact.
- Observed URL
/products/summit-shell-jacket- Repair
- Add price and priceCurrency to the server-rendered Offer object. On Shopify, add the values in the product template Liquid.
- Verify when
- The HTTP baseline observes the price and currency at the Price and terms stage.
Seven baseline checks passed: reachability, stable product URLs, product name and description, availability, merchant identity, cart-action contract, and semantic control names.
2 of 3 findings selected · maximum 5
Separate bonus signal
Bonus +2 / 5Machine-readable guidance
The bonus does not increase the core score and does not change the task cap.
llms.txt is present
The file gives agents a readable index of key pages.
No public catalog or feed index
A public product feed can help agents enumerate the catalog.
Content-ready is not transaction trust.
Public content can help a buyer's agent reach checkout. The merchant must still identify the agent, evaluate policy, validate delegated authority, and retain evidence. This KYA trust path is separate from the content score.
- 01Identify the agent and operator
- 02Evaluate merchant policy
- 03Validate the delegated mandate
- 04Record the decision and trace
- 05Record the terminal outcome
- 06Retain evidence for review
This sample scores public ecommerce content only. The result is not a trust, security, accessibility, or compliance certification. Public scan results do not enter agent reputation, the Trust Index, or KYA outcome records.