How does structured data / schema markup help my store?

PrestaShop schema, also called structured data, is a small extra layer of code that tells search engines what each piece of content on your page represents: a price, a stock state, a product, a rating, a breadcrumb trail or an FAQ entry. Search engines can use that data for eligible rich result features such as product price and stock snippets, review stars where supported, breadcrumb links, or FAQ-style presentation where the search engine still supports it.

Rich results do not push your page higher in the ranking on their own, but they can make the listing more useful and easier to trust. For a store, the schema types that usually matter are Product, Offer, AggregateRating/Review, BreadcrumbList, Organization, WebSite, CollectionPage, Article and, where appropriate, FAQPage.

Our Automatic SEO Schema Rich Snippets module attempts to add Product, Offer, rating/review, breadcrumb, Organization, WebSite, category and CMS-page markup without template editing. The same schema functionality is also part of the Smart SEO Revolution Suite if you also want sitemaps, canonicals and meta-tag automation in one place.

Important current-code caveat: the module outputs JSON-LD from hookDisplayHeader, but clean_existing_jsonld is enabled by default and the final-output cleanup preserves only JSON-LD scripts containing the <!-- mprschema --> marker. The header hook currently emits unmarked JSON-LD, so with JSON-LD cleanup active the final HTML can remove the module's own schema. Until the renderer marks its scripts or the cleanup logic is disabled/fixed, verify the final page source before treating the JSON-LD as reliably present.

On product pages, the Product schema can include the product name, URL, description, SKU, GTIN/UPC/ISBN/MPN identifiers, manufacturer/supplier/feature-based brand data, images, item condition, offer data, weight, category and review data when the shop has that data. The brand generator uses the configured catalogue source, such as manufacturer, supplier or a feature named like Brand, with a manufacturer fallback; the declared override-brand field is not used by the current generator. Offer data can include price, currency, availability, seller, shipping details and return policy. For products with combinations, the implementation can build aggregate offer data instead of pretending every variant has one identical offer.

Category pages are handled differently: they are rendered as CollectionPage data with a category name, URL, description, image, number of items and an ItemList sample of products. CMS pages are rendered as Article schema with headline, URL, description, article body, word count, dates, author, publisher, logo, language and main entity URL.

The practical merchant rule is to fill the underlying data, not just switch schema on. If a product has no identifier, weak images, no stock state, no reviews or an empty description, the schema can only describe that weak data. Structured data works best when your catalogue data is already clean, and in the current module you should also check that cleanup settings are not removing the JSON-LD you expect to publish.