Schema Markup Analyzer

Schema Markup Analyzer

Validate schema with rich result eligibility and code generation.

Home / Free Tools / Schema Markup Analyzer
Free tool · No signup

Free Schema Markup Validator for Any URL

Paste a page URL and see every JSON-LD block on it: the schema type, the parsed contents, a list of errors, a list of warnings and a verdict on rich-results eligibility. It checks markup that already exists on a page. Free, no signup.

Every JSON-LD blockErrors and warningsRich-results verdictFree, no signup

What does a schema markup validator do?

A schema markup validator reads the structured data already published on a page and tells you whether it is correct. This one finds every JSON-LD block, shows its type and parsed contents, separates hard errors from warnings, and gives a verdict on whether the markup meets the requirements for rich results. It checks existing markup rather than creating new markup.

The report

What comes back when you paste a URL

Structured data usually breaks silently. The page looks fine, the plugin says it is working, and the markup has been wrong for eight months. This tool opens the page, finds each JSON-LD block and lays it out so you can read it without opening developer tools.

1

Every block, parsed

Pages often carry more markup than their owners realize: one block from the theme, one from the SEO plugin, one pasted in by hand two years ago. You see each block's type and its contents in readable form, which is usually how people discover they have two conflicting Organization blocks.

2

Errors

Errors are the ones that stop the markup working: a required property missing, a value in the wrong format, a date that is not a date. If a block has an error, it will not qualify for the feature it was written for, no matter how long it has been sitting on the page.

3

Warnings and the verdict

Warnings flag recommended properties you have left out. They will not break anything, but filling them in gives search engines a fuller picture. The verdict then sums it up: whether what is on the page meets the requirements for rich results, or falls short of them.

Before you trust a schema block, check these

The problems we find most often on client sites, in the order they cost the most.

Only one Organization or LocalBusiness block sitewideTwo competing blocks give search engines two answers about who you are
The @type matches what the page actually isAn Article type on a service page is a plugin default nobody changed
URLs in the markup are absolute and liveRelative paths and old http:// URLs quietly break the connection
Phone, address and hours match your Google Business ProfileMismatched details are a local SEO problem, not a schema problem
Review markup describes reviews that exist on the pageMarking up reviews that are not visible breaks Google's guidelines
No leftover markup from a previous themeOld blocks survive redesigns more often than you would think
Required properties are filled, not left as placeholdersEmpty strings and template text like Your Business Name count as errors
Honest limits

Where this tool stops

We would rather tell you the boundaries up front than have you draw the wrong conclusion from a green tick. This is a spot check on one URL, built to answer one question quickly: is the markup on this page correct right now. It is not a crawler, and it is not a substitute for your own eyes on the output.

1

It reads JSON-LD in the HTML

The checker looks at the HTML the server returns. If your markup is injected later by JavaScript, or by a tag manager that fires after load, it may not appear here even though Google can sometimes still read it. Microdata and RDFa markup is not covered either.

2

Eligible is not the same as guaranteed

Valid markup makes a page eligible for a rich result. It does not promise one. Google decides what to show based on the query, the device and its own judgment about the page, and it retires whole rich-result types from time to time. Correct markup is a ticket, not a seat.

Questions

Schema Markup Analyzer FAQ

What is the difference between a schema error and a warning?
An error means a required property is missing or malformed, so the block cannot do its job and the page will not qualify for the associated rich result. A warning means a recommended property is absent. Warnings are optional improvements that give search engines more to work with. Fix every error first, then work through warnings where the information is genuinely available.
Does valid schema guarantee rich results?
No. Valid markup makes a page eligible. Google decides whether to show a rich result based on the query, the device, the quality of the page and its own rules, and it can change or retire features whenever it wants. Anyone promising rich results in exchange for adding schema is selling you something they cannot deliver.
Are FAQ rich results still a thing?
No. Google restricted FAQ rich results to a small set of authoritative sites in 2023, then deprecated the feature entirely: it stopped appearing in Google Search from 7 May 2026, and the documentation was removed the following month. FAQPage is still a valid schema.org type and still gives any machine reading your page a clean question-and-answer structure, but it will not produce a rich result.
Does this check microdata or RDFa?
No, it reads JSON-LD blocks only. JSON-LD is the format Google recommends and the one nearly every WordPress plugin outputs, so for most sites that covers everything. If you are on an older ecommerce platform that still uses inline microdata attributes, this tool will report no markup found even though markup exists.
My schema is added by a plugin. Why does it show nothing?
Two usual causes. Either the markup is written by JavaScript after the page loads, so it is not in the HTML we fetch, or the plugin only outputs it for logged-out visitors on certain templates. Open the live page, view source and search for application/ld+json. If it is not there, the plugin is not outputting it on that URL.
How is this different from Google's Rich Results Test?
Google's Rich Results Test only reports on the features Google itself supports, so anything outside that list appears as nothing found. Schema.org runs a separate general validator at validator.schema.org that checks the vocabulary. This tool sits in between: it shows you every block on the page, flags errors and warnings, and gives a plain verdict.
Is there a limit on how many pages I can check?
One URL per run, and you can run it as often as you like. There is no account, no key and no quota. If you need every page on a site checked at once, along with the duplicate blocks that templates create across hundreds of URLs, that is a crawl rather than a spot check, and it is part of our website audit.
Keep going

Other free tools worth a minute

Clean markup is step one. Getting quoted by AI engines is the job.

We build the structured data, entity signals and content that get local businesses cited in AI answers and ranked in Maps. Book a free strategy call and we will show you where your site stands today.

Book a free CEO strategy call →
Scroll to Top