Jahanzaib

Free tool

Structured data validator

Schema markup tells a machine what a page is about: who wrote it, which company it belongs to, what a product costs. I built this validator to read the JSON LD on a live page, check it against schema.org and Google documentation, and tell you in plain words what is broken and how to fix it.

Need markup written from scratch? Use the schema markup generator.

New to the topic? Start with what structured data validation checks.

The check runs on app.jahanzaib.ai, my free tools app, and opens there.

The quick check is free and needs no account: the schema types on the page and how many errors it found. The full report needs a free account, which you open with a code sent to your email and no password. It lists every error with its fix, the types the page is missing and a corrected version of your markup.

Want to test markup before it goes live? Paste your code on my tools app.

Coverage

What it checks

  • Every block parses

    Finds each JSON LD script on the page and flags the ones that are not valid JSON, the most common reason markup is silently ignored.

  • Context and type

    Checks that each node declares schema.org as its context and a type that exists, spelled the way schema.org spells it.

  • Required and recommended properties

    Compares each node with the properties schema.org defines and Google documents for that type, and lists what is missing or malformed.

  • Links between nodes

    Follows the id references that tie an Article to its author or a page to its organization, and flags references that point to nothing.

  • Your identity

    Looks for one Organization or Person node with sameAs links to your real profiles, and flags duplicate Organization nodes that disagree.

  • Types answer engines use

    Lists the types that help a machine read your facts, such as Organization, Person, Article, Product and BreadcrumbList, and notes the ones this page could carry.

Method

How it works

  1. 1

    Enter a page or paste code

    Enter a live address here, or paste JSON LD or HTML on the app to test markup before you publish it.

  2. 2

    The app reads the markup

    For a live page it fetches the HTML from a public address and pulls out every JSON LD block, exactly as published.

  3. 3

    Each node is checked

    Every node gets a status with the property at fault and the fix in plain words. If the page fails to load, you see the error and nothing else.

  4. 4

    Copy the fix

    With a free account you get a corrected version of your markup to copy back into your page.

Example

What the report sections look like

An illustration of the layout with sample wording. It is not a result for any real page.

  • Types found

    For information

    Each node on the page with its type and where it sits in the graph.

    The page declares an Organization, a WebSite and an Article that names a Person as its author.

  • Errors

    Needs a fix

    Each problem with the node, the property and the fix.

    The Product offer has a price but no priceCurrency. Add the currency code, such as USD.

  • Identity

    Passed

    The Organization or Person node and its sameAs links.

    One Organization node with sameAs links to the company profiles on LinkedIn and GitHub.

  • Missing types

    For information

    Types that suit this kind of page and are not on it yet.

    This looks like a blog post with no Article markup. Adding one lets a machine read the author and dates.

Questions

Frequently asked questions

Does structured data get my page cited by AI assistants?

It helps a machine read your facts without guessing, such as who wrote the page and which company it belongs to. It does not promise a citation or a rich result, and this validator gives no score for that reason.

Does it read microdata or RDFa?

It reads JSON LD, the format Google recommends. If your markup is in microdata or RDFa, the report says it found none in JSON LD.

Can I check markup before it is live?

Yes. On the app you can paste JSON LD or a block of HTML instead of entering an address.

Should I add FAQPage markup?

Only when the questions and answers really appear on the page. Google no longer shows FAQ rich results in search, so the markup earns its place only as an accurate description of the page.

Do I need an account?

No. The quick check, with the types on the page and the error count, is free without an account. The full list of errors with fixes needs a free account, which you open with a code sent to your email. There is no password.

More free tools

Related tools

See every free tool

Rather hand it over?

I can find the fixes and ship them for you

I run SEO and answer engine optimization as one managed program: the pages, the technical fixes, the markup and the mentions that AI assistants read. You get a plain monthly report on what changed.

See how I run AEO