Structured data checker: find what's missing or broken.

1. 1Parsing

   Each JSON-LD block is parsed on its own. One stray comma and search engines skip the whole block; we show the error.

2. 2Required fields

   Article, Product, Offer, Review, FAQ, Event, Recipe, Video, JobPosting and more, checked against Google's docs.

3. 3Recommended fields

   Not needed for eligibility, but each one gives search engines and AI models more to work with.

4. 4Value formats

   Dates that aren't ISO 8601, relative URLs where absolute ones are expected, and empty strings.

5. 5Page fit

   A homepage should carry Organization and WebSite; an article, Article; a product page, Product. We say which is missing.

6. 6Entity links

   Whether your Organization's sameAs points at Wikidata or Wikipedia, the strongest identity signals there are.

Nested nodes are checked too, so an Offer inside a Product inside an @graph gets the same scrutiny as a top-level node. Microdata and RDFa are counted and listed by type, not validated property by property.

Schema injected by JavaScript. Tag managers and some plugins add JSON-LD after load. If this checker finds nothing but your browser's inspector shows it, that's why. Move it into the server-rendered template. What AI Sees shows the full picture.

Dates in the wrong format. “March 4, 2026” isn't machine-readable. Use 2026-03-04 or a full timestamp with a timezone offset.

Offers without a currency. A price of 89 means nothing without priceCurrency. Add it, plus availability.

Duplicate, conflicting nodes. An SEO plugin and a theme both output Organization with different names or logos. Keep one.

Article without an author. Give author a Person with a url pointing at a real bio page. It's cheap and it's what systems look for when they weigh who wrote something. Our Schema Markup Generator builds the block for you.

AI search tools fetch pages, strip them to text and decide what to quote. JSON-LD survives that process intact: a price, a rating, an author and a publish date in a format no one has to interpret. When the prose is ambiguous, the schema settles it.

It's not a shortcut to being cited. Pages get quoted for clear, specific answers. But schema that is complete and matches the page removes a reason to skip you, and entity links in sameAs help a model connect your site to what it already knows about your company.