Why this matters

When a shopper asks ChatGPT, Claude, Perplexity, or Google's AI Overviews "what's a good fragrance-free moisturizer for sensitive skin," the AI doesn't invent the answer — it pulls from product pages it has crawled and parsed.

The richer and more structured your PDP, the more likely your product is the one the AI recommends, names, and links to. The list below is what we recommend you expose on every page. Each item earns visibility for a specific kind of question.

What we can provide that LLMs hunger for

The flag taxonomy (anti-aging, comedogenic, allergen, etc.) is necessary but not sufficient. LLMs ingest and synthesize text — natural-language descriptions matter more than booleans alone. Our enrichment combines both:

1. Natural-language ingredient descriptions (50–150 words each) ✅
2. Canonical naming + aliases — so semantic queries ("vitamin B3" → niacinamide) ✅
3. Property/utility taxonomy — so concern queries ("anti-aging," "non-comedogenic") ✅
4. Free-from and concern flags — so exclusion queries ("paraben-free," "fragrance-free") ✅
5. Source/derivation — vegan, animal-derived, synthetic, mineral. Increasingly queried ✅
6. Use-case framing — "good for X / avoid if Y." Mirrors user query patterns directly — benefit list ✅

And one more thing AI systems love: freshness. Every enriched payload ships with an enriched_at timestamp — e.g. "enriched_at": "2026-05-07T10:23:00Z" — a machine-readable token that tells crawlers exactly when the data was last refreshed. AIs weight recent, dated content higher than undated content, and re-crawl pages whose timestamps move. It's a small field that does a lot of work.

1. Product identity — basic findability

You almost certainly already have all of this. Our integration plugs it in alongside the synthesised summaries and enriched ingredient data.

2. Discovery signals — getting surfaced for intent-based questions

This is where you stop being "a moisturizer" and start being "the fragrance-free moisturizer for sensitive skin that the AI recommends."

3. Ingredient intelligence — depth and trust

This is the layer competitors don't have — and the one that converts a casual mention into a confident recommendation.

4. Authority and trust signals

What you provide vs. what we provide

What this looks like in real-world queries

Three example shopper questions and what wins them:

"Best fragrance-free moisturizer for sensitive skin under $40"

• Wins on: formulation_signals includes "fragrance-free", skin_type_fit.sensitive = true, price exposed.
• Loses if: "fragrance-free" is buried inside marketing copy without being flagged as a structured attribute.

"What does niacinamide do?"

• Wins on: the short_description for niacinamide in driving_ingredients_breakdown, with your PDP as the source.
• Loses if: your ingredient list is just an INCI string dump with no explanations.

"Is this product safe during pregnancy?"

• Wins on: per-ingredient caution_flags.pregnancy_caution across the full driving_ingredients_breakdown.
• Loses if: shoppers have to interpret the INCI list themselves and the AI has to guess.

The bottom line

You don't have to write any of the technical or ingredient content yourself. We synthesise it from your EAN. Your job is small:

1. Confirm your commercial data (name, brand, EAN, image, price, URL, description) is correct and up to date.
2. Have engineering implement the integration template — typically half a day's work.

Within a few weeks of crawler indexing, your PDPs become the source of truth that AI search engines cite when shoppers ask questions about products in your category. That's the visibility — and the click — we're earning together.

Example: how to fetch the enriched data

Once your products are enrolled, the enriched payload is served at a per-product URL keyed by EAN. Your engineering team fetches it server-side and embeds it on the PDP (typically as a JSON-LD <script> block inside the page head).

URL pattern

Example request — fetching the enriched payload for EAN 0716170124353:

Example response

{
  "@context": [
    "https://schema.org",
    "https://schema.inferencebeauty.com/v1"
  ],
  "@type": "Product",
  "ean": "0716170124353",
  "category": "moisturizer",
  "consistency": "cream",
  "meta": {
    "enriched_at": "2026-05-07T10:23:00Z",
    "enriched_by": "InferenceBeauty.com"
  },
  "formulation_signals": [
    "fragrance-free",
    "vegan",
    "paraben-free",
    "sulfate-free"
  ],
  "key_benefits": [
    { "claim": "Hydration",       "driving_ingredients": ["Glycerin", "Sodium Hyaluronate", "Squalane"] },
    { "claim": "Barrier support", "driving_ingredients": ["Niacinamide", "Squalane", "Tocopherol"] },
    { "claim": "Soothing",        "driving_ingredients": ["Panthenol", "Niacinamide"] }
  ],
  "driving_ingredients_breakdown": {
    "inci_name": "NIACINAMIDE",
    "standard-capitalization": "Niacinamide",
    "common_name": "Vitamin B3",
    "chemical_name": "3-Pyridinecarboxamide",
    "inci_position": 3,
    "short_description": "A form of vitamin B3 widely used to support the skin barrier, even tone, and reduce visible pores.",
    "source": "synthetic",
    "group": "vitamin",
    "other utility": ["skin conditioning", "humectant", "barrier support"],
    "caution_flags": {
      "pregnancy_caution":  ["retinol"],
      "allergen_caution":   ["dimethicone", "silicone"],
      "sensitivity_status": ["dimethicone", "silicone"],
      "regulatory_notes":   ["EU Allergen"]
    },
    "skin_type_fit": {
      "dry":         true,
      "normal":      true,
      "combination": false,
      "oily":        false,
      "sensitive":   false,
      "mature":      true
    },
    "concern_targeting": {
      "hydration":         true,
      "spf":               true,
      "uneven_tone":       true,
      "fine_lines":        false,
      "redness":           true,
      "acne":              false,
      "hyperpigmentation": false
    },
    "inci_stats": {
      "count": 9,
      "allergen_count": 2,
      "fragrance_count": 0
    }
  }
}

Cache the payload as long as you like — when meta.enriched_at changes, refetch. We notify your integration endpoint on updates so you never have to poll.