Web & SEO
Structured Data (JSON-LD) Validator
Paste JSON-LD (or a page's HTML) to check it's valid JSON, uses schema.org correctly and includes the key properties for common rich result types.
How to use
- 1Paste the JSON-LD script or the whole page source.
- 2Fix syntax errors and missing required properties, then confirm with Google's Rich Results Test.
How it's calculated
Every <script type="application/ld+json"> block (or the pasted JSON) is parsed; each item's @type is checked against a list of commonly required properties for Google rich results.
Frequently asked questions
Is this the same as Google's Rich Results Test?
No — it catches syntax errors and common missing fields quickly and privately. Use Google's test for the final word on eligibility.
Does @context matter?
Yes — it should be https://schema.org (or http). Without it, parsers don't know which vocabulary you mean.
Can one page have several JSON-LD blocks?
Yes — they're all read. You can also combine items with @graph.
Why it checks nested items, not just the top-level object
Schema.org structures are often nested — a Product contains an Offer, an Article might contain a Person as its author — and this validator's check() function recurses into every nested object that has its own @type, not just the outermost one, which is why checking a Product with a nested Offer reports two items checked, not one. A problem buried two levels deep (a missing price inside an Offer inside a Product) gets caught the same way a top-level problem would.
Worked example: Structured Data (JSON-LD) Validator
Pasting {"@context":"https://schema.org","@type":"Product","name":"Mug","offers":{"@type":"Offer","price":"12"}} checks two items — the Product itself (which has its required 'name' property, so it passes) and the nested Offer, which is missing its required priceCurrency property, producing exactly 1 problem. Fix that by adding "priceCurrency":"USD" to the Offer object, and the same structure would report 'Valid' with 2 items checked — the recursion finds and validates the nested object either way, it's only the completeness of its properties that changes the result.
Why @context gets its own explicit check
A JSON-LD block with a perfectly structured @type and all its required properties still isn't useful to a search engine if @context doesn't point to https://schema.org, because without it, parsers have no way to know which vocabulary your @type names refer to — 'Product' means nothing in isolation without the schema.org context declaring what vocabulary defines that term. That's a separate, independent check from the required-property checks for exactly that reason: a missing or wrong context breaks the whole block even if every individual property is present.
Why this isn't a substitute for Google's own Rich Results Test
This validates against a fixed list of commonly required properties for common types — it catches JSON syntax errors and obvious missing fields quickly and entirely in your browser, without sending anything to Google. But Google's actual eligibility rules for rich results can be more specific or stricter than this general checklist, and they change over time as Google adjusts which types and properties qualify — which is why the tool's own FAQ recommends treating a 'Valid' result here as a fast first pass, with Google's Rich Results Test as the actual final word before relying on a rich result appearing.
Script blocks are read and the rest of the page is not
An empty box asks you to paste JSON-LD or HTML containing it. If the paste includes one or more structured-data script blocks, only those blocks are parsed and the surrounding page is ignored. A block that is not valid JSON is counted as a problem and the message names the block number. A type this checker has no rule list for is marked as passing with a note that there are no required-field rules for that type. An empty string counts as missing, the same as leaving the property out. One problem stays singular in the result line; two or more become a plural. A graph or a list of items is walked item by item.
Related tools
- Schema Markup (JSON-LD) Generator
Generate JSON-LD structured data for FAQ pages, articles, products, local businesses and organizations — ready to paste into your page's <head>.
- Email Spam Checker (Spam Score)
Check an email for spam triggers before you send it — trigger phrases, ALL CAPS, excessive punctuation, link ratio, URL shorteners, deceptive subjects and missing unsubscribe links. Get a spam score and fixes.
- Website Accessibility Checker (WCAG 2.2 Quick Scan)
Scan a web page for common WCAG 2.2 accessibility failures — missing alt text, unlabelled form fields and buttons, empty links, heading order, page language and title, disabled zoom and more — with fixes for each.
- Email List Cleaner & Validator
Clean an email list in seconds — remove duplicates and invalid addresses, fix typos like gmial.com, and optionally drop role (info@, noreply@) and disposable addresses. Paste any list; nothing is uploaded.
- Fake Test Data Generator (JSON / CSV)
Generate realistic fake people — names, emails, phones, addresses, companies — as JSON or CSV for testing and demos.
- Test IBAN Generator
Generate random, checksum-valid IBANs for software testing — for Germany, France, the Netherlands, Spain, Italy, the UK and more.