Setup Product Schema Markup in Magento 2

Condition Values:

• NewCondition - Brand new products
• RefurbishedCondition - Factory refurbished
• UsedCondition - Second-hand items

Google requires priceValidUntil for Offer schema. Options:

Tip: Set a custom fallback (e.g., 30-90 days) to ensure all products have valid dates.

Best Practice: Enable both aggregate rating and individual reviews for maximum visibility.

Add custom mappings for additional product data. The following Schema.org properties are available:

The category, material, color, and numberOfItems properties are available since v2.10.0.

How numberOfItems works: This Schema.org property tells search engines how many individual items are included in a product. The extension reads the value from your selected Magento attribute, extracts the numeric portion, and outputs it as an integer on the Product schema. This means attribute values like "6 pieces" or "6 stuks" are automatically converted to "numberOfItems": 6. This is particularly useful for furniture sets (e.g., a dining set with table + 6 chairs = "numberOfItems": 7), multi-packs, and bundles where the quantity matters for buyer decisions.

Example mappings:

A configurable product (e.g., "T-Shirt") has multiple simple products (e.g., "T-Shirt - Red - Small", "T-Shirt - Blue - Large"). Each variant may have different:

• Price
• Stock status
• SKU/GTIN
• Images

Enable Split Configurable Products Snippets with Use Variants mode.

This generates:

{
  "@type": "ProductGroup",
  "name": "T-Shirt",
  "hasVariant": [
    {
      "@type": "Product",
      "name": "T-Shirt - Red - Small",
      "offers": { "price": "29.99" }
    },
    {
      "@type": "Product",
      "name": "T-Shirt - Blue - Large",
      "offers": { "price": "29.99" }
    }
  ]
}

Inherit from Parent:

• Name (if variants don't have unique names)
• Description (usually same for all variants)
• Brand (always same)
• Image (only if variants don't have unique images)

Don't Inherit:

• Price (variants may have different prices)
• SKU/GTIN (always unique per variant)

Set Split Bundle Products Snippets to Yes to generate schemas for each bundle item.

Set Split Grouped Products Snippets to Yes for individual item schemas.

Choose the right value type based on the nature of the attribute:

Tip: For boolean attributes, the extension recognizes common truthy values ("yes", "true", "1", "ja", "oui") and falsy values ("no", "false", "0", "nee", "non") across multiple languages and normalizes them to "Yes" or "No".

A garden lounge set with custom specifications:

"additionalProperty": [
  {
    "@type": "PropertyValue",
    "name": "Weather Resistant",
    "value": "Yes"
  },
  {
    "@type": "PropertyValue",
    "name": "UV Resistant",
    "value": "Yes"
  },
  {
    "@type": "PropertyValue",
    "name": "Seat Height",
    "value": {
      "@type": "QuantitativeValue",
      "value": 45,
      "unitCode": "CMT"
    },
    "unitCode": "CMT"
  },
  {
    "@type": "PropertyValue",
    "name": "Maximum Load Capacity",
    "value": {
      "@type": "QuantitativeValue",
      "value": 150,
      "unitCode": "KGM"
    },
    "unitCode": "KGM"
  }
]

Important: Make sure the attribute contains a numeric value only (e.g., "240" not "240 cm"). The extension extracts the number and pairs it with the configured unit code. If the attribute value contains text mixed with numbers, the extension will attempt to extract the numeric portion.

A table with width, height, and weight:

{
  "@type": "Product",
  "name": "Oak Dining Table",
  "width": {
    "@type": "QuantitativeValue",
    "value": 240,
    "unitCode": "CMT"
  },
  "height": {
    "@type": "QuantitativeValue",
    "value": 75,
    "unitCode": "CMT"
  },
  "depth": {
    "@type": "QuantitativeValue",
    "value": 100,
    "unitCode": "CMT"
  },
  "weight": {
    "@type": "QuantitativeValue",
    "value": 45.5,
    "unitCode": "KGM"
  }
}

Use UN/CEFACT Common Codes for standardized measurement units:

Maps Magento's native product relationship types to Schema.org isRelatedTo. This tells search engines which products are related, similar, or complementary.

Which relationship type to choose:

• Related Products — Items frequently bought together or similar alternatives. Best general-purpose option.
• Up-Sell Products — Higher-end alternatives. Good for showing premium options.
• Cross-Sell Products — Complementary items (e.g., accessories shown at checkout). Good for connecting different product categories.

Tip: Keep the limit reasonable (3-5 products). Each related product adds to the JSON-LD payload size. Only enabled (visible) products are included — disabled products are automatically filtered out.

Example output:

"isRelatedTo": [
  {
    "@type": "Product",
    "@id": "https://store.com/matching-chair.html#product",
    "name": "Matching Dining Chair",
    "sku": "CHAIR-OAK-001",
    "url": "https://store.com/matching-chair.html"
  },
  {
    "@type": "Product",
    "@id": "https://store.com/table-extension.html#product",
    "name": "Table Extension Leaf",
    "sku": "EXT-OAK-001",
    "url": "https://store.com/table-extension.html"
  }
]

Links a product to the main product it is an accessory or spare part for. This is a directional relationship — the current product belongs to a parent product, not the other way around.

Common use cases:

• Cushion sets for a lounge or sofa
• Replacement parts for machinery or appliances
• Phone cases linked to a specific phone model
• Ink cartridges linked to a printer

The attribute value can be either:

• A product SKU — the extension looks up the product and generates a full reference with name, SKU, and URL
• A product URL — used directly as the @id and url (useful for external or cross-store references)

Example: A cushion set that is an accessory for a lounge set.

"isAccessoryOrSparePartFor": {
  "@type": "Product",
  "@id": "https://store.com/premium-lounge-set.html#product",
  "name": "Premium Lounge Set",
  "sku": "LOUNGE-001",
  "url": "https://store.com/premium-lounge-set.html"
}

Tip: If a product referenced by SKU is not found or has been deleted, the property is silently omitted to avoid invalid structured data.

Enable to exclude the Offer schema when product price is €0.00. Useful for:

• "Price on request" products
• Free downloadable products
• Products with required options

If you use a custom attribute for pricing (not Magento's standard price):

1. Enable Use non-default attribute for price
2. Select your custom price attribute