Structured Data v26.7+

Maho emits schema.org structured data (JSON-LD) into your storefront pages: products, breadcrumbs, organization info, site search, and blog posts. This markup is what makes your store eligible for rich results in Google Search, powers Google Merchant listings (price, availability, shipping and returns shown directly in search), and is read by AI assistants and shopping surfaces when they present your products.

The module is enabled by default and works with no configuration. The settings on this page make the product markup complete: with them in place, Google can show your price, availability, shipping cost and return policy without a Merchant Center feed, and validate your feed against your pages when you have one.

As of v26.9 the product markup covers Google's full core product set: seller, item condition, price validity, shipping details, return policy, and variant markup for configurable products.

Where everything lives

The module settings sit in System > Configuration > Catalog > Catalog > Structured Data (schema.org):

The markup also reads settings you have probably already configured elsewhere. Check these, because they directly shape what is emitted:

Prices follow the page v26.9+

Emitted prices are in the customer's display currency and follow your tax display mode (Sales > Tax > Price Display Settings > Display Product Prices In Catalog). A store that displays prices excluding tax now emits excluding-tax prices; "Including Tax" and "Including and Excluding Tax" both emit including-tax prices. This is what Google requires: the structured-data price must match the price visible on the page.

Every offer also carries priceValidUntil, which Google recommends:

• A product with an active special price that has an end date emits that end date.
• A special price scheduled to start in the future caps the regular price's validity at the day before it begins.
• Otherwise a rolling fallback of today plus 30 days is emitted.

Product identity fields

• brand, GTIN and MPN come from the product attributes you map in the settings above. A product without a value in the mapped attribute simply omits the field.
• The GTIN is emitted to the length-specific property (gtin8, gtin12, gtin13, gtin14) based on its digit count, exactly as entered; other values use the generic gtin property. Maho does not validate checksums: Google Merchant Center is the validator and reports invalid GTINs there.
• itemCondition v26.9+ comes from the attribute you select as Condition Attribute. Recognized values are new, refurbished, used and damaged (plus common synonyms such as "pre-owned"). Products with no value, or with an unrecognized value, are emitted as new, so stores that only sell new goods need no attribute at all. Map an attribute only if you sell refurbished, used or damaged items.
• seller v26.9+ is your store's organization node, named from General > General > Store Information > Store Name.

Shipping details v26.9+

Each offer can carry an OfferShippingDetails node with the shipping rate, the destination countries, and optionally handling and transit times. Maho only emits the node when it can state an honest rate and a real destination; it never invents one. The node is omitted for virtual and downloadable products.

The rate is resolved in this order:

1. The Shipping Rate field, when set: a flat amount in base currency, converted to the display currency.
2. The Free Shipping carrier, when enabled and the product's price meets the Minimum Order Amount (or no minimum is set): rate 0.00. For configurable products this is checked per variant, so cheap and expensive variants can carry different rates.
3. The Flat Rate carrier, when enabled: its Price plus its Handling Fee.
4. Otherwise no node is emitted. Stores using only table rates or live carrier rates have no single honest per-product rate, so set the Shipping Rate override if you want the node.

The destination countries are resolved in this order:

1. The rate-source carrier's Ship to Specific Countries list, when "Ship to Applicable Countries" is set to Specific Countries.
2. Allowed Shipping Countries (General > General > Countries Options).
3. The shipping Origin Country (Sales > Shipping Settings).
4. If none resolves, the node is omitted, because Google requires a destination.

Handling and transit times are emitted only when you fill in both the minimum and the maximum for each range.

Return policy v26.9+

Each offer can carry a MerchantReturnPolicy node, controlled by Return Policy Type:

• Automatic (from Right of Withdrawal settings) - the default. When the Revocation Button feature is enabled (Sales > Revocation Button) and its Cooling-Off Period is above zero, the policy is a finite return window of that many days. When Revocation is disabled, nothing is emitted: a stock install never advertises a return policy it does not honor.
• Finite Return Window - a fixed window using the Return Window (days) field.
• Unlimited Return Window - returns accepted at any time.
• Returns Not Permitted - explicitly states that returns are not accepted.
• Do Not Emit - no return policy node at all.

Except for "Returns Not Permitted", the node also carries Return Fees (Customer Pays Return Shipping, or Free Return) and Return Method (by Mail, in Store, at Kiosk). The countries the policy applies to come from Return Countries, or when empty: your Allowed Shipping Countries, then your merchant country (Store Information), then the shipping origin country.

Variants of configurable products v26.9+

Configurable products emit ProductGroup + hasVariant, Google's supported variant markup:

• The parent becomes a ProductGroup with productGroupID (the parent SKU) and variesBy (the configurable attributes, for example color and size).
• Each enabled variant (up to 100) is a Product node with its attribute values, its own image (or the parent's when it has none), its identifiers, and inProductGroupWithID pointing back to the group.
• A variant that is visible in the catalog on its own also carries its own url.
• Each variant's offer advertises the price the buyer actually pays at checkout: the parent's price plus the configured option price adjustments. The variant's own price attribute is never advertised, because checkout never charges it.

Why is a field missing? (troubleshooting)

Recommended setup

1. Open System > Configuration > Catalog > Catalog > Structured Data (schema.org) and check that it is enabled.
2. Identity: verify the Brand, GTIN and MPN attribute mappings match the attributes your catalog actually uses. If you sell non-new goods, create a condition attribute (values: new, refurbished, used, damaged) and select it as Condition Attribute.
3. Seller: fill in General > General > Store Information (Store Name and Country).
4. Shipping: confirm Sales > Shipping Settings > Origin > Country and your Allowed Shipping Countries. If you use Flat Rate or Free Shipping, the rate derives automatically; otherwise set the Shipping Rate override. Optionally fill in the handling and transit day ranges you quote to customers.
5. Returns: if you use the Revocation Button, keep Automatic. Otherwise select the policy type, window, fees and method that match your written terms.
6. Tax: confirm Sales > Tax > Price Display Settings reflects how you really display prices, since emitted prices follow it.
7. Save, flush the Configuration cache, and validate a product page with the Google Rich Results Test. If you use Google Merchant Center, check its diagnostics a few days later.

For developers

Every JSON-LD graph passes through an event before rendering (maho_structureddata_product_data, _organization_data, _article_data, and so on), so a module can enrich or suppress the output without overriding templates.