Agentic Commerce Readiness Audit

4/9

score

Early Stage

Some infrastructure in place; most agent-readiness criteria still need work.

Area breakdown

1. Crawlability

1/3

2. Structured data

2/4

3. Content quality

1/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

0/3 PDPs ship Review or AggregateRating schema.

✗ C6

FAQPage / HowTo schema

No FAQPage or HowTo schema on checked pages.

✓ C7

Organization schema

Organization JSON-LD present with sameAs array (9 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.

C1 AI crawler access Fail

Checked: Freck Beauty/robots.txt
Found: The following AI crawlers are blocked by explicit Disallow rules: GPTBot, ClaudeBot, Google-Extended, Amazonbot, 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: Freck Beauty/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: 0/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.

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 blocks: GPTBot, ClaudeBot, Google-Extended, Amazonbot. 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. 0/3 PDPs carry rating schema. Reviews likely displayed visually but not exposed as structured data on others.

✗ 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 (9 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.

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

Freck Beauty is around the category median — not yet agent-ready, but not structurally behind.

A 4/9 score sits in the middle of premium DTC beauty. Implementing 2-3 targeted fixes would lift this brand into the top tier.