Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to add product schema on Salesforce Commerce Cloud

On Salesforce Commerce Cloud there is no admin toggle, plugin, or settings panel for product schema. Adding it is developer work: your SFCC developer adds a JSON-LD block to the product detail template in your cartridge, and it deploys through the same sandbox-to-production pipeline as every other storefront change. Salesforce's own SEO documentation for B2C Commerce explicitly recommends adding JSON-LD structured data using schema.org types like Product, Offer, and AggregateRating, so this is a sanctioned part of the storefront, not a hack. The one constraint shaping everything is that nothing about this can be done by a merchandiser; it starts and ends with code.

## Why Salesforce Commerce Cloud is different

SFCC is the only platform in this series where the entire task belongs to an implementation team. There is no theme file editor in Business Manager, no app marketplace shortcut, and no code injection field. The storefront is built from ISML templates inside cartridges, and the product detail page is rendered server side from the product object, which is actually good news: the data you need (name, price, currency, availability, variant relationships) is already in the template context, so the JSON-LD block can be generated from the same product object that renders the page. Page Designer cannot do this job; it is for page layout, not template code.

## Steps

**1\. Check what already exists.** Open a live product page, view the page source, and search for `application/ld+json`. On a stock SFRA implementation you will typically find nothing product-specific, which tells your developer this is a new build rather than a fix. Note any blocks injected by third-party tags (a reviews provider via tag manager, for example) so the developer does not create a second Product block that conflicts with them.

**2\. Have your developer add the block to the product detail template.** The change belongs in the cartridge's product detail ISML template, guarded so it only renders on product pages. A minimal version inside the template pulls from the product object already in context:

```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "${pdict.Product.name}",
  "offers": {
    "@type": "Offer",
    "price": "${pdict.Product.price.sales.decimalValue}",
    "priceCurrency": "${pdict.Product.price.sales.currencyCode}",
    "availability": "https://schema.org/${pdict.Product.availabilityModel.inStock ? 'InStock' : 'OutOfStock'}"
  }
}
</script>
```

The exact property paths depend on your implementation's product model, so the developer should verify them against the objects in your cartridge rather than copying these verbatim. The principle that matters: every value in the markup must come from the same product data that renders the visible page, never from a separate feed.

**3\. Handle variants at the model level.** On SFCC, variants are typically separate products linked through the variation model, each with its own price and availability. The markup for each variant page must carry that variant's own facts, not the parent's. Confirm this on a variant URL before calling the work done.

**4\. Deploy through the normal pipeline.** Build it on a sandbox, review the rendered source there (not the browser DOM), replicate to staging, and validate with Google's Rich Results Test and the Schema Markup Validator on a URL such as https://\[yourdomain.com\]/your-product.html, replacing yourdomain.com with your actual domain. Include a variant page and an out-of-stock product.

**5\. If you have no SFCC developer, engage your implementation partner.** This is not a task for a merchandiser or an SEO generalist. If your storefront was built by an agency or a systems integrator, this is a small, well-defined work item for them.

### The fundamentals

-   •The complete JSON-LD reference this article builds on, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •Whether AI crawlers can reach your pages at all, see our [robots.txt guide](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)
-   •A readable catalog summary for AI engines, see our [llms.txt guide](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)

### A hypothetical example

Say you run an apparel brand on SFCC with a catalog of 2,000 SKUs and size variants. Your developer checks the page source and finds no product JSON-LD at all, plus a reviews provider's tag injecting a thin Product block with only a rating. The developer adds a full JSON-LD block to the product detail template in your cartridge, pulling name, variant price, currency, and per-variant availability from the product object, and configures the reviews provider's tag to stop emitting its conflicting block. One staging review, one validation pass on variant and out-of-stock pages, then it ships with the next release.

## What this guide does not cover

This covers getting valid product markup onto your SFCC product pages through template code. It does not cover keeping prices and availability accurate as inventory changes (monitoring work), getting AI crawlers to your pages past your WAF and bot management, or letting an agent complete the checkout, which is the transaction layer and a separate job.

## Frequently Asked Questions

Where is product schema generated in SFCC Storefront Reference Architecture?

Product schema is usually rendered in the productDetails.isml template or a dedicated jsonld.isml component.

How do I add merchant return policy data to SFCC schema?

Extend the product view model to include return window and policy URLs, outputting them inside the offers block.

Does SFCC support automated product schema testing?

You can add unit tests to your cartridge build pipeline that validate JSON-LD outputs against Schema.org specifications.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your product pages today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)