What it Checks
The validator combines three tools: the Schema Markup Validator (is the markup correct schema.org?), Google's Rich Results Test (does it qualify for a rich result?) and the schema.org type hierarchy (what can a type hold?).
- Extraction. Every
application/ld+jsonscript (single objects, arrays,@graph, several scripts per page), microdata (itemscope,itemtype,itemprop,itemref,itemid, nested items) and RDFa (vocab,prefix,typeof,property,resource). A JSON-LD script that doesn't parse is reported with its line and column. - schema.org. Types and properties are checked against the official vocabulary, inheritance included: a property is valid on a type when the type or one of its supertypes declares it. Values are compared with the expected types (dates, numbers, URLs, durations, enumeration values, nested items).
- Google rich results. Each item is matched to the Google features it can produce (Article, Breadcrumb, Product snippets, Merchant listings, Review snippets, Recipes, Events, Job postings, Local business, Organization and Logo, Videos, Datasets, Q&A, Discussion forum, Profile page, Vacation rentals, Image metadata, Speakable, Math solver and more), with the required and recommended properties Google documents for each one, checked against Google Search Central and its changelog in October 2026.
- Bot walls. A challenge or refusal served instead of the page (Cloudflare, Akamai, PerimeterX, DataDome, Imperva, AWS WAF, rate limits, an almost empty HTTP 202) is reported as Blocked., not as a page without structured data.
Run a Test
- Choose URL and paste the page address, Bulk and paste up to 50 URLs (one per line), or Code and paste a page's HTML, a snippet with microdata or RDFa, or bare JSON-LD (anything starting with
{or[is read as JSON-LD). - Press Validate. The result opens with the verdict: 3 items · 2 rich results eligible., 2 errors., No structured data found. or Blocked by Cloudflare.
- In Bulk, pages are validated three at a time as raw HTML; the table fills as they finish and exports to CSV or Excel. Click a URL for its full report.
- From the Schema Generator, Validate this opens the generated JSON-LD in the validator and runs it.
Options
- User agent. The crawler or browser the page is fetched as. Googlebot Smartphone is the default, the crawler Google indexes with. Some sites refuse crawler user agents from a data centre; the source row shows the HTTP status they answered.
- Raw HTML or Rendered (JavaScript). Raw reads the HTML as the server sends it. Rendered loads the page in Chromium, runs its scripts and reads the resulting DOM, like Google's rendering step: use it for markup injected by JavaScript (tag managers, single-page apps).
- Type explorer. Search any schema.org type or property: its place in the hierarchy, its more specific types, its own and inherited properties with their expected types, and the values of an enumeration. Inherited properties are folded by the supertype that declares them; open one group, or Show every property. Type names in the results open it. Link to a type with
/tools/schema-validator#type=Recipe.
Reading the Result
- Google rich results: one row per feature, each item marked eligible or not, with the missing required properties (the item can't get the rich result without them) and the missing recommended ones (it can, but with less detail). Paths like
offers.pricepoint inside nested items;a or bmeans either is enough. Deprecated features (FAQ since 7 May 2026, How-to, the sitelinks search box, fact checks and the features removed in 2025) are listed, never counted as eligible. - Bulk table: per URL the status, items, errors, warnings, the rich results it is eligible for, the ones it isn't with their missing required properties, and a note (bot wall, fetch error, no structured data, deprecated features). The types found are in the export.
- Detected items: each item as a tree of properties and values, nested items indented, references by
@idshown with the type they point to. Errors and warnings sit under the property or value they are about. - Extracted JSON: the items as JSON-LD, the original objects for JSON-LD and a conversion for microdata and RDFa.
Errors and warnings follow the Schema Markup Validator:
| Finding | Level |
|---|---|
JSON-LD that doesn't parse, no @context, unknown type, unknown property, property not valid for the type | Error |
| Value that doesn't match the expected type (a date, number, duration, URL, enumeration value or item type) | Warning |
| Superseded or pending type or property | Warning |
| Missing property Google requires for a feature | Not eligible for that rich result |
| Missing property Google recommends | Eligible, listed as missing |
Good to Know
- Text is accepted where schema.org expects an item (
"author": "Jane Doe"), as its data model allows. - Nodes with the same
@idin different scripts are merged into one item, and references by@idare followed when checking Google's properties, so@graphmarkup from Yoast or Rank Math is read as Google reads it. - RDFa support covers the schema.org subset (
vocab,prefix,typeof,property,resource,content; a typed element'shreforsrcnames it, as RDFa 1.1 says);rel/revchaining is not read. Open Graphmeta propertytags are not structured data items and are ignored. - Remote JSON-LD contexts other than schema.org are not fetched; their terms are shown but not checked.
- Google's rules are stored with links to each feature's page; value checks Google runs beyond presence (image sizes, price formats per country) are not reproduced. Write your markup with the Schema Generator.
API
POST /api/schema-validator
Send a url (with optional agent, an id from the user-agent list, and render) or the code to check. When the response was a bot wall, source.blocked says who served it and what came back. Bulk runs one request per URL.
Request
curl -X POST https://plumb.reacthive.dev/api/schema-validator \
-H "content-type: application/json" \
-d '{
"url": "https://www.bbcgoodfood.com/recipes/easy-pancakes",
"agent": "googlebot-smartphone",
"render": false
}'Request with Code
curl -X POST https://plumb.reacthive.dev/api/schema-validator \
-H "content-type: application/json" \
-d '{"code": "{\"@context\": \"https://schema.org\", \"@type\": \"Recipe\", \"name\": \"Pancakes\"}"}'Response (Trimmed)
{
"source": { "kind": "url", "finalUrl": "https://www.bbcgoodfood.com/recipes/easy-pancakes", "status": 200, "rendered": false, "agent": "Googlebot Smartphone" },
"formats": { "json-ld": 3, "microdata": 0, "rdfa": 0 },
"totals": { "items": 3, "errors": 1, "warnings": 0, "features": 4, "eligible": 4 },
"parseErrors": [],
"items": [
{
"index": 0,
"format": "json-ld",
"block": 1,
"line": 1,
"errors": 1,
"warnings": 0,
"node": {
"types": ["VideoObject"],
"props": [
{ "name": "name", "schema": true, "values": [{ "t": "text", "v": "How to make perfect pancakes" }], "issues": [] },
{
"name": "customPosterUrl",
"schema": true,
"values": [{ "t": "text", "v": "https://media.delight.video/…" }],
"issues": [{ "level": "error", "message": "The property customPosterUrl is not recognized by schema.org." }]
}
],
"issues": []
},
"json": { "@context": "https://schema.org", "@type": "VideoObject", "…": "…" }
}
],
"features": [
{
"id": "recipe",
"name": "Recipes",
"doc": "https://developers.google.com/search/docs/appearance/structured-data/recipe",
"eligible": 1,
"checks": [
{ "item": 1, "path": "", "label": "Recipe · Easy pancakes", "eligible": true, "missingRequired": [], "missingRecommended": ["video"] }
]
}
],
"vocabulary": { "version": "30.1", "built": "2026-10-22" }
}A Bot Wall (Trimmed)
{
"source": {
"kind": "url",
"finalUrl": "https://www.imdb.com/title/tt0111161/",
"status": 202,
"rendered": false,
"agent": "Googlebot Smartphone",
"blocked": { "vendor": "AWS WAF", "reason": "AWS WAF answered HTTP 202 with a challenge page instead of the page." }
},
"totals": { "items": 0, "errors": 0, "warnings": 0, "features": 0, "eligible": 0 },
…
}The type explorer is a GET endpoint: no parameter lists every type and property name, ?name= describes one.
GET /api/schema-validator/types?name=Recipe
Response (Trimmed)
{
"kind": "type",
"name": "Recipe",
"paths": [["Thing", "CreativeWork", "HowTo", "Recipe"]],
"subtypes": [],
"groups": [
{ "from": "Recipe", "properties": [{ "name": "cookTime", "expects": ["Duration"], "description": "The time it takes to actually cook the dish, in ISO 8601 duration format." }] },
{ "from": "HowTo", "properties": [{ "name": "step", "expects": ["CreativeWork", "HowToSection", "HowToStep", "Text"], "description": "…" }] }
],
"members": [],
"url": "https://schema.org/Recipe"
}