Schema Analyzer

The Schema Analyzer is a free tool that fetches any public page and reads every JSON-LD structured data block it contains — the <script type="application/ld+json"> tags search engines parse to understand what a page represents. It reports which schema.org types are declared, whether each block's JSON is actually valid, and surfaces the raw structure so you can confirm your Article, Product, FAQPage, or Organization markup is set up the way you intended, without digging through page source by hand.

It exists because structured data fails silently. A single misplaced comma or unescaped character makes an entire JSON-LD block unparseable, and search engines simply skip it — no error appears on the page itself, and rich results that would have shown a star rating, an FAQ dropdown, or breadcrumbs in search listings just never show up. Running a scan catches exactly that kind of quiet failure before it costs a site the extra visibility rich results provide.

When you submit a URL, the tool fetches the page's live HTML and extracts every <script type="application/ld+json"> block it contains. Each block's content is parsed as JSON — if parsing succeeds, the tool reads its @type field (or fields, for an array of entities) to identify which schema.org types are declared; if parsing fails, the block is flagged as invalid and reported separately, since search engines would discard it under the same conditions.

This reflects the page's HTML response at the moment you run the scan, not a historical or cached copy — it does not execute JavaScript, so structured data injected purely client-side after page load may not appear in the results. It also checks JSON-LD specifically, since that's Google's recommended and by far the most common format; older microdata or RDFa markup embedded directly in HTML attributes isn't covered by this scan.

• Use JSON-LD rather than microdata or RDFa. It's Google's recommended format, keeps structured data cleanly separated from your visual markup, and is far easier to maintain and validate over time.
• Match the schema type to the actual content. Article for blog posts, Product for e-commerce listings, FAQPage for FAQ sections — using the wrong type, or a generic one, forfeits rich-result eligibility you'd otherwise qualify for.
• Remember that invalid JSON is ignored entirely, not partially applied. A single stray comma or unescaped quote drops the whole block silently, taking every rich-result benefit with it until the syntax is fixed.
• Re-validate schema after any template or CMS update. Structured data lives in code that's easy to accidentally break during a redesign, and a broken block often produces no visible error on the page itself.