How to Fix Every Schema Debugger Finding
The Schema Debugger doesn't just validate — it tells you why Google rejected your schema for rich-result eligibility. Errors are blocking. Warnings are eligibility-degrading but non-fatal. Recommended-field gaps reduce the richness of the result Google shows. This index covers fixes for every category.
By finding type
Each severity has different fix urgency. Pick yours:
🔴 Fix blocking validation errors PLANNED
Errors disqualify the page from rich results entirely. Missing required fields, wrong types, malformed JSON. Fix order: errors first (eligibility), then warnings (richness).
⚠️ Fix non-blocking warnings PLANNED
Warnings allow eligibility but degrade result richness. Missing image, missing description, missing aggregateRating. Each warning fixed adds a piece to the rich-result display.
💡 Add recommended fields PLANNED
Beyond required and warned, schema.org has recommended fields for each type. These don't trigger errors but enrich Knowledge Graph and AI-engine understanding.
⭐ Fix aggregateRating issues PLANNED
Aggregated ratings need at least 1 review, valid rating value in expected range, and the reviewed item visible on the page. Common mistakes: hard-coded fake ratings (Google detects), wrong scale, missing item.
📦 Fix Product schema eligibility PLANNED
Product needs offers with price and priceCurrency, plus availability. review or aggregateRating for stars. The full Product checklist Google enforces.
🍳 Fix Recipe schema eligibility PLANNED
Recipe needs image, name, recipeIngredient, recipeInstructions, recipeYield. Plus aggregateRating for ratings to show. Video recipe extensions for the carousel.
❓ Fix FAQPage schema eligibility PLANNED
FAQPage needs mainEntity containing Question entities, each with acceptedAnswer. Google's 2023 reduction of FAQ rich results means fewer pages now show; the eligibility criteria tightened.
📖 Fix HowTo schema eligibility PLANNED
HowTo needs step array with named steps. Each step needs name + text. Image per step for the visual carousel. The full HowTo checklist plus the desktop-vs-mobile result differences.
By platform
Debugging approaches by platform:
📰 Debug schema in WordPress PLANNED
The Yoast / Rank Math debug screens, the schema-output filters for advanced cases, and the developer console patterns.
🛒 Debug schema in Shopify PLANNED
Theme-generated schema with manual overrides, the Shopify Schema App debugging, and the apps that conflict.
🌐 Debug schema in headless / custom builds PLANNED
Server-rendered JSON-LD vs client-injected schema, the timing implications for Googlebot, and CI validation hooks.
What our Schema Debugger checks
The debugger fetches your page, extracts every JSON-LD block, runs it against Google's Rich Results criteria, lists errors and warnings with their specific cause, and shows you what the rich result would look like once fixed. For the full reference, see the Schema Debugger Guide.
🔬 Debug your schema first
Run the debugger. Most schemas have 1-2 fixable issues blocking rich results — quick wins.
Open Schema Debugger →