aeotime
Start free trial

Free tool · no signup

Free Schema Markup Validator

Paste a URL or a snippet. The validator finds every JSON-LD block, reports the ones that don't parse, and checks each entity — Organization, Product, FAQPage, Article and more — for required and recommended fields.

What it checks

An AI-readiness audit, check by check · illustrative

The validator reads the server HTML of the page (no JavaScript), extracts each <script type="application/ld+json"> block and parses it. A block with a JSON syntax error is reported with the parser's message — search engines ignore the whole block, so one stray comma can remove all your markup.

Every typed entity inside, including nested ones and @graph arrays, is then checked against field rules for common types: Organization, LocalBusiness and its subtypes, Product, Offer, FAQPage, Question, Article and BlogPosting, BreadcrumbList, WebSite, SoftwareApplication, HowTo, Recipe, Event, Person, VideoObject and Review. Rules follow schema.org and Google's structured data documentation.

How to read the results

  • Missing (required) — a property the type needs to be useful, such as name on an Organization or offers, review or aggregateRating on a Product. Fix these first.
  • Add (recommended) — properties that make the entity more complete: logo and sameAs on Organization, datePublished and author on Article.
  • Parsed — the type is valid JSON-LD but has no rule set here. That's not an error.

What this validator doesn't do

It doesn't render JavaScript, doesn't check microdata or RDFa, and doesn't decide rich result eligibility. For eligibility, Google's Rich Results Test is the reference, and the Schema.org validator checks full vocabulary conformance. Use this tool for a fast read of what's actually in your HTML — the same HTML AI crawlers see. To create markup, use the schema markup generator.

FAQ

Questions

Why does my markup show in Google's test but not here?+

Google's Rich Results Test renders JavaScript; this tool reads the raw server HTML. If schema only appears here after rendering, it's injected by client-side code, and crawlers that don't execute JavaScript won't see it.

Is a missing recommended field a problem?+

No, the markup is still valid. Recommended fields give search engines and AI systems more facts to work with, so add them when the information exists on the page.

Should I use JSON-LD, microdata or RDFa?+

Google recommends JSON-LD because it sits in one block and doesn't have to be woven into your HTML. All three are supported; this validator reads JSON-LD only.

Keep reading

Related

Schema markup generator→JSON-LD for Organization, LocalBusiness and Product.FAQ schema generator→Turn questions and answers into valid FAQPage JSON-LD.AEO checker→Grade any URL A–F on AI-readiness: crawler access, llms.txt, schema, meta.

Check once. Or track it every week.

aeotime runs your prompts on eight AI engines every week, shows who gets recommended instead of you, and turns it into an action plan.

Start 7-day trial →See pricing