JSON syntax
Parse each application/ld+json block independently so one malformed block does not hide the rest.
Free schema markup checker / live JSON-LD
See the structured data the public page actually returns.
Fetch one public page, parse every bounded JSON-LD block, inventory its entity types, and expose broken JSON or missing context without digging through page source.
✓ No signup✓ Live HTML✓ Read-only
40maximum JSON-LD blocks
2 MBbounded HTML response
Liveserver markup checked
$0no account required
Separate parseable markup from markup that only looks present.
A script tag count cannot tell you whether its contents are broken, what entities it describes, or whether an enclosing context exists. RankLatch turns those live blocks into a concise evidence report.
Type inventory
Follow nested objects and @graph arrays to list the distinct @type values exposed by the page.
Context presence
Surface valid JSON-LD structures that do not declare an @context at the block or graph level.
Format context
Count microdata items and RDFa typeof declarations without pretending they received full validation.
Parsing evidence—not a rich-result promise.
- ✓JSON-LD blocks present in the server-returned HTML
- ✓Whether each inspected block contains parseable JSON
- ✓Declared types, contexts, identified nodes, and a bounded @id count
- ✓Final HTTP response plus redirect context
- —Google rich-result eligibility or search-feature appearance
- —Every required or recommended property for every Schema.org type
- —Structured data inserted only after client-side rendering
- —Whether markup matches visible content and applicable search policies
Current markup → removal evidence
Know if a schema block disappears later.
RankLatch records the number of JSON-LD blocks in each approved page snapshot and logs an evidence event when a later daily check returns fewer. It does not claim to compare every nested property.
See continuous monitoring →Straight answers
Before you check.
Structured data is useful only when its code, meaning, visible content, and search-policy requirements agree.
01What structured data does this checker read?+
RankLatch parses JSON-LD scripts returned in the server HTML and inventories their @type, @id, @context, and typed-node structure. It also counts HTML microdata items and RDFa typeof declarations without attempting to fully validate those formats.
02Does valid JSON mean the schema is valid?+
No. Valid JSON only proves the block can be parsed. The checker also identifies missing context and untyped structures, but it does not validate every Schema.org property or Google's requirements for a specific rich-result feature.
03Does this replace Google's Rich Results Test?+
No. Use Google's Rich Results Test to evaluate supported search-feature eligibility and its reported warnings. This tool is useful for quickly inventorying every live JSON-LD block and exposing broken JSON before that step.
04Does the checker execute JavaScript?+
No. RankLatch checks the bounded public HTML response. Structured data added only after browser-side JavaScript runs may not appear here, and the result clearly states that limitation.
05Can a page have more than one JSON-LD block?+
Yes. Multiple blocks can be intentional. RankLatch reports each one separately, follows nested objects and @graph arrays, and combines the types into one page-level inventory.
06Will schema markup guarantee a rich result or ranking improvement?+
No. Structured data does not guarantee crawling, indexing, a search feature, rankings, or traffic. It should accurately describe visible page content and comply with the search engine's applicable policies.
07What happens with a very large page?+
The public endpoint reads at most 2 MB of HTML and inspects the first 40 JSON-LD blocks. If a page exceeds the block limit, the result labels the inspection as bounded rather than claiming full coverage.