Free structured data check
Structured Data and Schema Markup Checker
Structured data tells search engines and AI assistants what a page is: an article, a product, an organisation, a set of questions. Check that your JSON-LD parses and carries the properties each type needs.
Validate structured data
Enter a page. Every JSON-LD block is parsed and checked.
Why use the Structured Data Checker
Every block parsed
Each script of type application/ld+json is parsed, and a syntax error is reported with the block it is in.
Types listed
All the schema.org types on the page, including the ones nested inside @graph.
Required properties
Common types are checked for the properties search engines require and recommend.
Organisation and breadcrumbs
The entity behind the site and the breadcrumb trail of nested pages are confirmed.
When to use the Structured Data Checker
Rich results
Find missing properties before they cost you a rich result.
Plugin output
SEO plugins emit structured data. Check it is valid and not duplicated.
Product pages
Products need offers with a price and availability.
Articles
Articles need a headline, an author and dates.
Brand identity
An Organization with a logo and sameAs links ties your profiles together.
AI understanding
Clear entities help assistants attribute content correctly.
Understanding Structured Data
What structured data does
Structured data is a machine readable description of the page, written with the schema.org vocabulary. Search engines use it for rich results such as product prices, ratings and breadcrumbs, and to understand entities and their relations.
JSON-LD is the format Google recommends: a script block that stays separate from the visible HTML.
What to mark up
- 1Organization and WebSite. On the home page, with the name, logo, url and sameAs profiles.
- 2BreadcrumbList. On nested pages, matching the visible breadcrumbs.
- 3The main entity. Article, Product, Event, Recipe, LocalBusiness or whatever the page is about.
- 4FAQPage and HowTo. Only when the content really is a list of questions or steps.
Valid is not eligible
Valid markup does not guarantee a rich result. Search engines decide based on quality and policy, and the marked up content must be visible on the page. Test eligibility for specific results with Google's Rich Results Test.
Privacy, safety and limits
The page is fetched by AbackAuditBot from Aback servers with an ordinary GET request. No cookie, password or form data is sent, and nothing on the site is changed.
The tags are read from the HTML the server sends. Tags that a script adds after the page loads are not seen, and neither are they by most crawlers and preview bots.
Related tools and guides
Frequently asked questions
JSON-LD, Microdata or RDFa?
JSON-LD. Google recommends it, it is easier to maintain, and it does not tangle with the visible HTML. This checker reads JSON-LD.
Does structured data improve rankings?
Not directly. It enables rich results, which can improve clicks, and helps search engines and assistants understand the page.
Why is a required property missing?
Your template or plugin does not output it. The finding names the type and the property so you can add it.
Can I have several JSON-LD blocks?
Yes. Several blocks or one @graph both work. Avoid describing the same entity twice with conflicting values.
Is FAQ markup still useful?
Google shows FAQ rich results only for a small set of authoritative sites now. The markup is still valid and still describes the page.
Does this replace Google's Rich Results Test?
No. Use both. This checker validates syntax and properties and fits into a full audit. The Rich Results Test shows Google's eligibility decision.
Is there a generator?
Yes. The schema markup generator writes JSON-LD for Organization, WebSite, Article, Product, LocalBusiness, FAQPage and BreadcrumbList.