Technical SEO

Schema Markup Validator

Enter a page URL or paste JSON-LD to validate its structured data. The validator pinpoints JSON syntax errors by line and column, then checks every entity — including @graph nodes and nested offers, authors and addresses — against the properties Google documents as required or recommended for Article, Product, Breadcrumb, LocalBusiness, Event, Recipe, Video, JobPosting, Review and more.

It validates JSON-LD in depth and lists the microdata and RDFa it finds. It is not Google's own tool: for Google features, the Rich Results Test has the final word.

FreeNo signupChecks the live pageUpdated October 2026

Schema Markup Validator

Pasted code stays in your browser. In URL mode our server fetches the public page and keeps no copy.
How it works

How to use it

  1. 01

    Enter a URL or paste code

    Check a live page by URL, or paste raw JSON-LD or the HTML around it — every script tag with type application/ld+json is picked up.

  2. 02

    Fix the errors first

    Errors are syntax mistakes and missing required properties — until they are fixed, the markup can't produce a rich result. Each one says where it is and what to change.

  3. 03

    Then work through the warnings

    Warnings cover recommended properties and values in the wrong format: relative URLs, dates that aren't ISO 8601, prices with currency symbols.

  4. 04

    Confirm in Google's Rich Results Test

    Before publishing, run the page through Google's Rich Results Test — it decides eligibility for Google's own features.

Honest notes

What this tool does and does not do

It parses JSON-LD, flattens @graph and nested entities, follows @id references between blocks and checks each entity against the requirements Google Search Central documents for the most common rich result types. Other Schema.org types get syntax and general checks only — they are never reported as invalid just because the checker doesn't know them.

Passing here doesn't guarantee a rich result. Google decides what to show, and markup must describe content visitors can actually see on the page. Google no longer shows FAQ rich results (since May 2026) or HowTo rich results (since 2023); the validator still checks that markup and tells you so.

URL mode reads the HTML as served, without running JavaScript, so markup injected by scripts or a tag manager won't appear here — Google, which renders JavaScript, may still see it. Microdata and RDFa are detected and listed, not validated property by property.

In URL mode our server fetches the public page and keeps no copy; pasted code is checked in your browser and never sent anywhere.

Seonix does this on autopilot

Valid structured data on every article — without checking it by hand

Seonix generates JSON-LD for every article it publishes from that article's own content, so the markup always matches the page. Its free site audit checks the rest of your site — missing or invalid structured data, broken links, redirect chains — across SEO, technical health, AI readiness and speed.

For your stack

SEO on autopilot for the site you have

Seonix researches, writes and publishes articles — and keeps the technical side in check — wherever your site lives.

Frequently asked questions

How do I validate schema markup?

Enter the page URL or paste the JSON-LD into the validator above. It flags syntax errors with the line and column, missing required properties and values in the wrong format, entity by entity. For Google rich results, confirm the final version in Google's Rich Results Test.

How is this different from Google's Rich Results Test?

The Rich Results Test shows which Google features a page is eligible for, and it renders JavaScript. This validator also covers types Google has no rich result for, explains each problem in plain language with the fix, checks pasted code before it is published, and flags issues such as relative URLs, invalid dates and the same entity marked up twice.

Why doesn't my FAQ markup show up in Google?

Google stopped showing FAQ rich results in May 2026; from 2023 they were limited to well-known government and health sites. Valid FAQPage markup is still machine-readable, but it no longer produces a FAQ snippet in Google results.

Does structured data improve rankings?

Not directly. Structured data makes a page eligible for rich results and helps machines understand it without guessing; it is not a ranking factor on its own, and no validator can promise a rich snippet.

Is JSON-LD better than microdata?

Google supports JSON-LD, microdata and RDFa, and recommends JSON-LD because it sits apart from the visible HTML and is easier to maintain. This tool validates JSON-LD in depth; for microdata it lists the types it finds.
Free tools

More free tools

All free tools