Automatic SEO Schema Rich Snippets: setup and help

Upload the ZIP in Modules > Module Manager > Upload a module. Install it, then click Configure. Open Improve > Schema Rich Snippets > Settings > Configuration.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.

HTML cleanup requires your core to call actionOutputHTMLBefore. Check the public output on your actual core and theme.

Installation creates the mprschema_override and mprschema_log tables with your database prefix. It stores module settings under mprschema in the shared MPR configuration table.

In Schema Types, the following switches default to Yes.

Disable a schema type when you do not want that type published. Review cleanup before saving if another module publishes markup you need to retain. Cleanup operates on rendered HTML and does not edit theme files.

The module does not produce FAQ schema and has no FAQ configuration option.

In Organization, review these fields. Text fields start empty.

In Social Profiles, fill Facebook URL, Twitter / X URL, Instagram URL, YouTube URL, LinkedIn URL, Pinterest URL, and TikTok URL as needed. They start empty and supply the organization's sameAs values. Leave unused profiles empty.

Product output reads current catalog data. Available fields include name, URL, description, reference as SKU, EAN-13 as gtin13, UPC as gtin12, ISBN, supplier reference as MPN, brand, images, condition, weight, category, and product features. Offers include price, currency, availability, URL, and seller where available. Products with hidden prices or unavailable ordering do not publish their stored price as an offer.

For products with usable, distinct combination URLs, output can become a ProductGroup containing variant Product records and their offers. If combinations cannot be preselected at distinct URLs, the module falls back to the product page's single offer. Do not expect the former AggregateOffer structure.

Review data comes from approved records in {prefix}product_comment. The module can add an aggregate rating and up to 10 recent reviews. When no approved aggregate rating is available, it can read rating values from the latest active override for that product, without filtering by shop. It does not create ratings without source data.

The module maps available product identifiers directly from the product fields. There is no setting to remap them.

Rates use one unit of the product and the lowest applicable rate from selected carriers for each destination. The calculator checks carrier ranges, zones, taxes, handling, product surcharges, and supported free-shipping thresholds.

Shipping details may be omitted if the rate depends on an extension, address-specific taxes, carrier modules, warehouse rules, or other unsupported checkout conditions. The module does not substitute a guessed price. Test rates against your checkout before relying on the output.

Return applicability is built from the shop's delivery countries. Return policy country uses the organization or shop country. It is not derived solely from Shipping Countries (ISO).

Review these values against the policy your shop actually publishes. Saving schema settings does not configure checkout shipping or your returns process. Invalid choices, country codes, day ranges, or required fixed-fee values can prevent the form from saving. Correct the reported fields and save again.

Open Schema Rich Snippets > Schema Preview. Generate a homepage preview and a preview for a real product, category, or CMS page.

Preview renders applicable schema groups independently of their top-level enable switches. Always check the public URL too. In page source, find application/ld+json blocks marked data-mprschema="1". Confirm prices, currency, availability, identifiers, business details, shipping, and returns against visible page content.

Use the preview screen's validator links to inspect the public URL.

If your custom theme does not call the header hook, add the native call in its head template:

{hook h='displayHeader'}

The module outputs JSON-LD through that hook. It does not add shopper-facing CSS or JavaScript.

There is no ordinary rating editor in this setup flow. The code can read review_count and review_value from {prefix}mprschema_override for an active product record. It does not filter by id_shop, so an override can affect other shops sharing that product ID. Approved comment aggregates take precedence.

If you maintain such records directly, use real reviews, the actual table prefix, product ID and shop ID. The original insertion shape is:

INSERT INTO ps_mprschema_override
(entity_type, entity_id, id_shop, review_count, review_value, active, date_add, date_upd)
VALUES
('product', 123, 1, 42, 4.80, 1, NOW(), NOW());

Replace every example value before use. This stores an aggregate fallback, not individual Review records.

If markup is missing, check the schema type switch, header hook, entity ID, and page cache. The dashboard reports catalog counts and configuration coverage. Use Settings > Integrity for required infrastructure checks.

If required third-party markup disappears, disable Remove Existing JSON-LD, clear any page cache, and inspect the output again. If duplicate microdata remains, confirm your core calls the output hook and the page has a normal head section.

If shipping details are missing, select carriers and review unsupported pricing conditions. If a return fee is missing, check its amount, selected currency, and each shop's default currency. Compare a simple product and a combination product separately.

Disable the module in Module Manager to stop output. Uninstall removes its menu, module settings, admin preferences, override table, and log table. Export any custom override records you need before uninstalling.