Validate JSON-LD, Microdata, and RDFa structured data on any URL. See exactly which schema types are declared and whether they parse correctly for Google rich results.
Structured data is the price of entry for Google rich results — review stars, FAQ accordions, product cards, recipe boxes. Invalid JSON-LD silently disqualifies a page; you only find out by losing the rich snippet.
We fetch the public HTML (capped at 600KB to control parser cost) and extract every <script type="application/ld+json"> block, every itemscope+itemtype attribute pair (Microdata), and every typeof= attribute (RDFa). JSON-LD blocks are JSON.parse()-ed; failures are reported with the parser error and a snippet for debugging. We separately count OpenGraph and Twitter card meta tags because they affect social previews even though they are not strictly structured data. The 0–100 score rewards valid blocks, penalises parse failures, and adds bonuses for OpenGraph + Twitter coverage.
Paste the URL above. The tool extracts every JSON-LD, Microdata and RDFa block from the live HTML, confirms each parses, and lists the declared @type values so you can see exactly what a search engine would read.
Valid markup earns eligibility, not a guarantee. The usual blockers are a missing required property, structured data that describes content not visible on the page, or markup injected by JavaScript that the crawler never executed.
Yes, for almost every case. Google recommends JSON-LD because it does not entangle markup with content, can sit in <head>, and is easier to template.
No — but every page that could earn a rich result should have it. Articles, products, FAQs, recipes, events, and how-tos benefit most. Static About pages do not.
Schema does not directly boost rankings, but rich results dramatically increase CTR from the same ranking position — which Google then interprets as quality.
Yes. A blog post typically ships Article + BreadcrumbList + (optional) FAQPage as separate JSON-LD blocks. Google parses all of them.
Marking up content the user cannot see (cloaking) or fabricating reviews. Both can trigger manual penalties. Always mark up what is actually on the page.
Paste the URL above. The tool extracts every JSON-LD, Microdata and RDFa block from the live HTML, confirms each parses, and lists the declared @type values so you can see exactly what a search engine would read.
Valid markup earns eligibility, not a guarantee. The usual blockers are a missing required property, structured data that describes content not visible on the page, or markup injected by JavaScript that the crawler never executed.