Free structured data tool
AI Schema Markup Checker
Paste a public page URL to see its JSON-LD structured data: the Schema.org types it declares, any parse errors, and which commonly-used properties are present. A free JSON-LD and structured data checker.
We fetch the page and scan it for <script type="application/ld+json"> blocks. Public pages only.
What this checker tests
Is JSON-LD present?
Whether the page contains any `<script type="application/ld+json">` block at all, and how many.
Which Schema.org types are declared
Every `@type` found across all blocks — including types inside an `@graph` container and inside JSON-LD arrays. Types this tool doesn't have guidance for are still listed, not dropped.
Syntax / parse errors
Each block is parsed on its own. A block with invalid JSON is reported as a parse error (and the others are still analysed).
Commonly-used properties per type
For recognised types (Organization, Article, Product, LocalBusiness, FAQPage, …) the tool marks properties as Found or Consider adding — guidance, not a pass/fail verdict.
Practical recommendations
A short, cautious list: fix parse errors first, add commonly-used properties where they apply, and remember Schema.org validity is separate from any specific rich-result requirement.
It reports what is on the page. It does not score the page, and it makes no claim about search rankings, rich results, or whether an AI system will use the content.
Why structured data matters
A web page is written for people. Structured data adds a parallel, machine-readable description of the same thing: this is an Organization named X, with this logo and these official profiles; this is an Article by this author, published on this date. That lets search engines and other systems identify the page’s entities and content structure without inferring them from the prose.
What it does not do: it is not a ranking guarantee, it does not by itself produce a Google rich result (those have their own separate requirements), and it does not guarantee that ChatGPT or any other AI system will cite or recommend the page. It is a clarity signal, not a growth lever.
JSON-LD and Schema.org, briefly
Schema.org is a shared vocabulary of types (Organization, Article, Product, …) and their properties. JSON-LD is the syntax most sites use to express it: a<script type="application/ld+json"> block containing a JSON object. Many pages wrap several entities in one @graph array; a page can also have multiple separate blocks. This checker handles all of those.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Organization", "name": "Example Co",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"sameAs": ["https://www.linkedin.com/company/example-co"] },
{ "@type": "WebSite", "name": "Example Co",
"url": "https://example.com" }
]
}
</script>Schema types this tool recognises
The checker gives property guidance for these common types:
Any other Schema.org type is still detected and listed by name — the tool simply has no property checklist for it. Nothing is discarded.
Need to build FAQPage markup for a page’s Q&A section? Use the FAQ Schema Generator, then bring the page back here to check it.
Structured data is only part of the picture. To see whether the page’s wording and layout also make a clear answer easy to extract, check your content’s AI answer readiness.
How to fix common issues
1Invalid JSON in a block
A single syntax slip (a trailing comma, an unquoted key, a // comment, a smart quote) makes the whole block unreadable. Run the raw block through a JSON validator, and put multiple entities in one array rather than stacking several JSON objects in one <script>.
2No @type or no @context
Each entity needs an @type, and the document needs "@context": "https://schema.org". Without them, consumers can't tell what the data describes.
3Markup that doesn't match the visible page
Structured data should describe what a user actually sees on the page. Marking up content that isn't there (fake reviews, prices, or FAQs) is against Google's guidelines and can cause manual actions.
4Missing commonly-used properties
Add the properties that genuinely apply — e.g. author, datePublished, and publisher on an Article; address and telephone on a LocalBusiness. Only add what is true for the page.
5Confusing Schema.org validity with rich-result eligibility
A block can be perfectly valid Schema.org and still not produce a Google rich result, because rich results have their own separate, type-specific requirements. Check those against Google's documentation for the result you want.
Frequently asked questions
What is a schema markup checker?
It is a tool that reads a web page and reports the structured data it contains — here, JSON-LD embedded in application/ld+json script blocks — including which Schema.org types are declared, whether the JSON parses, and which commonly-used properties are present. This tool focuses on JSON-LD, which is the format most widely used and recommended today.
What is JSON-LD and how does it relate to Schema.org?
JSON-LD (JSON for Linking Data) is a way to embed machine-readable data in a page using a script tag. Schema.org is the shared vocabulary of types (Organization, Article, Product, …) and properties that the JSON-LD usually describes. Together they let systems read a page's entities and structure without guessing from the prose.
Does adding schema markup improve my search rankings or get me cited by AI?
There is no guarantee of that. Structured data helps search engines and other systems understand a page's meaning and structure in a machine-readable way, and it is a prerequisite for some Google rich results. It is not a ranking guarantee, it does not guarantee a rich result, and it does not guarantee that any AI system will cite or recommend the page.
Does this tool guarantee a Google rich result?
No. This checker reports what JSON-LD is on the page and whether it parses. Whether a page is eligible for a specific rich result depends on Google's own separate requirements for that result type, on content quality, and on Google's discretion. Use Google's Rich Results Test for eligibility questions.
The page has no JSON-LD. Is that an error?
No. Many pages have no structured data and still work fine. The tool returns a normal result that simply says none was detected, and suggests what you could add if it would help — for example Organization and WebSite markup on a homepage, or Article markup on a blog post.
Does it check Microdata or RDFa?
Not currently. It looks specifically for JSON-LD, which Google recommends and which is the most common format. If your structured data is in Microdata or RDFa, this tool will report no JSON-LD even though structured data exists in another form.
Why does it say a property is "Missing / consider adding" when my markup is valid?
"Consider adding" means the property is commonly used with that type and often helps consumers, not that Schema.org requires it. A block can be entirely valid without it. Only add properties that are actually true for the page.
Is my URL or page content stored?
No. The page is fetched once to analyse it and nothing about it is stored. The fetch is server-side, limited to public http/https URLs, and blocked from loopback, private, and link-local addresses.