toywiz.com
Audited 5 days ago· bigcommerce
Agent-readiness across all five AI commerce surfaces.
Surfaces — click to filter
13 failing · 37 not checked · 50 shown
37 checks couldn't run on this store — each is listed below with the reason. Your score reflects only what we could verify.
Enforce HTTPS sitewide and ship a Strict-Transport-Security header with max-age ≥ 6 months
Why this matters: AI agents and payment flows refuse plain HTTP; weak HSTS is treated as effectively no HSTS by trust-and-safety scanners.
Findings (1)
Confirmed the homepage is HTTPS (status 200), probed http://toywiz.com/ for redirect behaviour, and parsed the Strict-Transport-Security header (value: "max-age=0").
How: URL scheme + homepage status check, an http://host/ redirect probe through politeFetch, and a Strict-Transport-Security max-age parse (RFC 6797; ≥ 180-day threshold).
- HSTS max-age is below the 6-month minimumCRITICAL
/parsed max-age = 0s (need ≥ 15552000s = 180 days)
What we found
max-age=0What we expected
Strict-Transport-Security: max-age=31536000; includeSubDomainsBump
max-ageto at least 15552000 (180 days). 31536000 (1 year) is required for preload-list inclusion.
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Agents need a price with a currency to show and compare your product.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Make product pages discoverable without JavaScript
Why this matters: AI shopping crawlers do not run JavaScript; without server-rendered product pages, agents can't see your catalog.
Findings (1)
Counted product pages discovered by the non-JavaScript crawl. None were found — JS-only storefront, products missing from sitemap, or the crawl was blocked.
How: Count the product pages a non-JavaScript crawl could discover via the sitemap or initial HTML (no JS execution). The fetcher already attempted discovery; we read ctx.pdpSample.
- No product pages discoverable from a non-JavaScript crawlHIGH
/0 products in pdpSample after sitemap + HTML link discovery
Server-render product pages and list every product URL in the sitemap.
Publish a product feed or a crawlable product sitemap
Why this matters: Agents build their catalog from a feed or by crawling product pages; if neither yields products, your store is invisible.
Findings (1)
Ran the discovery cascade (feed → platform catalog → typed sitemap → content-verified crawl). Method: none; verified 0 product pages of 37 sampled.
How: Read the product-discovery cascade result from ctx.discovery. Score by discovery method (feed / platform_api / sitemap_typed → pass when verifiedProductCount ≥ MIN_CONFIDENT_PRODUCTS; content_verified → partial; none or under-threshold → fail).
- No reliable way for agents to discover your productsHIGH
/method=none, verified=0
Publish a product feed (Google Merchant XML or ACP) and declare it in /.well-known/ucp and /llms.txt, or ensure every product page carries Product JSON-LD and is listed in the sitemap.
Add every required top-level key to the UCP profile
Why this matters: A profile missing one of the four required keys is treated as non-conformant — agent runtimes fall back to default behaviour and may skip the merchant.
Findings (1)
Profile is missing required key(s): signing_keys.
How: Read the profile root (or top-level ucp wrapper) and verify the presence of version, services, capabilities, and signing_keys keys.
- Required top-level key
signing_keysis missingHIGHWhat we expected
Add a top-level "signing_keys" field to the JSON document (empty array/object is fine).Set
signing_keysat the root of the JSON document.
Populate the conditional fields required by each service's transport
Why this matters: A service declared with the right transport but missing endpoint/schema is unreachable — agents can't negotiate or connect.
Findings (1)
Validated 1 services with recognised transports (0 satisfy their transport's required fields).
How: For each services[] entry with a recognised transport, require the transport-conditional fields: rest/mcp → endpoint+schema; a2a → endpoint; embedded → schema.
Coverage
0/1 · 0%
- Service is missing transport-conditional field(s)HIGH
/.well-known/ucpnamespace=dev.ucp.shopping; transport=rest
What we found
missing: schemaWhat we expected
`endpoint` + `schema`Add schema to this services[] entry.
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: AI agents quote your concrete return window in shopping cards. Without `merchantReturnDays`, your policy renders as 'has a return policy' without the headline number.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: A policy node missing both shapes is invisible to agents — they can't render it, link to it, or quote your return terms.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Without the entry-point return-policy node, agents can't render or quote your return terms — they fall back to platform defaults or skip your store.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Agents suppress out-of-stock or ambiguous items; a valid availability URL keeps you eligible.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Without shippingDetails, AI agents fall back to vague defaults — they can't quote your rates, destinations, or delivery windows in shopping cards.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: PDPs behind a login wall are silently dropped from Google's merchant listing and from every AI agent surface.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: A noindex on the PDP makes it invisible to Google and ineligible for the merchant listing program.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Duplicate Product nodes on a single PDP cause Google's merchant scraper to drop the listing or pick the wrong variant.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Brand on every product is a primary agent filter and a required feed field.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: GTINs let agents match your product to the same item elsewhere; without them you lose cross-catalog matching.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Agents show your product image in shopping cards; a missing image weakens or drops the listing.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Product JSON-LD is how agents identify the canonical product entity without running JavaScript.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: A product's name is the minimum an agent needs to list it.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Without an Offer, agents can't see that the product is for sale.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Profile declares no signing_keys; JWK validation has no entries to evaluate.
Context: Malformed JWK entries are rejected silently by agents — signed payloads cannot be verified and the merchant loses trust signal.
Why this was skipped
Profile declares no signing_keys; JWK validation has no entries to evaluate.
How: Walk signing_keys[] and validate each entry per RFC 7517 §4.1 (kty required) + RFC 7518 §6 (kty-specific required parameters). kid is OPTIONAL per RFC 7517 §4.5 and not enforced here.
Add includeSubDomains to your Strict-Transport-Security header
Why this matters: Without includeSubDomains, an HTTP subdomain (staging, mail, …) can be used to attack the apex's cookies.
Findings (1)
Inspected the homepage Strict-Transport-Security header ("max-age=0") and the includeSubDomains directive is absent.
How: Parse the homepage Strict-Transport-Security header for the includeSubDomains directive (RFC 6797 §6.1.2).
- HSTS header is missing the includeSubDomains directiveMEDIUM
What we found
max-age=0What we expected
Strict-Transport-Security: max-age=31536000; includeSubDomainsAppend
; includeSubDomainsto your STS header once every subdomain you operate supports HTTPS.
Add an Organization (or OnlineStore) JSON-LD block to your homepage with a contactPoint
Why this matters: Organization markup with a contactPoint tells AI agents who you are and how a shopper can reach you for support.
Findings (1)
Parsed the homepage JSON-LD looking for an Organization/OnlineStore node with a contactPoint, but no Organization-class node is present.
How: Parse homepage <script type="application/ld+json"> blocks, flatten @graph, and look for an Organization/OnlineStore/Store node with a contactPoint carrying email or telephone.
- No Organization/OnlineStore JSON-LD on homepageMEDIUM
What we expected
<script type="application/ld+json">{"@context":"https://schema.org","@type":"OnlineStore","name":"Example Store","url":"https://example.com","contactPoint":[{"@type":"ContactPoint","contactType":"customer service","email":"support@example.com"}]}</script>Add an Organization (or OnlineStore) JSON-LD block in the homepage
<head>with a contactPoint.
Add a Sitemap: line to robots.txt
Why this matters: Declaring the sitemap in robots.txt is the simplest way to point every crawler at your full product list.
Findings (1)
Read robots.txt and looked for a Sitemap: directive; none were declared.
How: Read parsed Sitemap: directives from robots.txt (sitemaps.org / RFC 9309 implementation note).
- robots.txt has no Sitemap: directiveMEDIUM
/robots.txt0 Sitemap: lines parsed
What we expected
Sitemap: https://yourdomain.com/sitemap.xmlAdd a top-level
Sitemap:line pointing at your XML sitemap (or sitemap index).
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: A broken return-link makes Option B policies invisible — agents can't render or follow the link.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: A non-ISO country is dropped silently; the policy looks present but never reaches the merchant-listing rich result.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: An invalid category is silently dropped — your policy looks present in the source but never renders in Google's return-policy rich result.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Without a valid destination region, your shipping rate has no scope — Google can't decide whether to render it for a given shopper's country.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: An invalid rate object is silently dropped; agents can't quote your shipping cost in shopping cards.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Brand on every product is a primary agent filter and a required feed field.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Agents quote your description to answer shopper questions; an empty description gives them nothing to work with.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: A stable SKU lets agents track and re-identify your product across catalogs.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Placeholder titles like Default Title make products look broken to agents.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Profile declares no capabilities; required-field checks have nothing to evaluate.
Context: Capabilities missing version/spec/schema can't be matched against agent support tables — agents skip them silently.
Why this was skipped
Profile declares no capabilities; required-field checks have nothing to evaluate.
How: For each capabilities[] entry, require non-empty string values for version, spec, and schema.
Skipped — No services declared a `spec` URL; origin matching has nothing to evaluate.
Context: A spec URL on an unrelated authority signals the service was copy-pasted from stale documentation — agents can't trust the conformance claim.
Why this was skipped
No services declared a spec URL; origin matching has nothing to evaluate.
How: For each service with a spec URL, require the URL origin to be a canonical UCP authority OR the host/path to include the namespace token.
Add preload to your Strict-Transport-Security header and submit to hstspreload.org
Why this matters: HSTS preload-list inclusion is the strongest downgrade protection available — first-time visits are protected too.
Findings (1)
Inspected the homepage Strict-Transport-Security header ("max-age=0") and the preload directive is absent.
How: Parse the homepage Strict-Transport-Security header for the preload directive (hstspreload.org vendor extension to RFC 6797).
- HSTS header is missing the preload directiveLOW
What we found
max-age=0What we expected
Strict-Transport-Security: max-age=31536000; includeSubDomains; preloadAppend
; preloadafterincludeSubDomainsand submit your domain at https://hstspreload.org/.
Split over-cap sitemaps into a sitemap index
Why this matters: Over-cap sitemaps are silently dropped — neither byte overflow nor entry overflow surfaces a crawler error.
Findings (1)
Checked 1 sitemap resource(s) against the 50 MiB / 50,000-URL caps; 1 breach(es) found.
How: Check raw byte size (≤ 52,428,800 B) and entry count (≤ 50,000) for every resolved sitemap resource.
- Sitemap exceeds 50,000-URL cap (99,087 entries)LOW
/sitemap.xmlactual: 99087 entries; cap: 50000
Paginate into multiple sitemaps and reference them from a sitemap index.
Publish a substantive About page at a standard URL
Why this matters: Perplexity and ChatGPT use About-page text to summarise your brand to shoppers in answer responses.
Findings (1)
Probed 5 candidate About-page paths and none returned a 2xx body.
How: URL probe of platform-specific about-page paths via politeFetch; the first 2xx response whose HTML-stripped body length is ≥ 200 chars counts as a pass.
- No About page reachable at any standard URLLOW
statuses: /about-us/=404, /about/=404, /about=404, /about-us=404, /pages/about=404
Publish an About page at /about (or your platform's standard path) with ≥ 200 chars of body text.
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Breadcrumbs help agents understand where a product sits in your catalog.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Alt text is the only text description AI agents and screen readers have for your product imagery.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Tiny product images get dropped from Google’s shopping rich-result modules and are unhelpful to AI agents quoting your product visually.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Invalid enrichment values are dropped silently, leaving merchants confused about why their rendered policy is missing fields they configured.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: When you declare itemCondition, agents and Google require a canonical Schema.org IRI; free-text values get ignored.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Without populated handling/transit times, agents can't quote a delivery window in shopping cards.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Review ratings are a trust signal agents use to rank and filter products.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
Context: Empty or all-caps product titles signal low quality to agents and trigger Google Merchant Center policy flags.
Why this was skipped
Couldn't confidently identify product pages — only 0 of 37 sampled URLs carried product structured data, so product-level checks aren't applicable.
How: n/a
Skipped — Walked services[] for `transport: "mcp"` entries; none advertised.
Context: If you advertise MCP transport, agents will try to connect — broken or non-HTTPS endpoints fail silently and lose the integration.
Why this was skipped
Walked services[] for transport: "mcp" entries; none advertised.
How: Filter services[] to entries where transport=mcp and validate that endpoint is an absolute https:// URL.
Enable Apple Pay through your payment processor (informational only)
Why this matters: Apple Pay is a checkout-quality signal for human shoppers — informational only, does not affect the agent-readiness score.
Findings (1)
Scanned the homepage and 0 sampled PDPs for Apple Pay markers; none matched.
How: Substring match on known Apple Pay SDK/markup signatures (ApplePaySession, apple-pay-button, /apple-developer-merchantid-domain-association) across the homepage and every sampled PDP HTML.
- No Apple Pay markers detected on the homepage or PDPsINFO
Enable Apple Pay in your payment processor's dashboard (Stripe / Adyen / Braintree). Informational only — does not affect the score.
Enable Google Pay through your payment processor (informational only)
Why this matters: Google Pay is a checkout-quality signal for human shoppers — informational only, does not affect the agent-readiness score.
Findings (1)
Scanned the homepage and 0 sampled PDPs for Google Pay markers; none matched.
How: Substring match on known Google Pay SDK/markup signatures (pay.google.com/gp/p/js/pay.js, google.payments.api, <google-pay-button) across the homepage and every sampled PDP HTML.
- No Google Pay markers detected on the homepage or PDPsINFO
Enable Google Pay in your payment processor's dashboard (Stripe / Adyen / Braintree). Informational only — does not affect the score.
Skipped — Looked for /llms.txt at the site root; the fetcher returned no file.
Context: An /llms.txt manifest points agents at your feed and key pages without them having to guess.
Why this was skipped
Looked for /llms.txt at the site root; the fetcher returned no file.
How: Check whether the fetcher reached an /llms.txt at the site root. Informational only — no failure path per llmstxt.org being a voluntary community convention.