ZenovayTools

Structured Data Validator

Validates JSON-LD and Microdata structured data against schema.org specs. Checks required properties for 12 schema types (Article, Product, FAQPage, LocalBusiness, Recipe, Event…) and grades rich snippet eligibility.

How to Use Structured Data Validator

  1. 1Enter the URL you want to validate.
  2. 2The tool extracts all JSON-LD and Microdata structured data from the page.
  3. 3Review validation results per schema type with required vs missing properties.
  4. 4Fix flagged issues to improve rich result eligibility in Google Search.
Zenovay

Track your website performance

Real-time analytics, session replay, heatmaps, and AI insights. 2-minute setup, privacy-first.

Try Zenovay Analytics — Free

Frequently Asked Questions

What is structured data and why does it matter for SEO?
Structured data is machine-readable markup (usually JSON-LD) embedded in your HTML that tells search engines what your content is about. Google uses it to generate rich results — star ratings, FAQ dropdowns, recipe cards, event listings, breadcrumbs — which increase click-through rates by 20–30% compared to regular search results.
What happened to Google's Structured Data Testing Tool?
Google deprecated the Structured Data Testing Tool (SDTT) in July 2023. The replacement, Rich Results Test, requires a Google account, renders JavaScript (which can be inconsistent), and doesn't expose detailed validation output. This tool fills that gap with instant HTTP-based validation of static JSON-LD without requiring login.
What schema types does this validator check?
Article, NewsArticle, BlogPosting, Product, FAQPage, BreadcrumbList, LocalBusiness, Organization, Event, Recipe, JobPosting, Review, WebSite, and Person. These cover the most common rich result types in Google Search. Validation checks both schema.org base requirements and Google's specific rich result requirements.
What is the difference between required and recommended properties?
Required properties are mandatory for the schema type to be valid per schema.org spec. Missing required properties prevent rich results from appearing. Recommended properties are optional per the base spec but strongly advised by Google for better rich result display — for example, an Article's image is technically optional but Google almost always needs it for the Article rich result.
My schema passes validation but I still don't get rich results — why?
Valid structured data is necessary but not sufficient for rich results. Google also considers: (1) page quality and relevance, (2) whether the page has been crawled and indexed recently, (3) the schema is only used for the page's primary content, (4) no spammy or misleading use of schema. This tool can only validate schema correctness, not predict Google's quality assessment.
What is @graph in JSON-LD?
@graph allows multiple schema entities to be declared in a single JSON-LD script block with relationships between them. For example, a product page might have a Product, BreadcrumbList, and Organization in one @graph. This tool handles @graph automatically and validates each entity within it separately.
Why doesn't this tool detect schemas injected by JavaScript or GTM?
This tool fetches raw HTML without executing JavaScript — the same as Googlebot's initial crawl. Schemas injected by JavaScript (GTM, analytics tags, React/Next.js dynamic injection) won't appear in the raw HTML. For Google to consistently detect these schemas, embed them as static JSON-LD in your server-rendered HTML instead.