Free tool · No signup

Check what your schema markup actually says

Inspect JSON-LD in a public page's static HTML and find invalid JSON, detected types, missing fields, and source markup.

Schema markup checker Free

Five checks per IP address within the current usage window. Public HTTP and HTTPS pages only.

Enter a page URL to inspect its static JSON-LD.
  • Up to 50 JSON-LD blocks
  • Type and syntax evidence
  • JSON export

A precise first check

Parsing is only the first layer.

01

JSON syntax

Malformed JSON-LD cannot be parsed. The checker reports the approximate line and column so you can return to the source block.

02

Declared structure

Detected @type values and basic warnings reveal what the page claims, without inventing a universal score.

03

Platform validation

Schema.org vocabulary and Google rich-result requirements are separate checks and can change independently.

Important boundaries

What this result does not promise

The checker reads JSON-LD from one page's static HTML. It does not validate Microdata or RDFa, execute browser JavaScript, certify every Schema.org property, or guarantee a rich result.

After fixing syntax, use the Schema.org validator for vocabulary validation and Google's Rich Results Test for supported search features. For repeatable extraction, use the Schema Markup Extraction API.

Common questions

Schema checker FAQ

Is valid JSON-LD automatically valid schema?

No. JSON syntax can be correct while a type or property is misspelled, misplaced, incomplete, or inconsistent with visible content.

Does valid schema guarantee a rich result?

No. Search platforms apply feature requirements, policies, crawling signals, and their own display decisions.

Why does the checker show no schema?

The page may not contain JSON-LD, the fetch may receive different HTML, or JavaScript may add the markup only after the initial response.

Check structured data against the page

The free Schema Markup Checker finds JSON-LD on a public webpage and helps you review types, properties, and parsing errors. Markup should describe information users can actually see.

Validation does not guarantee a rich result. Pair it with the broader SEO Page Inspector.

What to review

Confirm values, canonical URLs, dates, prices, and nested organization, author, product, or article entities.

Common problems

Watch for invalid JSON, duplicated entities, placeholder values, unsupported properties, and stale information.

Use schema carefully

Our AI search guide explains why schema is useful but not an AI citation shortcut.