birdsnest.com.au — AI Commerce Audit

HALFCRITICAL

HTTPS enforced sitewide + HSTS (≥ 6-month max-age)https-and-hsts-enforcedHSTS

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.

RFC 6797 — HTTP Strict Transport Security (HSTS)

−2.9impact

Findings (1)

Confirmed the homepage is HTTPS (status 200), probed http://birdsnest.com.au/ for redirect behaviour, and parsed the Strict-Transport-Security header (value: "max-age=7889238").

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 = 7889238s (need ≥ 15552000s = 180 days)
What we found
```
max-age=7889238
```
What we expected
```
Strict-Transport-Security: max-age=31536000; includeSubDomains
```
Bump max-age to at least 15552000 (180 days). 31536000 (1 year) is required for preload-list inclusion.

How to fix · 3 steps · create a free account to viewCreate a free account →

FAILHIGH

GTIN coverage on PDPsproduct-gtin-populatedSchema.orgMerchant

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.

schema.org/Product.gtin

−1.9impact

Findings (11)

Checked 20 sampled product pages for a GTIN in the Product JSON-LD (3 carry a valid GTIN, 15%).

How: Extract gtin / gtin8 / gtin12 / gtin13 / gtin14 from the first Product JSON-LD node on each PDP; validate digit length.

Coverage

3/20 · 15%

No valid GTIN on this product pageHIGH× 10
Populate gtin/gtin8/gtin12/gtin13/gtin14 with the manufacturer's barcode.
Affected (10)

…and 1 more

How to fix · 2 steps · create a free account to viewCreate a free account →

FAILHIGH

UCP profile carries all four required top-level keysucp-profile-required-keysUCP

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.

UCP overview — required profile keys

−1.5impact

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_keys is missingHIGH
/.well-known/ucp
What we expected
```
Add a top-level "signing_keys" field to the JSON document (empty array/object is fine).
```
Set signing_keys at the root of the JSON document.

How to fix · 2 steps · create a free account to viewCreate a free account →

HALFHIGH

Product JSON-LD present on PDPsproduct-jsonld-presentSchema.orgMerchant

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.

schema.org/Product

−1.2impact

Findings (3)

Parsed JSON-LD on 20 sampled product pages for a Product node (17 found, 85%).

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

17/20 · 85%

No Product JSON-LD on this PDPHIGH× 3
Add a <script type="application/ld+json"> block with @type: Product to the PDP <head>.
Affected (3)

How to fix · 3 steps · create a free account to viewCreate a free account →

HALFHIGH

Brand attribution on PDPsproduct-brand-attributionSchema.orgMerchant

Surface brand attribution on every PDP

Why this matters: Brand on every product is a primary agent filter and a required feed field.

schema.org/Product.brand

−0.9impact

Findings (3)

Checked 20 sampled product pages for brand attribution via Product JSON-LD or visible HTML signals (17 attributed, 85%).

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

17/20 · 85%

No brand attribution on this PDP (neither JSON-LD brand nor OG/Microdata)HIGH× 3
Add brand to the Product JSON-LD or a <meta property="product:brand"> tag.
Affected (3)

How to fix · 3 steps · create a free account to viewCreate a free account →

NAHIGH

UCP profile Cache-Control is shared-cacheable with max-age ≥ 60sucp-cache-headers-validUCP

Skipped — the runner did not surface transport metadata

Context: If your UCP profile says `no-cache`, agent runtimes re-fetch on every interaction — brittle at scale and prone to rate-limit failures.

UCP overview — profile caching

Not scoredimpact

Why this was skipped

Wanted to inspect the UCP profile's Cache-Control header, but the runner did not surface transport metadata.

How: Parse the Cache-Control header on the /.well-known/ucp response; require public, max-age ≥ 60, and no no-store/no-cache/private.

Transport metadata not available — runner update pendingLOW
/.well-known/ucp
This check activates once the runner (Task I1) populates ctx.wellKnownUcp.cacheControl.

NAHIGH

Every signing_keys[] entry is a valid JWKucp-signing-keys-validJWKS

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.

RFC 7517 — JSON Web Key (JWK)

Not scoredimpact

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.

FAILMEDIUM

Product `description` presentproduct-description-presentSchema.orgMerchant

Populate description on every Product JSON-LD node

Why this matters: Agents quote your description to answer shopper questions; an empty description gives them nothing to work with.

schema.org/Product.description

−1.3impact

Findings (11)

Read description on Product JSON-LD across 17 sampled product pages (5 non-empty after HTML strip, 29%).

How: Read description on each Product node; strip HTML tags and collapse whitespace; require length > 0.

Coverage

5/17 · 29%

Product JSON-LD has no description (empty after HTML strip)MEDIUM× 10
Fill in the product description in your store admin; the JSON-LD template typically binds to that field.
Affected (10)

…and 1 more

How to fix · 2 steps · create a free account to viewCreate a free account →

FAILMEDIUM

Product `sku` populatedproduct-sku-populatedSchema.orgMerchant

Populate sku on every Product JSON-LD node

Why this matters: A stable SKU lets agents track and re-identify your product across catalogs.

schema.org/Product.sku

−1.1impact

Findings (11)

Read the sku field on Product JSON-LD across 17 sampled product pages (5 populated, 29%).

How: On each PDP with a Product node, accept sku if it is a non-empty trimmed string or a number.

Coverage

5/17 · 29%

Product JSON-LD has no populated skuMEDIUM× 10
Fill in the SKU field in your product admin; the JSON-LD template typically binds to that field.
Affected (10)

…and 1 more

How to fix · 2 steps · create a free account to viewCreate a free account →

FAILMEDIUM

HSTS policy carries the includeSubDomains directivehsts-include-subdomainsHSTS

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.

RFC 6797 — HSTS `includeSubDomains` directive

−1.1impact

Findings (1)

Inspected the homepage Strict-Transport-Security header ("max-age=7889238") 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=7889238
```
What we expected
```
Strict-Transport-Security: max-age=31536000; includeSubDomains
```
Append ; includeSubDomains to your STS header once every subdomain you operate supports HTTPS.

How to fix · 2 steps · create a free account to viewCreate a free account →

NAMEDIUM

MerchantReturnPolicy merchantReturnLink URL is reachablemerchant-return-link-reachableReturns

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.

Google return-policy SD — merchantReturnLink reachability

Not scoredimpact

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.

NAMEDIUM

Each capability has version + spec + schemaucp-capability-required-fieldsUCP

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.

UCP overview — capabilities

Not scoredimpact

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.

FAILLOW

Product images meet Google’s 50,000-pixel area thresholdimage-area-50k-pixelsMerchant

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.

Image quality (≥50K pixels area)

−0.4impact

Findings (11)

Inspected <img width=… height=…> attributes on 20 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/20 · 0%

No <img> on this PDP carries explicit width+height attributesLOW× 4
Server-render explicit width and height attributes so crawlers can verify image area without fetching.
Affected (4)
- /products/bird-keepers-the-comfort-true-knit-dr…316 <img> tags found, none with width+height
- /products/winning-combination-printed-maxi-skir…308 <img> tags found, none with width+height
- /products/head-turning-handpicked-cord299 <img> tags found, none with width+height
- /products/foxwood-elements-scoop-rib-cotton-ble…304 <img> tags found, none with width+height
All images on this PDP are below the 50,000-pixel thresholdLOW× 6
Upload an image whose width × height ≥ 50,000 (e.g., 400 × 300 = 120,000).
Affected (6)
- /products/off-duty-energy-18408588largest image area observed: 2,916 px
- /products/rosewood-romance-18408624largest image area observed: 2,916 px
- /products/quiet-luxe-18408596largest image area observed: 2,916 px
- /products/black-tie-waist-knit-with-sand-longli…largest image area observed: 2,916 px
- /products/dark-navy-knit-dress-with-denim-jacke…largest image area observed: 2,916 px
- /products/wine-blazer-with-burgundy-skivvy-blac…largest image area observed: 2,916 px

…and 1 more

How to fix · 2 steps · create a free account to viewCreate a free account →

FAILLOW

HSTS policy carries the preload directivehsts-preload-directiveHSTS

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.

RFC 6797 — HSTS `preload` directive (vendor extension)

−0.3impact

Findings (1)

Inspected the homepage Strict-Transport-Security header ("max-age=7889238") 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=7889238
```
What we expected
```
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
```
Append ; preload after includeSubDomains and submit your domain at https://hstspreload.org/.

How to fix · 3 steps · create a free account to viewCreate a free account →

FAILLOW

Product `aggregateRating` presentproduct-aggregate-rating-presentSchema.org

Add an AggregateRating to Product nodes when you have real reviews

Why this matters: Review ratings are a trust signal agents use to rank and filter products.

schema.org/AggregateRating

−0.2impact

Findings (11)

Looked for a valid aggregateRating on Product JSON-LD across 17 sampled product pages (0 valid, 0%).

How: On each Product node, parse aggregateRating (or the first element if it's an array) and require ratingValue in [0,5] AND reviewCount or ratingCount ≥ 1.

Coverage

0/17 · 0%

Product has no valid AggregateRating (ratingValue 0-5 + reviewCount/ratingCount ≥ 1)LOW× 10
Render aggregateRating from real review totals — never fabricate.
Affected (10)

…and 1 more

How to fix · 2 steps · create a free account to viewCreate a free account →

FAILINFO

Apple Pay markers detected (informational)apple-pay-detectedSchema.org

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.

Apple Pay availability — payment options observed

No score impactimpact

Findings (1)

Scanned the homepage and 20 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.

How to fix · 3 steps · create a free account to viewCreate a free account →

FAILINFO

Google Pay markers detected (informational)google-pay-detectedSchema.org

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.

Google Pay availability — payment options observed

No score impactimpact

Findings (1)

Scanned the homepage and 20 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.

How to fix · 3 steps · create a free account to viewCreate a free account →

13 failing · 4 not checked · 17 shown