FAST. PRIVATE. NO SIGN-UP.

Free Schema Markup Checker

Read the structured data that a public page actually returns and inspect each JSON-LD block for parse validity, declared @type values and top-level properties.

TOOLMERA
Loading tool…
Preparing the interactive tool in your browser…
Public-data onlyLive public HTTP/HTTPS checks
Instant workflowNo setup or account required
Free core toolOpen it and get the task done
WHY TOOLMERA

Built to get the task done.

  • JSON-LD block detection
  • Schema type inventory
  • Invalid JSON reporting
ABOUT THIS TOOL

Free Schema Markup Checker — Inspect JSON-LD Structured Data

Inspect JSON-LD on a public page, list declared schema types and surface invalid JSON blocks without claiming rich-result eligibility.

See the JSON-LD that is really present in the server HTML

Structured-data debugging often starts with a simple question: did the markup reach the page at all? Toolmera reads application/ld+json blocks from the HTML response and reports how many were found, which ones parse as JSON and which schema types they declare.

This is useful after template changes, CMS migrations and conditional rendering bugs where the intended schema exists in code but never reaches the public HTML returned to a crawler.

Detected formatJSON-LD script blocks
Syntax checkJSON parse success or parse error
Type inventory@type values, including @graph nodes

Valid JSON is not the same as valid rich-result markup

A JSON-LD block can be perfectly valid JSON and still be incomplete for a particular Schema.org type or a Google search feature. Toolmera therefore separates syntax inspection from eligibility claims.

Use the report to catch malformed JSON, missing markup or unexpected @type values. For Google-specific rich-result requirements, continue with Google documentation or Rich Results Test because those rules change by feature and are stricter than basic JSON syntax.

Multiple schema blocks and @graph structures are normal

Modern sites often publish Organization, WebSite, BreadcrumbList, Article, Product or other entities in separate blocks or inside one @graph. The checker inventories the types it can parse instead of assuming there should be exactly one schema object.

That makes the report especially useful when plugins, themes and custom code all inject markup and you want to see the combined public result.

Server HTML and client-rendered schema can differ

The current checker reads the HTML response and does not run a full browser rendering engine. If a site injects structured data only after client-side JavaScript executes, that late markup may not appear in this report.

For SEO debugging this limitation is useful to know explicitly: the checker tells you what the server response contains, not what a fully executed browser DOM might eventually contain.

HOW IT WORKS

How to use Schema Markup Checker

01

Enter a public URL

Paste the website or page you want to analyze.

02

Run the live check

Toolmera fetches bounded public response data relevant to this checker.

03

Review the evidence

Use the returned values and stated limitations before changing production configuration.

SOURCES

Reference material used for this page:

Schema.org — Getting startedGoogle Search Central — Structured data
FAQ

Common questions

Does the Schema Markup Checker validate rich-result eligibility?

No. It checks JSON-LD presence, JSON syntax and declared schema types. Google rich-result eligibility has feature-specific requirements that should be checked with Google tools and documentation.

Does it support @graph?

Yes. The type inventory walks parsed JSON-LD structures and can surface @type values inside @graph nodes.

What happens if a JSON-LD block is malformed?

The block is reported as invalid with a shortened parse-error message so you can locate the syntax problem.

Does it detect Microdata or RDFa?

This version focuses on JSON-LD because it is the format explicitly extracted by the checker.

Does it execute JavaScript?

No. It analyzes structured data returned in the server HTML response.