Agentic Commerce Readiness Audit — Herbivore Botanicals

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

All 8 tested AI bots allowed in robots.txt.

✗ C2

PDP server-side render

Only 0/3 sampled PDPs render all core elements 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

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 schema missing: sameAs.

✗ C8

PDP titles

3/5 sampled titles include 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.

C2 PDP server-side render Fail

Checked: 3 sampled PDPs via raw HTML fetch
Found: 3 of 3 PDPs don't render all core fields in raw HTML. Missing: title. Examples: coco-rose-tremella-cleansing-oil-body-wash, nova-turmeric-pineapple-body-polish.
Fix: Audit the product-template rendering path to confirm title/price/description appear in raw HTML without JS. Agents cannot execute JavaScript on merchant sites.

C3 Sitemap freshness Fail

Checked: Herbivore Botanicals/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.

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.

C7 Organization schema Fail

Checked: Homepage for Organization JSON-LD
Found: Organization schema missing or incomplete. Missing: 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 3/5 titles include specific use-case, target audience, or differentiator cues. Examples: "GREEN MAGIC Centella + Ceramides Soothing Face Serum", "EVENING RESTORATIVE Bodycare Set".
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: 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. 0/3 sampled PDPs return complete product data without JS. Others missing one or more of title/price/description.

✗ 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. 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. Missing sameAs on homepage.

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

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

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

Herbivore Botanicals has foundational gaps that limit agent visibility.

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