Agentic Commerce Readiness Audit — Beauty Edition 1

Half Magic Beauty

https://halfmagicbeauty.com
Audit date: 2026-04-18
Sampling: 3 PDPs / 5 titles / sitemap + robots.txt + homepage
Evidence: source-level httpx fetch
5/9
score
Strong Foundations, Missing Structured Layer
Crawlability and basic infrastructure work; structured data emission is the primary gap for agent retrieval.
Area breakdown
1. Crawlability
3/3
2. Structured data
1/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 2 URLs with fresh <lastmod> timestamps.
✗ C4
Product schema
0/3 PDPs have complete Product JSON-LD.
✗ 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 (3 profiles).
✗ C8
PDP titles
2/5 sampled titles include differentiator cues.
✓ C9
Description depth
4/5 descriptions answer comparison / 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 0/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.
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.
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: "EYESHADOW SINGLES | PRETTY ROBOT", "EYELECTRIC EXTREME LENGTHENING MASCARA".
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.
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 2 recently-updated URLs (most recent: 2026-04-16T14:48:12-07:00).
✗ C4 Product schema. 0/3 PDPs ship complete Product JSON-LD. Others missing required fields or the block entirely.
✗ 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 (3 profiles).
✗ C8 PDP titles. 2/5 sampled titles go beyond brand + generic category.
✓ C9 PDP descriptions. 4/5 sampled descriptions address 3+ buyer-context cues (fit, comparison, ingredient rationale, usage, counter-indications).

Fix priority

Ranked by leverage on agent discoverability, highest first.

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

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

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

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

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

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