AuditsStructured data checker
Check the Schema.org markup machines rely on.
Search engines, rich results, shopping surfaces and AI systems read structured data to understand what a page is about. MaxiMarket reads the JSON-LD on a page, checks that it parses and declares a usable Schema.org type, and validates the properties documented for Organization, BreadcrumbList, Article, Product, Offer and Review markup.
What it checks
- JSON-LD that parses
- Schema.org @type
- Organization and WebSite
- BreadcrumbList
- Article, author and dates
- Product and Offer
- Review and AggregateRating
Check the structured data on a page
Free, read-only and usually done in about a minute. No account needed for your first audit.
How it is checked
Parse, identify, then validate.
Every JSON-LD block must parse
A trailing comma or an unescaped quote makes a whole block unreadable, including everything that was correct in it.
It must say what it describes
Valid JSON without a usable
@typetells machines nothing. @graph structures and nested entities are followed.Each type needs its properties
Recognized entities are checked against the properties their documentation requires, below and in the ecommerce checks.
Schema.org types
The schema markup that is validated.
Product, Offer and ProductGroup data have their own, larger set of checks, explained in the ecommerce SEO audit.
Organization and WebSite
On the home page: who publishes the site, with a name, url and a logo large enough to use, and the WebSite entity for the canonical home URL.
BreadcrumbList
Breadcrumb trails whose items have a name and URL, with positions that run 1, 2, 3 in order.
Articles, authors and dates
Article headline, image, dates and author, author names, and dates in ISO 8601 with a time zone that are realistic.
Reviews and ratings
AggregateRating and Review markup with the properties search engines require before they can use it.
Example
Two small mistakes, two findings.
This markup parses and has types, so it looks fine at a glance. On a home page, MaxiMarket reports the missing logo and the breadcrumb position that skips from 1 to 3:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Tools",
"url": "https://example.com/"
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Tools", "item": "https://example.com/tools" },
{ "@type": "ListItem", "position": 3, "name": "Drills", "item": "https://example.com/tools/drills" }
]
}
</script>How to fix: Add name, url and logo to the Organization.
How to fix: Number the ListItems 1, 2, 3 … from the start of the trail.
Scope
Scope of this structured data checker
- MaxiMarket evaluates JSON-LD, the format Google recommends. Microdata and RDFa markup are not evaluated.
- Passing these checks means the documented requirements are met. Whether a search engine shows a rich result is its own decision.
- When a page builds its content with JavaScript, the audit renders it, so structured data added by scripts is checked too.
Free during the Public Beta
Check the structured data on a page
The audit reports every JSON-LD block it inspected, the types it found, and each missing or invalid property, next to the rest of the page’s technical findings.
Read how a MaxiMarket page audit works or browse the published Audit Standard.