Mixed signal. Agents can reach the page, but guess from there.

Olipop scores 57 out of 100, a mixed signal that reflects a real tension in how the site is built: the crawlers are welcomed, the product content is genuinely excellent, and the payment rails are agent-friendly, but the transactional surface is booby-trapped with CAPTCHAs and the machine-readable scaffolding around price, inventory, and variants is half-finished. This is a brand that wants to be found and understood, then makes an agent fight to actually buy something.

The most expensive single failure is CAPTCHA prevalence, where Olipop scores 0 of 4. Both reCAPTCHA and hCaptcha are detected on the cart page and the homepage, and the check flags this as transaction-blocking. Layer on the 403 returned by drinkolipop.com/checkout during the agent-posture probe, and the picture is unambiguous: any agent that gets past discovery and product parsing runs into a wall the moment it tries to convert. For a DTC brand whose entire growth thesis depends on repeat purchase, deliberately gating the cart against automation is a strategic own-goal.

Price in raw HTML is the next big leak, scoring 4 of 8. Seven of nine sampled product pages expose price via schema (the recurring $35.99 shows up cleanly in the Shopify product JSON), but zero pages surface it in rendered HTML text. Agents that do not execute JavaScript or parse JSON-LD see nothing. Compounding this, structured product data coverage lands at 3 of 6 and product attribute completeness at 3 of 6, both dragged down by the same two URLs (classic-root-beer/sitemap.xml and blackberry-vanilla/sitemap.xml) which return 200 but carry no Product schema at all. Those look like routing accidents worth fixing in an afternoon.

Checkout flow structure scores 2 of 6 and guest checkout availability scores 2 of 4, both hobbled by the same problem: the classifier could not even reach a checkout page to evaluate it, and the cart page shows a "Log in" link with no visible guest path. Shopify defaults to guest checkout, so the capability almost certainly exists, but if it is not surfaced prominently on the cart, an agent has no way to know. Combined with the CAPTCHA finding, Olipop is telling agents three separate times that transacting here is not welcome.

Two smaller but symbolic misses: price history signals score 0 of 2 despite sale markup appearing on seven product pages (the classifier could not verify a prior price on any of them, which reads as decorative strikethroughs without substance), and stated agent policy scores 0 of 2 because the terms and privacy pages could not be fetched for classification. Return policy machine-readability is 1 of 3, and the evidence quote explains why: "we don't accept returns of product or do exchanges of product," which is a legitimate business choice but is presented as prose rather than structured fields for window, conditions, and process.

The bright spots are real. Every tracked AI crawler is allowed, llms.txt is present, Shop Pay and Apple Pay and PayPal are all live, the Shopify cart API is accessible, and product content scores near-perfect on specification completeness and conversational description quality. The biggest opportunity is unambiguous: remove the CAPTCHAs from cart and homepage and surface a guest checkout path, because everything upstream of the transaction already works.