Schema Validator (JSON-LD)
Paste JSON-LD code, one or more script blocks or the full source of a page. The tool finds JSON syntax errors with their line and column, checks @context, @type and @graph, and compares every item with the required and recommended properties Google documents for rich results. It also checks values: full URLs, ISO 8601 dates, numeric prices with a currency and ratings within their scale. To create markup use the schema generator; for the basics read what is schema markup.
The code is validated in your browser and is not sent anywhere.
1 block, 1 item, 2 errors, 2 warnings.
Block 1 · line 2
- Required field missing in offers: priceCurrency.line 8
- price is not a number (24,90 USD). Write it without currency or symbols, with a dot for decimals ("249.90"), and give the currency in priceCurrency.line 10
- Recommended fields missing: description, sku, review. Not required, but adding them makes the result richer.line 2
- image is a relative address (/img/mug.jpg). Use a full address (https://...).line 6
What this tool does not replace
This tool does not replace Google's Rich Results Test. It checks the required and recommended properties Google documents as of November 2026, but it cannot see how Googlebot renders your page, schema added by JavaScript, whether the markup matches the visible content or structured data policy issues. Before and after publishing, also check with Google's Rich Results Test, and with the Schema Markup Validator for general schema.org conformance.
Related tools and articles
To see the signals that keep a page out of the index, use the indexability checker.
How to use it
- Paste the code into the box: raw JSON-LD, <script type="application/ld+json"> blocks or the whole page source (view-source in your browser). The result updates as you type.
- If there is a JSON syntax error, fix it first; the tool shows the line, the column and the likely cause.
- Each item card shows which Google feature it matches and its status. Fix red items first (required fields and invalid values), then review amber warnings.
- Generate missing markup with the schema generator. After publishing, test the live page with Google's Rich Results Test and follow the enhancement reports in Search Console.
Frequently Asked Questions
Does this replace Google's Rich Results Test?
No. This tool checks the markup you paste against the properties Google documents, without sending it anywhere. The Rich Results Test renders your live page the way Googlebot does, including schema added by JavaScript, and shows exactly which rich results Google detects. Use this tool while writing and editing, and the Rich Results Test before and after publishing.
Should I remove FAQ markup now that FAQ rich results are gone?
There is no need to rush. Since 7 May 2026 Google no longer shows FAQ rich results, but FAQPage markup is not an error and Google can still use it to understand the page. If your CMS adds it automatically you can leave it; just do not expect expandable questions in search results. More context in what is schema markup.
What is the difference between required and recommended properties?
Without the required properties the item is not eligible for the rich result at all. Recommended properties are optional, but they add information (price, rating, image, date) and can make the result more useful. Red findings are required fields or invalid values; amber ones are recommendations or values worth checking.
JSON-LD, microdata or RDFa?
Google supports all three but recommends JSON-LD, because it sits in a separate block and is easier to maintain. This tool only checks JSON-LD; if you paste a page that uses microdata, it tells you so. The schema and structured data guide explains the setup step by step.
Is the code I paste sent anywhere?
No. Validation runs entirely in your browser; nothing is sent to a server or stored. You can safely paste markup from staging or unpublished pages.
There are no errors, so why is there no rich result?
Valid markup makes a page eligible, but Google does not guarantee a rich result. Content quality, whether the markup matches what is visible on the page, structured data policies and the search query all play a role. Check the enhancement reports and the URL Inspection tool in Search Console, and see the schema and structured data guide.


