SchemaGen’s validator checks your JSON-LD against two separate standards at once: the Schema.org specification itself, and Google’s Rich Result requirements. These are not the same thing—a schema can be perfectly valid Schema.org and still fail to qualify for a Rich Result. The validator reports on both so you know exactly what to fix and why. Validation is available on all plans, including Free.Documentation Index
Fetch the complete documentation index at: https://docs.schemagen.io/llms.txt
Use this file to discover all available pages before exploring further.
What the validator checks
Schema.org compliance confirms that your JSON-LD is structurally correct. This includes whether required properties are present, whether property values match their expected types (a URL field should be a URL, a date field should follow ISO 8601, and so on), and whether the overall structure matches the Schema.org definition for that type. Google Rich Result eligibility checks whether your schema meets the additional requirements that Google imposes on specific types for enhanced search appearances—featured snippets, star ratings, price information in search results, and similar rich features. Google’s requirements are a subset of Schema.org but often stricter about which specific fields must be present.Two ways to validate
- From the dashboard editor
- Via the API
Open any saved schema from your Schemas list and click Validate in the schema detail toolbar. The validator runs immediately and displays the full result below the schema preview. This is the fastest way to validate schemas you’re working on in SchemaGen.You can also click Validate directly from the Schema Builder before saving, to check your work as you fill in the form.
Understanding the validation result
A validation result contains several distinct sections:| Field | What it tells you |
|---|---|
isValid | Whether the schema passes all required checks for its detected type |
detectedTypes | The @type values found in the schema (may be multiple if nested) |
issues | Hard errors that make the schema invalid—these must be fixed |
warnings | Non-blocking issues that may reduce quality or eligibility |
schemaOrgIssues | Problems specific to Schema.org spec compliance |
googleRichResultWarnings | Fields missing or incorrect for Google Rich Result eligibility |
seoRecommendations | Suggestions for improving schema quality beyond the minimum requirements |
correctedSchema | A suggested fixed version of your schema, generated automatically |
Schema.org errors vs. Google Rich Result warnings
These two categories are intentionally separate and mean different things for your SEO strategy. Schema.org issues are structural errors. If yourProduct schema is missing @context, has a price value that is a string where a number is expected, or references an undefined property type, these will appear as schemaOrgIssues. A schema with these errors may not be read correctly by any search engine.
Google Rich Result warnings appear in googleRichResultWarnings and represent fields that are optional in Schema.org but required or expected by Google to qualify for enhanced search appearances. For example, a Product schema without aggregateRating or offers is valid Schema.org, but will not show star ratings or prices in Google Search. Fix these if Rich Results matter for the page.
The corrected schema
When the validator detects fixable problems, it generates acorrectedSchema: a complete, ready-to-use JSON-LD object with the issues resolved as best as the system can determine. You can copy this corrected version directly from the validation result panel.
The corrected schema handles common fixes automatically: adding missing @context, coercing values to their correct types, adding placeholder values for required missing fields (clearly marked so you know to fill them in), and restructuring nested objects that are incorrectly formatted.
The corrected schema is a suggestion, not a guarantee. Review it before using it, especially for fields where a placeholder was added. Placeholder values like
"MISSING_VALUE" need to be replaced with your actual content before the schema is meaningful.Common validation errors and how to fix them
Missing required field
Missing required field
What it looks like:
Issue: Required property 'name' is missing.What it means: The schema type requires this field to be present. Without it, the schema fails Schema.org validation.How to fix it: Open the schema in the editor, locate the missing field (it will be marked with a red asterisk), and fill it in. If you used AI extraction and the page didn’t have this information visible, add it manually.Wrong property type
Wrong property type
What it looks like:
Issue: Property 'price' expected type Number, got String.What it means: You’ve entered a value in a format that doesn’t match what Schema.org expects. Prices should be numbers (29.99), not strings ("$29.99"). Dates should follow ISO 8601 (2026-09-01), not free-form text (September 1, 2026).How to fix it: Edit the field and correct the format. The field’s help text in the Schema Builder shows the expected format.Invalid URL format
Invalid URL format
What it looks like:
Issue: Property 'url' must be a valid URL.What it means: A URL field contains something that isn’t a valid URL—missing protocol (https://), a relative path, or a plain text string.How to fix it: Enter the full absolute URL including the protocol. For example, use https://example.com/page not /page or example.com/page.Google Rich Result: missing recommended fields
Google Rich Result: missing recommended fields
What it looks like:
Google Rich Result Warning: 'aggregateRating' is recommended for Product rich results.What it means: Your schema is valid Schema.org but is missing fields that Google looks for when deciding whether to show a Rich Result for this page type. This is a warning, not an error—your schema will still be indexed, but the page may not get enhanced search appearance.How to fix it: Add the recommended fields to your schema. For Product, this typically means adding offers with a price and aggregateRating if you have review data. For Article, add author and datePublished.Missing @context or @type
Missing @context or @type
What it looks like:
Issue: JSON-LD must include @context set to 'https://schema.org'.What it means: The schema is missing the root-level @context or @type declarations that tell parsers what vocabulary and type you’re using. This is a fundamental structural error.How to fix it: Use the corrected schema from the validation result, which adds these automatically. If you’re editing JSON-LD by hand, every schema must begin with "@context": "https://schema.org" and "@type": "YourType".