Agentic Commerce Readiness Audit

3/9

score

Accessible but Under-Structured

Content is reachable, but the machine-readable layer is thin. Schema and description depth are the constraints.

Area breakdown

1. Crawlability

1/3

2. Structured data

2/4

3. Content quality

0/2

The 9 criteria

✗ C1

AI crawler access

5 AI bots blocked in robots.txt.

✓ C2

PDP server-side render

3/3 sampled PDPs render title, price, description in raw HTML.

✗ C3

Sitemap freshness

Sitemap missing, invalid, or stale.

✓ C4

Product schema

3/3 PDPs ship valid Product JSON-LD with required fields.

✗ C5

AggregateRating

2/3 PDPs ship Review or AggregateRating schema.

✓ C6

FAQPage / HowTo schema

FAQPage/HowTo schema found on 1 checked page(s).

✗ C7

Organization schema

Organization schema missing: name, url, sameAs.

✗ C8

PDP titles

2/5 sampled titles include differentiator cues.

✗ C9

Description depth

3/5 descriptions answer buyer-context questions.

What needs fixing

The top 9-criterion grid shows all checks. Detail below covers only items that need action.

C1 AI crawler access Fail

Checked: Nécessaire/robots.txt
Found: The following AI crawlers are blocked by explicit Disallow rules: GPTBot, PerplexityBot, anthropic-ai, Google-Extended, CCBot.
Fix: Add explicit Allow rules for the tested AI crawlers, or remove the Disallow: / entries that match them. AI shopping surfaces rely on these bots to index product data.

C3 Sitemap freshness Fail

Checked: Nécessaire/sitemap.xml
Found: Sitemap missing, invalid XML, or has no <lastmod> timestamp within the past 90 days.
Fix: Generate a valid sitemap that includes product URLs with accurate <lastmod> timestamps, and keep it current. Shopify emits this automatically for standard themes.

C5 AggregateRating Fail

Checked: 3 sampled PDPs — Review / AggregateRating schema
Found: 2/3 PDPs expose rating data as JSON-LD with real ratingValue and reviewCount. Others likely display reviews visually but don't emit structured data — typically a widget toggle that hasn't been enabled.
Fix: Enable review-schema output in your review plugin (Yotpo, Judge.me, Okendo, etc.) — often a single setting. See schema.org/AggregateRating.

C7 Organization schema Fail

Checked: Homepage for Organization JSON-LD
Found: Organization schema missing or incomplete. Missing: name, url, sameAs. sameAs should link to at least 2 social profiles for entity recognition.
Fix: Add (or extend) Organization JSON-LD in the site-wide <head>: name, url, logo, and a sameAs array of verified social-profile URLs. Low risk, high leverage for AI entity recognition.

C8 PDP titles Fail

Checked: 5 PDP titles sampled from the sitemap
Found: Only 2/5 titles include specific use-case, target audience, or differentiator cues. Examples: "The Body Lotion 70 ml | Multi-Peptide | Olibanum", "The Body Lotion 450 ml | Multi-Peptide".
Fix: Expand generic titles ("Brand Name Face Cream") with specific differentiators ("Retinol Alternative Night Serum for Sensitive Skin"). Titles match the natural-language shopper queries AI agents parse.

C9 Description depth Fail

Checked: 5 sampled PDPs — full description text
Found: 3/5 descriptions cover 3+ of: target skin/fit type, comparison to similar products, ingredient/material rationale, sizing reasoning, usage guidance, counter-indications. Most are spec-heavy with limited buyer context.
Caveat: Evaluation via rendered-response text. Descriptions may include buyer-context content in expandable sections or tabs that weren't surfaced.
Fix: Add a structured "Why you'll love it" block to every PDP — who it's for, how it compares, when to use, what it isn't for. At catalog scale this is a content pipeline (LLM-assisted generation from existing spec sheets is plausible).

View complete check log (all 9 criteria)

✗ C1 AI crawler access. robots.txt blocks: GPTBot, PerplexityBot, anthropic-ai, Google-Extended. Allowed: 3.

✓ C2 PDP server-side render. 3/3 sampled PDPs render all three core elements (title, price, description) in raw HTML without JS.

✗ C3 Sitemap freshness. No valid sitemap with recent <lastmod> within 90 days.

✓ C4 Product schema. 3/3 PDPs have complete Product JSON-LD (name, image, brand, offers, identifier).

✗ C5 AggregateRating. 2/3 PDPs carry rating schema. Reviews likely displayed visually but not exposed as structured data on others.

✓ C6 FAQPage / HowTo schema. Found on 1 page(s) — homepage or help/how-to surface.

✗ C7 Organization schema. Missing name, url, sameAs on homepage.

✗ C8 PDP titles. 2/5 sampled titles go beyond brand + generic category.

✗ C9 PDP descriptions. 3/5 sampled descriptions cover 3+ buyer-context cues. Others are spec-heavy with limited context.

Fix priority

Ranked by leverage on agent discoverability, highest first.

Enable AggregateRating output in your review plugin
Usually a single setting in Yotpo / Judge.me / Okendo that exposes existing review data as JSON-LD. Reviews already live on the site — this just makes them machine-readable.
Add complete Organization JSON-LD with sameAs
10-line site-wide <head> addition — name, url, logo, and links to verified social profiles. Low risk, foundational for AI entity recognition.
Expand PDP descriptions with buyer-context cues
Who it's for, how it compares, when to use, what it isn't. The largest content project but touches every product, so compounds across the catalog. LLM-assisted generation from existing spec sheets is viable.

Implementing the top fixes would move this brand materially upward on this framework. Final score depends on implementation quality and broader content improvements.

The real story

Nécessaire has foundational gaps that limit agent visibility.

A 3/9 score means multiple layers need attention. Prioritize structured-data basics (C1, C3, C5) before content-level work.