Schema Markup Checker

Paste a URL and the checker fetches the page, extracts every <script type="application/ld+json"> block, and validates each one in three layers: the JSON must parse (syntax errors are shown with a line and column where the browser reports one), every entity must carry an @context referencing schema.org and an @type, and 12 common types are then graded against a checklist based on Google's rich-results documentation. Missing required fields show as errors, missing recommended fields as warnings, and it understands arrays, multiple types, and @graph containers.

Required fields are the ones Google's documentation says a rich result cannot appear without: headline on an Article, offers with a price and priceCurrency on a Product, or name, startDate and location on an Event. Recommended fields, like an Article's image and author or a Product's aggregateRating, are not mandatory but make the rich result richer and more likely to show. The checker marks missing required fields as errors and missing recommended fields as warnings, so you can fix eligibility first and enrichment second.

The checker reads the raw HTML the server sends, so JSON-LD injected later by JavaScript, a tag manager, or a CMS plugin that renders client-side will not appear, even though Google's rendering crawler may still see it. It also reads JSON-LD only: schema written as microdata or RDFa attributes in the HTML is real structured data but outside this tool's scope. Finally, if the site's bot protection blocked our request, the tool says so explicitly rather than claiming the page has no schema.

No, and it is not trying to be. Google's Rich Results Test renders the page with JavaScript and applies Google's exact, frequently updated eligibility rules; this checker is a fast static check that catches the problems responsible for most schema failures: broken JSON, a missing @context or @type, and absent required fields. Use this tool for quick audits and debugging while you build, then confirm final eligibility for a specific rich result in Google's own test.

A theme update, plugin change, or CMS migration can silently strip the JSON-LD from a page, and you typically only notice weeks later when rich results vanish from search. SiteGauge re-checks a page on a schedule, records the schema types it finds on every check, and alerts you the moment they change or disappear. That works on your own pages and on competitors' pages, so you can also see when a rival adds Product or FAQ markup you have not.