ultraleds.co.uk
Audited 5 days ago· bigcommerce
Agent-readiness across all five AI commerce surfaces.
Surfaces — click to filter
20 failing · 15 not checked · 35 shown
15 checks couldn't run on this store — each is listed below with the reason. Your score reflects only what we could verify.
Populate gtin on every branded Product node
Why this matters: GTINs let agents match your product to the same item elsewhere; without them you lose cross-catalog matching.
Findings (11)
Checked 17 sampled product pages for a GTIN in the Product JSON-LD (0 carry a valid GTIN, 0%).
How: Extract gtin / gtin8 / gtin12 / gtin13 / gtin14 from the first Product JSON-LD node on each PDP; validate digit length.
Coverage
0/17 · 0%
- No valid GTIN on this product pageHIGH× 10
Populate gtin/gtin8/gtin12/gtin13/gtin14 with the manufacturer's barcode.
Affected (10)
- /
- /px24500-rgb-dmx-decoder-controller-12-24v-dc-3…
- /2-4g-rgb-colour-wheel-18a-remote-control-wifi-…
- /px24500d-4-channel-x-5a-dmx512-12-24v-decoder-…
- /single-colour-white-led-tape-remote-control-1-…
- /4-zone-rgbww-rgbcw-hand-held-controller-2-4g-1…
- /candle-c35-led-filament-bulb-b15-400lm-2700k-v…
- /pygmy-t28-led-crown-filament-lamp-e27-150lm-22…
- /4-zone-rgb-warm-white-cool-white-handheld-cont…
- /flame-tip-candle-ca35-led-filament-lamp-b15-40…
…and 1 more
Add a positive merchantReturnDays to finite-window return policies
Why this matters: AI agents quote your concrete return window in shopping cards. Without `merchantReturnDays`, your policy renders as 'has a return policy' without the headline number.
Findings (11)
Inspected 32 finite-window MerchantReturnPolicy nodes (0 carry a positive merchantReturnDays, 0%).
How: For each MerchantReturnPolicy node whose returnPolicyCategory normalizes to MerchantReturnFiniteReturnWindow, require merchantReturnDays to be a positive number (or a numeric string > 0).
Coverage
0/32 · 0%
- Finite-window MerchantReturnPolicy missing positive merchantReturnDaysHIGH× 10
What we found
(missing)What we expected
30Set
merchantReturnDaysto a positive integer (or switch the category to MerchantReturnUnlimitedWindow).Affected (10)
- /px24500-rgb-dmx-decoder-controller-12-24v-dc-3…
- /px24500-rgb-dmx-decoder-controller-12-24v-dc-3…
- /2-4g-rgb-colour-wheel-18a-remote-control-wifi-…
- /2-4g-rgb-colour-wheel-18a-remote-control-wifi-…
- /px24500d-4-channel-x-5a-dmx512-12-24v-decoder-…
- /px24500d-4-channel-x-5a-dmx512-12-24v-decoder-…
- /single-colour-white-led-tape-remote-control-1-…
- /single-colour-white-led-tape-remote-control-1-…
- /4-zone-rgbww-rgbcw-hand-held-controller-2-4g-1…
- /4-zone-rgbww-rgbcw-hand-held-controller-2-4g-1…
…and 1 more
Emit shippingDetails (OfferShippingDetails) on Offer JSON-LD
Why this matters: Without shippingDetails, AI agents fall back to vague defaults — they can't quote your rates, destinations, or delivery windows in shopping cards.
Findings (11)
Inspected shippingDetails on Product/Offer JSON-LD across 16 sampled PDPs (0 present, 0%).
How: On each PDP, locate the Product JSON-LD node and check for shippingDetails (single object or array) at Product or Offer level. Pass band ≥ 85% coverage.
Coverage
0/16 · 0%
- Offer JSON-LD missing
shippingDetailsHIGH× 10Add OfferShippingDetails with shippingRate, shippingDestination, and deliveryTime.
Affected (10)
- /px24500-rgb-dmx-decoder-controller-12-24v-dc-3…
- /2-4g-rgb-colour-wheel-18a-remote-control-wifi-…
- /px24500d-4-channel-x-5a-dmx512-12-24v-decoder-…
- /single-colour-white-led-tape-remote-control-1-…
- /4-zone-rgbww-rgbcw-hand-held-controller-2-4g-1…
- /candle-c35-led-filament-bulb-b15-400lm-2700k-v…
- /pygmy-t28-led-crown-filament-lamp-e27-150lm-22…
- /4-zone-rgb-warm-white-cool-white-handheld-cont…
- /flame-tip-candle-ca35-led-filament-lamp-b15-40…
- /golf-ball-g45-led-filament-b15-400lm-2700k-ver…
…and 1 more
Publish /.well-known/ucp with at minimum a version field
Why this matters: Without `/.well-known/ucp`, Google's AI Mode can't identify your storefront as a UCP-conformant merchant.
Findings (1)
Inspected /.well-known/ucp for a parseable JSON document with a top-level version string.
How: Confirm ctx.wellKnownUcp is non-null and carries a non-empty version string (the only universally-required UCP profile field).
- /.well-known/ucp is not reachable or not parseable as JSONHIGH
Serve a JSON document at /.well-known/ucp with a top-level
versionstring (e.g., "2026-04-08").
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)
Wanted to inspect UCP root keys, but no profile was found.
How: Read the profile root (or top-level ucp wrapper) and verify the presence of version, services, capabilities, and signing_keys keys.
- No /.well-known/ucp profile presentHIGH
Publish /.well-known/ucp first (see ucp-profile-present).
Declare a shopping service entry with a recognised transport and an HTTPS endpoint
Why this matters: Without a valid shopping service entry, agents can recognise you as a UCP merchant but have no way to fetch your catalog.
Findings (1)
Wanted to walk the UCP profile's services[] for a valid shopping entry, but no profile was found.
How: List every services[] entry whose namespace is shopping (or contains shopping) and require at least one with transport ∈ {rest,mcp,a2a,embedded} AND a syntactically valid https:// endpoint.
- No /.well-known/ucp profile presentHIGH
Publish /.well-known/ucp first (see ucp-profile-present), then declare the shopping service.
Make every signing_keys[] entry a JWK with kty + kty-specific params
Why this matters: Malformed JWK entries are rejected silently by agents — signed payloads cannot be verified and the merchant loses trust signal.
Findings (1)
Wanted to validate signing_keys[], but no UCP profile was found.
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.
- No /.well-known/ucp profile presentHIGH
Publish a Product JSON-LD block on every PDP
Why this matters: Product JSON-LD is how agents identify the canonical product entity without running JavaScript.
Findings (1)
Parsed JSON-LD on 17 sampled product pages for a Product node (16 found, 94%).
How: Walk each sampled PDP's parsed jsonLdBlocks, flatten @graph containers, and count the page as passing if any node has @type Product / ProductGroup / IndividualProduct / ProductModel.
Coverage
16/17 · 94%
- No Product JSON-LD on this PDPHIGH
Add a
<script type="application/ld+json">block with@type: Productto the PDP<head>.
Add a mailto: email link or tel: phone link to your contact page
Why this matters: Without an email or phone on your contact page, ChatGPT and Perplexity have no escalation path to surface for shoppers.
Findings (1)
Reached the contact page at https://ultraleds.co.uk/contact-us/ but found neither a mailto link, tel link, plain email, nor a phone-shaped number.
How: URL probe of contact paths; the first 2xx body is scanned for mailto: / tel: hrefs, plain emails (placeholder hosts excluded), and phone-shaped numbers.
- Contact page reachable but exposes no email, phone, mailto, or tel linkHIGH
Add a
mailto:link or atel:link to the page body.
Publish a privacy policy page and link it from your site nav/footer
Why this matters: A privacy policy is required by GDPR/CCPA and is a baseline trust signal for AI agents, ad networks, and most merchant-listing programs.
Findings (1)
Reached a privacy policy page at https://www.ultraleds.co.uk/legal/privacy but its stripped body length (48 chars) is below the 200-char substantiveness threshold.
How: Discover candidate URLs by scoring homepage nav/footer anchors for privacy/gdpr/cookie keywords, then append platform-conventional paths; probe each with politeFetch and pass on the first 2xx with ≥200 stripped-body chars.
- Privacy policy page reachable but too short to be substantiveHIGH
/legal/privacy48 chars of stripped body text (need ≥ 200)
Expand the body to cover data collection, use, sharing, and deletion rights.
Publish a terms of service page and link it from your site nav/footer
Why this matters: A published ToS is a baseline trust signal AI agents and ad networks use to decide whether to surface or accept a merchant.
Findings (1)
Reached a terms-of-service page at https://www.ultraleds.co.uk/legal/terms-and-conditions but its stripped body length (48 chars) is below the 200-char substantiveness threshold.
How: Discover candidate URLs by scoring homepage nav/footer anchors for terms/tos/legal/conditions keywords, then append platform-conventional paths; probe each with politeFetch and pass on the first 2xx with ≥200 stripped-body chars.
- Terms of service page reachable but too short to be substantiveHIGH
/legal/terms-and-conditions48 chars of stripped body text (need ≥ 200)
Expand the body to cover scope, eligibility, IP, order acceptance, and governing law.
Surface brand attribution on every PDP
Why this matters: Brand on every product is a primary agent filter and a required feed field.
Findings (1)
Checked 17 sampled product pages for brand attribution via Product JSON-LD or visible HTML signals (16 attributed, 94%).
How: On each PDP, accept brand attribution from either (a) extractBrand on the first Product JSON-LD node OR (b) an HTML brand signal (OG product:brand, brand meta, og:brand, Microdata itemprop="brand").
Coverage
16/17 · 94%
- No brand attribution on this PDP (neither JSON-LD
brandnor OG/Microdata)HIGHAdd
brandto the Product JSON-LD or a<meta property="product:brand">tag.
Skipped — No UCP profile present; Cache-Control policy is not evaluable.
Context: If your UCP profile says `no-cache`, agent runtimes re-fetch on every interaction — brittle at scale and prone to rate-limit failures.
Why this was skipped
No UCP profile present; Cache-Control policy is not evaluable.
How: Parse the Cache-Control header on the /.well-known/ucp response; require public, max-age ≥ 60, and no no-store/no-cache/private.
Skipped — No UCP profile present; Content-Type is not evaluable.
Context: Agent runtimes that gate parsing on Content-Type will skip your profile if it's served as HTML or plain text.
Why this was skipped
No UCP profile present; Content-Type is not evaluable.
How: Check that the Content-Type header on /.well-known/ucp starts with application/json (optionally with a charset parameter).
Skipped — No UCP profile reachable; public-fetch evaluation deferred to ucp-profile-present.
Context: Agents fetch `/.well-known/ucp` without credentials — a 401 or 403 means they never see the profile.
Why this was skipped
No UCP profile reachable; public-fetch evaluation deferred to ucp-profile-present.
How: Confirm an unauthenticated GET to /.well-known/ucp returns a 2xx status.
Skipped — No UCP profile present; redirect behaviour is not evaluable.
Context: Lightweight agent clients fetch `/.well-known/ucp` without following redirects — a 301/302 means they never see your profile.
Why this was skipped
No UCP profile present; redirect behaviour is not evaluable.
How: Inspect the final HTTP status of GET /.well-known/ucp and whether any 3xx redirect was followed to reach it.
Skipped — No UCP profile present.
Context: A service declared with the right transport but missing endpoint/schema is unreachable — agents can't negotiate or connect.
Why this was skipped
No UCP profile present.
How: For each services[] entry with a recognised transport, require the transport-conditional fields: rest/mcp → endpoint+schema; a2a → endpoint; embedded → schema.
Skipped — No UCP profile present.
Context: An unrecognised transport leaves agents with no handler to dispatch — your service appears absent.
Why this was skipped
No UCP profile present.
How: For each services[] entry, require transport to be one of: rest, mcp, a2a, embedded.
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.
Install a third-party review platform so agents see syndicated reviews on your storefront
Why this matters: Third-party review widgets feed the ratings AI agents trust when ranking merchants.
Findings (1)
Scanned the homepage and 17 sampled PDPs for 8 review-platform asset fingerprints; none matched.
How: Substring scan of homepage and sampled PDP HTML for known review-platform asset fingerprints (judge.me, yotpo, stamped.io, reviews.io, okendo, loox, trustpilot, bazaarvoice).
- No third-party review-platform integration detectedMEDIUM
none of 8 fingerprints matched across 18 sources
Install a Judge.me / Yotpo / Loox / Okendo / Stamped / Reviews.io / Trustpilot / Bazaarvoice widget on your storefront.
Publish a returns policy page and link it from your site nav/footer
Why this matters: AI agents quote return terms to shoppers; missing returns pages are a baseline trust failure that suppresses you from agentic shopping cards.
Findings (1)
Reached a returns/refund policy page at https://www.ultraleds.co.uk/customer-care/returns but its stripped body length (48 chars) is below the 200-char substantiveness threshold.
How: Discover candidate URLs by scoring homepage nav/footer anchors for return/refund/exchange keywords, then append platform-conventional paths; probe each with politeFetch and pass on the first 2xx with ≥200 stripped-body chars.
- Returns policy page reachable but too short to be substantiveMEDIUM
/customer-care/returns48 chars of stripped body text (need ≥ 200)
Expand the body to at least 200 characters covering window, conditions, and refund process.
Publish a shipping policy page and link it from your site nav/footer
Why this matters: Agents quote shipping terms to shoppers; without a reachable shipping policy they fall back to vague defaults or skip your store.
Findings (1)
Reached a shipping policy page at https://www.ultraleds.co.uk/customer-care/delivery but its stripped body length (48 chars) is below the 200-char substantiveness threshold.
How: Discover candidate URLs by scoring homepage nav/footer anchors for shipping/delivery/dispatch keywords, then append platform-conventional paths; probe each with politeFetch and pass on the first 2xx with ≥200 stripped-body chars.
- Shipping policy page reachable but too short to be substantiveMEDIUM
/customer-care/delivery48 chars of stripped body text (need ≥ 200)
Expand the body to at least 200 characters covering carriers, costs, and delivery timeframes.
Skipped — No MerchantReturnPolicy node carried a `merchantReturnLink` URL, so reachability has nothing to evaluate.
Context: A broken return-link makes Option B policies invisible — agents can't render or follow the link.
Why this was skipped
No MerchantReturnPolicy node carried a merchantReturnLink URL, so reachability has nothing to evaluate.
How: Collect every unique merchantReturnLink URL across all MerchantReturnPolicy nodes; probe each once via politeFetch (failSoft). 2xx counts as reachable.
Skipped — No OfferShippingDetails node carried `shippingDestination`, so the DefinedRegion check has nothing to evaluate.
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
No OfferShippingDetails node carried shippingDestination, so the DefinedRegion check has nothing to evaluate.
How: On each OfferShippingDetails node where shippingDestination is set, require it to be a DefinedRegion (or array) and every entry to carry addressCountry matching /^[A-Z]{2}$/i.
Skipped — No OfferShippingDetails node carried `shippingRate`, so the MonetaryAmount check has nothing to evaluate.
Context: An invalid rate object is silently dropped; agents can't quote your shipping cost in shopping cards.
Why this was skipped
No OfferShippingDetails node carried shippingRate, so the MonetaryAmount check has nothing to evaluate.
How: On each OfferShippingDetails node where shippingRate is set, require an object with numeric value/maxValue (typed or numeric string) and a 3-letter ISO 4217 currency.
Skipped — No UCP profile present.
Context: Capabilities missing version/spec/schema can't be matched against agent support tables — agents skip them silently.
Why this was skipped
No UCP profile present.
How: For each capabilities[] entry, require non-empty string values for version, spec, and schema.
Skipped — No UCP profile present.
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 UCP profile present.
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.
Skipped — No UCP profile present; service version formats are not evaluable.
Context: Free-form version labels like `1.0` or `latest` defeat the version-pinning agents rely on, leaving them unable to negotiate the correct spec generation.
Why this was skipped
No UCP profile present; service version formats are not evaluable.
How: For each services[] entry, require version to be a string matching /^\d{4}-\d{2}-\d{2}$/.
Upload higher-resolution product images (area ≥ 50,000 pixels)
Why this matters: Tiny product images get dropped from Google’s shopping rich-result modules and are unhelpful to AI agents quoting your product visually.
Findings (11)
Inspected <img width=… height=…> attributes on 17 sampled product pages (0 have at least one image with area ≥ 50,000 px; dimensions absent from HTML are not HEAD-probed and count as indeterminate).
How: For every sampled PDP, parse <img> tags and read explicit width and height attributes; a PDP passes when at least one image has width × height ≥ 50,000. PDPs without any explicit-dimension <img> are marked indeterminate (this check does not HEAD image URLs).
Coverage
0/17 · 0%
- No <img> on this PDP carries explicit width+height attributesLOW
/305 <img> tags found, none with width+height
Server-render explicit width and height attributes so crawlers can verify image area without fetching.
- All images on this PDP are below the 50,000-pixel thresholdLOW× 9
Upload an image whose width × height ≥ 50,000 (e.g., 400 × 300 = 120,000).
Affected (9)
- /px24500-rgb-dmx-decoder-controller-12-24v-dc-3…largest image area observed: 1,089 px
- /2-4g-rgb-colour-wheel-18a-remote-control-wifi-…largest image area observed: 1,089 px
- /px24500d-4-channel-x-5a-dmx512-12-24v-decoder-…largest image area observed: 1,089 px
- /single-colour-white-led-tape-remote-control-1-…largest image area observed: 1,089 px
- /4-zone-rgbww-rgbcw-hand-held-controller-2-4g-1…largest image area observed: 1,089 px
- /candle-c35-led-filament-bulb-b15-400lm-2700k-v…largest image area observed: 1,089 px
- /pygmy-t28-led-crown-filament-lamp-e27-150lm-22…largest image area observed: 1,089 px
- /4-zone-rgb-warm-white-cool-white-handheld-cont…largest image area observed: 1,089 px
- /flame-tip-candle-ca35-led-filament-lamp-b15-40…largest image area observed: 1,089 px
…and 1 more
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)
Reached an About page at https://ultraleds.co.uk/about-us/ but its stripped body length (48 chars) is below the 200-char substantiveness threshold.
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.
- About page reachable but too short to be substantiveLOW
/about-us/48 chars of stripped body text (need ≥ 200)
Expand the body to at least 200 characters covering brand, mission, and team.
Skipped — No MerchantReturnPolicy node carried returnFees, returnMethod, or refundType, so the enum check has nothing to evaluate.
Context: Invalid enrichment values are dropped silently, leaving merchants confused about why their rendered policy is missing fields they configured.
Why this was skipped
No MerchantReturnPolicy node carried returnFees, returnMethod, or refundType, so the enum check has nothing to evaluate.
How: On each MerchantReturnPolicy node, inspect returnFees/returnMethod/refundType if set; require the bare name or schema.org URL form of a value in the corresponding Schema.org enum.
Skipped — No OfferShippingDetails node carried `deliveryTime`, so the ShippingDeliveryTime check has nothing to evaluate.
Context: Without populated handling/transit times, agents can't quote a delivery window in shopping cards.
Why this was skipped
No OfferShippingDetails node carried deliveryTime, so the ShippingDeliveryTime check has nothing to evaluate.
How: On each OfferShippingDetails node where deliveryTime is set, require an object with at least one of handlingTime / transitTime populated as a QuantitativeValue.
Skipped — No UCP profile found; MCP transport validity is not evaluable.
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
No UCP profile found; MCP transport validity is not evaluable.
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 17 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 17 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.