Schema Markup Validator
This schema markup validator reads the structured data on any page, or in code you paste, and checks it against the properties Google's documentation requires and recommends for each rich result.
Try it on or paste any public URL.
Structured data found
JSON-LD blocks Microdata items RDFa items
, , .
Checked:
A parser stops at the first error, so fix this one and check again: there may be more further down. Until it parses, search engines ignore the whole block.
Rich result readout
Google's documented requirements, checked . Meeting them makes a page eligible for a rich result, never certain of one: Google also applies its content guidelines and its own judgement.
Findings
-
·
What a parser reads, nested as written. An arrow marks a reference to another entity by @id.
The tree stops at 2,000 rows; the findings above cover everything.
That was one page. Check the structured data on every page.
Crawl Cove parses the JSON-LD and microdata on every page it crawls and runs the schema-validity and structured-data-missing checks, so a template that lost its offers or broke its JSON shows up as a list of pages, not one URL at a time.
Download Crawl Cove freeNeed to write the markup first? The schema markup generator builds JSON-LD for fourteen types, and sends it here to check.
Note
It reads all three formats (JSON-LD, microdata and RDFa), points to the exact line and column of a JSON syntax error, merges nodes that share an @id the way Google does, and flags references to an @id that is not on the page, dates that are not ISO 8601, relative URLs, prices with a currency symbol in them and misspelt types. Every entity comes back as a tree you can read, copy as JSON-LD or download as a CSV. No sign-up and nothing to install.
Use this tool often? Bookmark this page, so it is one click away next time.
Email me this result
Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.
Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.
How to validate schema markup
-
Enter a URL or paste code
Check a live page by its address, or switch to Paste code and drop in a JSON-LD object, a few script tags or a whole HTML page, for markup that is not live yet.
-
Read the rich result readout
Each entity that feeds a Google feature is listed with the feature it feeds, whether it has the properties Google requires, and a link to Google's documentation for that type.
-
Fix the errors first
Errors stop a rich result or stop the markup being read at all: a syntax error, a missing required property, a misspelt type, a date or URL in the wrong form. Warnings and notes come after.
-
Check the tree and export it
Open the entity tree to see exactly what a parser reads, copy the result as JSON-LD (microdata and RDFa are converted for you), or download every finding as a CSV for a ticket or a client.
What this schema markup validator checks
Syntax first. Every application/ld+json block is parsed, and when one fails the validator names the line and column and the likely cause: a trailing comma, a missing comma, single or curly quotes, a raw line break inside a string, a comment, or two objects with no array around them. A block that does not parse is ignored by search engines, so this is the one error that hides every other. Then the vocabulary: a missing or wrong @context, a type in the wrong case (product for Product), and duplicate keys that silently drop a value. Then Google's rules: the required and recommended properties for Article, Product and Offer, Review and AggregateRating, BreadcrumbList, Organization, LocalBusiness, Event, Recipe, VideoObject, SoftwareApplication, JobPosting, Movie and WebSite, with subtypes such as BlogPosting and Restaurant judged by their parent's rules. Finally the values: ISO 8601 dates and durations, absolute URLs, plain-number prices, three-letter currency codes, availability values and ratings that fit their scale.
Schema Markup Generator · How to validate structured data site-wide
This tool, Google's Rich Results Test and validator.schema.org
The Schema Markup Validator at validator.schema.org checks markup against the whole schema.org vocabulary and knows nothing about Google's rules, so a Product with no offers, review or rating passes there and earns nothing in Google. Google's Rich Results Test applies Google's rules, but only to the rich result types Google currently supports, and says nothing about types it ignores. This validator sits between them: Google's documented requirements for the types that still produce rich results, plus the mistakes that are wrong whatever the type, such as an @id that points at nothing or a date written 10/11/2026. It also gives the line and column of a syntax error, converts microdata and RDFa to JSON-LD, and exports a CSV. Google's test remains the final word on what Google itself sees, because it renders JavaScript and this check reads the HTML before scripts run.
Which rich results Google still shows
Fewer than it used to. Google removed how-to rich results in September 2023. FAQ rich results were cut back to well-known government and health sites the same year, and Google stopped showing them at all on 7 May 2026. The sitelinks search box that WebSite markup once powered went in November 2024, and Dataset markup now feeds Dataset Search rather than Google Search. None of that makes the markup wrong: FAQPage and HowTo are still valid schema.org that other search engines and AI tools can read. The validator marks those entities as retired instead of failing them, so you can see at a glance which markup still earns a rich result in Google and which is there for everyone else. The rules were read from Google's documentation in November 2026, and each type in the readout links to its page there.
Common schema markup errors and how to fix them
A trailing comma after the last property is the most common syntax error, because JavaScript allows it and JSON does not. A raw line break inside a description, usually pasted from a CMS field, is next. Prices written as £19.99 or 19,99 fail: Google wants 19.99 in price and GBP in priceCurrency. Dates such as 10/11/2026 are ambiguous and not ISO 8601; write 2026-11-10. Relative URLs such as /logo.png work in a browser but not in structured data, which needs https:// and the host. A lower-case type is read as a different, unknown type, so the whole node is ignored. Breadcrumb positions must run 1, 2, 3 with an item URL on every step except the last. And a rating must fit its scale: a 9 out of 10 needs bestRating 10, or Google reads it as out of 5.
@id, @graph and entities split across blocks
Large sites, and SEO plugins such as Yoast and Rank Math, describe a page as a graph: one block with an @graph array where the Article points to its author and publisher by @id instead of repeating them. Google follows those references within the page and merges nodes that share an @id, so this validator does the same before it judges anything. A Product described in two blocks with the same @id is checked as one Product. What breaks is a reference to an @id that is not on the page: Google reads each page on its own, so a publisher defined only on the home page resolves to nothing on a blog post. Each one is listed with the property that points at it.
Microdata and RDFa
Older themes and many ecommerce platforms write structured data as microdata (itemscope, itemtype and itemprop attributes) or RDFa (vocab, typeof and property). Google reads both, and a validator that only looks for JSON-LD reports those pages as having no structured data, which is wrong. This one converts microdata and RDFa items into the same entities as JSON-LD and runs the same checks on them, then offers the result as JSON-LD to copy, which is the format Google recommends because it lives in one block rather than across the page's HTML.
Valid markup and no rich result
Passing every check makes a page eligible for a rich result, never certain of one. Google also applies content guidelines (the marked-up content must be visible on the page, reviews must be genuine and not written by the business about itself), quality signals for the site, and its own judgement about when a rich result helps the searcher. Markup added by JavaScript is read by Google after rendering, which this validator does not do, so if the HTML has no structured data and you know a plugin adds it, test the page in Google's Rich Results Test as well. After a fix, Search Console's rich result reports show when Google has recrawled the page.
Frequently asked questions
- Is this schema markup validator free?
- Yes. It is free, needs no sign-up and no email, and the only limit is a rate limit that stops one visitor sending hundreds of checks a minute.
- Can I validate schema markup before it is live?
- Yes. Switch to Paste code and paste a JSON-LD object, the script tags, or a whole HTML page. Nothing is fetched and nothing you paste is stored.
- Does it check microdata and RDFa as well as JSON-LD?
- Yes. Microdata and RDFa items are converted to the same entities as JSON-LD and get the same checks, and you can copy them out as JSON-LD.
- Why does Google's Rich Results Test show something different?
- Google's test renders JavaScript and only reports the rich result types Google supports. This validator reads the HTML before scripts run and also checks types Google ignores. If a plugin adds your markup with JavaScript, Google's test will see it and this one will not.
- Does the FAQ schema still give a rich result?
- No. Google stopped showing FAQ rich results on 7 May 2026, after limiting them to government and health sites in 2023. FAQPage is still valid schema.org, so the validator marks it as retired rather than as an error.
- What does "required" mean here?
- A property Google's documentation lists as required for that rich result. Without it the page cannot get the result. schema.org itself requires nothing, which is why validator.schema.org passes markup that Google will not use.
- Is schema markup a ranking factor?
- Not directly. Google uses structured data to understand a page and to decide whether it can show a rich result, such as review stars or a breadcrumb trail in place of the URL. Those change how the listing looks and how many people click it.
- Can I export the results?
- Yes. Download CSV saves every finding with its severity, entity, property path and line, followed by the rich result readout. Copy as JSON-LD copies every entity found, microdata and RDFa included.
- Can I check every page on my site at once?
- Not here: this tool checks one URL or one paste at a time. Crawl Cove, the desktop crawler, checks the structured data on every page of a site in one crawl, and it has a permanent Free plan.
- Can I share the result?
- For a URL check, yes. The page address includes the URL you checked, so copying it gives a link that re-runs the same check. Results are cached for ten minutes. Pasted code is not put in the address, so it stays private to you.
From one page to your whole site
This validates one page. Crawl Cove checks the structured data on every page it crawls, so a product template that lost its offers or a theme update that broke the JSON on every post shows up as one list instead of one URL at a time. See check structured data site-wide or write the markup with the schema markup generator.
Want the same checks in a terminal or a CI pipeline? The open-source CLI validates JSON-LD from a URL, a file or stdin and exits non-zero on an error: crawlcove-schema-validator.
More free tools
More on-page SEO tools →-
Website SEO Checker
Open tool → -
HTTP Header Checker
Open tool → -
Canonical Checker
Open tool →