Some cookies are necessary for SecondDoor to work. Others are optional, and tell us how the site and the product are used. Accept all, or decline all optional ones. Without a selection, nothing optional is set. More in our cookie policy.
Basic scanRetail storefront · Storefront property/Scanned 8 Sept 2026, 14:41 UTC/1 browser pass
A browser-blocking storefront that welcomes AI crawlers in robots.txt but refuses them at the network edge, breaking assistant shopping while publishing the data agents need.
Older scan
This report was produced by an earlier version of the scanner. Some findings may not match how the site is measured now.
Present. Agents lose ground at specific gates, not everywhere.
Ordered by what the evidence says is costing most. Written for whoever owns the site, not whoever builds it.
3 pieces of evidence and the recommended fix are recorded for this issue.
This is a basic scan, so it raises the three issues the deterministic evidence supports. A deep scan sends two agents over the site and raises up to ten, each with cited evidence and the screens to prove it.
A deep scan walks the site with two agents, records cited evidence and screenshots, and keeps a mission timeline. It comes with the paid plans. Making an account costs nothing and gives you one basic scan a month.
The score and the audit trail stay public. The evidence and the files open with an account.
The audit trail behind every number above. Not measured is not zero.
Machine discoverability
The site publishes a sitemap listing 54 URLs including product pages, declares llms.txt, and serves 10 schema.org types on the homepage. A real browser is refused entirely, which is how assistant shopping arrives, and the network edge.
4 observations recorded.
Programmatic onboarding
No API documentation is linked from the homepage or discoverable in the raw HTML. No OpenAPI spec exists at any of the 6 standard paths. The site publishes a UCP manifest for transactional capability but offers no developer surface to.
3 observations recorded.
Pricing legibility
Prices appear in the raw HTML of all 3 product pages checked, with 9 prices on the homepage itself. Product structured data publishes price and currency on every offer. The visible price ($11.62) matches the structured data.
2 observations recorded.
Agent-aware instrumentation
A Universal Commerce Protocol manifest is published with 8 capabilities and 3 payment handlers, and a storefront MCP endpoint answers agent calls. The catalogue answers as data at /products.json with brand on each product.
4 observations recorded.
Machine-fetchable trust
The returns policy and shipping policy both read as text at their published URLs. Return policy is also in structured data. Shipping terms are in structured data. The homepage answers automated requests. No security.txt is published.
3 observations recorded.
Commercial rails
Product markup carries price, currency, identifier and brand. The catalogue answers as data at /products.json, ready for feed syndication. Return policy is in structured data and reads as text. Shipping policy reads as text.
4 observations recorded.
Steps to first value
A product with its price ($11.62) and an add-to-cart control is reachable in 2 steps from the homepage. The price is visible on the page. No account is required to proceed.
1 observation recorded.
Required fields
The product page does not demand an account before buying. Four express wallets (Apple Pay, Shop Pay, PayPal, Google Pay) skip the form entirely. The page carries 8 input fields with 1 constraint and 5 live regions for validation feedback.
1 observation recorded.
Verification walls
No sign-in requirement appears on the product page. The site does not force account creation before checkout. Express payment options bypass form entry.
1 observation recorded.
Error recovery
Three size or colour choosers on the product page let a shopper correct a selection before adding to cart. The page includes 1 inline error container and 5 live regions for validation feedback.
1 observation recorded.
It got through 10 of 17.
The agent got through 10 of 17 requests, but could not ask whether the door opens for requests carrying the AI crawlers' names. It came up empty on 6 other checks too.