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

Parachute Home scores 61 out of 100, a mixed signal that masks an unusual split personality. The discoverability and machine readability layers are largely in order, the trust signals are credible, and the Shopify plumbing under the hood gives agents real purchase rails to work with. But the storefront then turns around and gates the cart behind reCAPTCHA and hCaptcha, suppresses guest checkout, publishes no stated agent policy, and skips the agent-specific endpoints that would let a crawler self-orient. The site is technically transactable and culturally hostile to automation at the same time. The single most expensive finding is CAPTCHA prevalence. Both reCAPTCHA and hCaptcha fire on the cart and homepage, and the check flags transaction_blocking as true. That zeroes out four points and effectively neutralizes the otherwise excellent payment rail coverage (Shop Pay, Apple Pay, PayPal all detected at cart and homepage) and the working Shopify cart API at /cart. An agent that can construct a cart cannot actually push it through. Compounding this, guest checkout is hidden behind "Have an account? Log in to check out faster," costing another four points and turning a frictionless Shopify default into an account wall. For a brand whose buyer is shopping bedding once every few years, forcing account creation against the agent grain is a strange choice. Checkout flow structure loses four more points because the /checkout endpoint returned 403 to the scanner and required an initialized cart to evaluate, the only forbidden response across 29 fetches. Combined with the CAPTCHA wall, this is the cluster that drags transactability down to a partial band despite full marks on rails and cart API. The fix is not engineering; it is policy. Shopify already supports everything Parachute is choosing to suppress. Product attributes are the next leakage. Across all nine sampled products, the scanner found zero structured attribute hits and only labeled text for color, size, and material. The JSON-LD Product and Offer markup is present and clean (nine of nine, full credit on 1.2 and on raw HTML pricing at 2.1), but the variant axes that an agent needs to pick the right Sateen Venice Set in Bone, King, Back Envelope are not enumerated in machine-readable form. Variant handling itself only earned one of one because variants exist, but enumerated_ratio is zero across every URL. Inventory signals tell the same story: textAvailability is true everywhere, schemaAvailability is null everywhere. Smaller but telling: check 4.4 returns zero because no terms or privacy content was reachable to classify, and check 1.4 returns partial because there is no llms.txt, no ai-plugin.json, and no AI-specific robots directive even though GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and six others are explicitly allowed. The crawler posture is welcoming, the documented policy is silent. Sitemap quality (1.3) loses two points for missing lastmod and missing product URLs in the 10-loc index. Price stability signals (6.5) score zero because no priceValidUntil or equivalent appears in any Offer. The biggest opportunity is to remove the CAPTCHA from cart and homepage and surface guest checkout, which would convert a mixed-signal storefront into a genuinely agent-ready one without touching content or schema.