Agentic Commerce Readiness Audit

6/9

score

Strong Crawlability, Weak Structured Data

Score is concentrated in Crawlability; Structured Data is the constraining area.

Area breakdown

1. Crawlability

3/3

2. Structured data

2/4

3. Content quality

1/2

The 9 criteria

✓ C1

AI crawler access

All 8 tested AI bots allowed in robots.txt.

✓ C2

PDP server-side render

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

✓ C3

Sitemap freshness

Sitemap has 55 URLs with fresh <lastmod> timestamps.

✗ C4

Product schema

2/3 PDPs have complete Product JSON-LD.

✓ C5

AggregateRating

3/3 PDPs ship AggregateRating with real review counts.

✗ C6

FAQPage / HowTo schema

No FAQPage or HowTo schema on checked pages.

✓ C7

Organization schema

Organization JSON-LD present with sameAs array (5 profiles).

✓ C8

PDP titles

4/5 sampled titles include use-case or differentiator cues.

✗ C9

Description depth

2/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.

C4 Product schema Fail

Checked: 3 sampled PDPs — raw HTML via source-level fetch
Found: Only 2/3 PDPs ship complete Product JSON-LD with all commonly-recommended fields (name, image, brand, offers.price, offers.availability, and an identifier).
Fix: Ensure every PDP template emits Product JSON-LD with the Google rich-results minimum fields. See Google's product structured-data docs.

C6 FAQPage / HowTo schema Fail

Checked: Homepage and discoverable FAQ / how-to-use / about pages
Found: No FAQPage or HowTo JSON-LD detected. If your store publishes how-to / routine content, it's currently invisible as structured data.
Fix: Wrap existing FAQ content in FAQPage JSON-LD and any routine / tutorial content in HowTo JSON-LD. These map directly to the "how do I use X" queries AI shopping agents handle. schema.org/FAQPage / HowTo.

C9 Description depth Fail

Checked: 5 sampled PDPs — full description text
Found: 2/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 allows all 8 tested bots (GPTBot / PerplexityBot / ClaudeBot / anthropic-ai / Google-Extended / Amazonbot / CCBot / FacebookBot).

✓ 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. Valid sitemap with 55 recently-updated URLs (most recent: 2026-02-11T11:11:15-05:00).

✗ C4 Product schema. 2/3 PDPs ship complete Product JSON-LD. Others missing required fields or the block entirely.

✓ C5 AggregateRating. 3/3 PDPs carry rating schema with real ratingValue and reviewCount.

✗ C6 FAQPage / HowTo schema. Not present on homepage or auxiliary help pages.

✓ C7 Organization schema. Homepage ships Organization JSON-LD with name, url, and sameAs (5 profiles).

✓ C8 PDP titles. 4/5 sampled titles include use-case specifics (fabric, fit, target audience).

✗ C9 PDP descriptions. 2/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.

Ship complete Product JSON-LD on every PDP
Highest-leverage structured-data change. Ensures AI agents can extract name, price, availability, and identifiers cleanly. Lightweight if product data already exists server-side.
Wrap FAQ / how-to content in FAQPage or HowTo JSON-LD
Maps directly to "how do I use X" queries AI shopping agents handle. Lightweight if the FAQ template has Q&A as structured data; heavier if mixed with presentational HTML.
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

Ceremonia is in the top tier of premium DTC beauty for agentic commerce readiness.

A 6/9 score places this brand above the median (4/9) across the 40 brands we audited. The remaining gaps are specific and fixable.