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

Rhode scores 62 out of 100, a mixed signal that masks a sharper truth: the site is built beautifully for browsers, indifferently for agents, and outright hostile at the moment of transaction. The structured data foundation is excellent, the crawler posture is permissive, and the conversational copy reads cleanly to a model. But the checkout is gated, the cart is CAPTCHA-protected, and an autonomous buyer trying to complete a purchase will hit a wall before it ever reaches Shop Pay. The biggest single hole is guest checkout, which scores zero of four. The classifier returned high confidence on the evidence quote "Login now to activate early access. Email Password sign in... Don't have an account? Sign up here." Forcing account creation is friction for humans and a hard stop for agents that cannot create credentials, verify emails, or persist sessions across domains. Compounding this, check 4.2 finds reCAPTCHA and hCaptcha deployed on both the homepage and the cart, with transaction_blocking flagged true. Zero of four points there. An agent that successfully parses every product page on the site still cannot put an item in a cart without solving a challenge designed specifically to defeat it. These two findings together, seven points lost, are the entire transactability story. Bot detection more broadly costs another three points on check 4.1. The block rate is only three percent, but rhodeskin.com/checkout returned a 403 outright. Pair that with a missing stated agent policy (zero of two on 4.4, no terms or privacy content the classifier could evaluate) and the posture reads as: agents are not addressed, not welcomed, and not refused in writing, just blocked in practice. On the content side, decision-support metadata fails completely (zero of three on 6.3). Across ten sampled product pages, only three reached medium signal and none reached high. Glazing Milk, the hero SKU, returned an empty quote. Agents recommending skincare need skin-type fit, comparison cues, award context, and sensitivity warnings; the salted caramel lip treatment page nails this with its 17,707 review count and fragrance warning, but that quality is the exception. Delivery date transparency also fails (zero of two on 6.4), with no structured shipping schema anywhere and only free-shipping-threshold copy as a substitute for an actual ETA. The smaller deductions are worth naming because they are cheap to fix. Sitemap quality scores two of four: 69 URLs, no product URLs included, no lastmod timestamps. Product attributes structured loses three points because two of ten sampled pages (the salted caramel lip treatment and the spring lip case) returned zero structured hits, despite the rest of the catalog having clean JSON-LD with brand, sku, mpn, and size. Inventory signals score two of five because no page carries shipping details inside the Offer schema. And merchant verifiability scores one of three: the business name "rhode" is present, but no physical address and no registration ID, which matters for any agent doing trust due diligence on an unfamiliar brand. The biggest opportunity is unblocking the transaction: remove CAPTCHAs from the cart and enable a visible guest checkout path, and Rhode converts seven lost points and an unbuyable storefront into an agent-ready one almost overnight.