Why do I have Product schema errors? on PrestaShop

Product schema helps search engines understand your products and can enable rich results (e.g.

• Missing required properties (name, image, etc ) Invalid price or availability format
• Use Rich Results Test or Search Console Enhancements for Product Check required
• Add all required properties Use correct format for price and availability Fix

Product schema helps search engines understand your products and can enable rich results (e.g. price, availability). Errors (missing required fields, invalid values) can prevent rich results or trigger warnings. Fixing Product schema ensures valid markup and eligibility for product features. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide.…

Missing required properties (name, image, etc.). Invalid price or availability format. Wrong or missing product IDs. Offer or aggregateRating errors. Duplicate or conflicting Product markup. Outdated or incorrect data.

Common examples

A real-world example: after a site update, a business saw visibility drop for "Product schema". They checked Search Console, found the blocking issue, fixed it, and regained impressions over the following crawl cycles.

How to diagnose

Use Rich Results Test or Search Console Enhancements for Product. Check required and recommended properties. Validate price, availability, and image. See which URLs have errors. Compare with Google's Product documentation.

Recommended fixes

Add all required properties. Use correct format for price and availability. Fix or remove invalid markup. Keep data in sync with live page. Re-validate and request indexing. Monitor Enhancements. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task. Practical context: prioritise one representative URL, confirm the exact blocker with Search Console and live testing, then apply the fix in templates or settings so the issue does not repeat site-wide. Track impressions, indexed page counts, and click recovery for at least two crawl cycles before closing the task.